User`s guide

TCP/IP
Accounting and
Reverse
Channel
C-13
SNMP and TCP/IP Concepts
Example—This is an example of the alternative format output:
0215155656%%[Status: busy; source:Ethernet:q33; page-
count: 12; user: fred; title: accounting.doc]%%
Errors—Errors are reported in the format
tttttttttt %%[PrinterError: string ]%%
where
tttttttttt is a string of numbers indicating real-time, and string is
a description of the engine problem. This information varies according
to printer model. However, an attempt is made to search for key words
in the error string returned by the printer to provide a subset of basic
error messages that is identical for several slightly different error
strings returned by the printer (for example, paper jam, paper out).
Again, this is done to facilitate easy automatic parsing of the log file.
(As mentioned above, no support is provided for foreign languages,
and no special subset of error messages is generated within the log
files if the printer's message window is set to a language other than
English.) For example, a paper feed jam is reported as
0215155656%%[PrinterError:paper entry misfeed]%%
and any other type of paper jam as
0215155656%%[PrinterError:paper jam]%%
Since it is possible that the same status is returned each time that the
status request is made, duplicate messages are discarded.
Reverse Channel Information Format
The reverse channel information does not require formatting by the
host software; it is stored in the log file in the form returned by the
PDL interpreter.
For example, a PostScript error might be returned as
%%[ Error: undefined; OffendingCommand: junk ]%%
The format of other information is entirely dependent on the PDL
code used to generate it. For example, an informative string contain-
ing PostScript pagecount information might be returned as
%%[ status: starting job; pagecount: xxxx ; otherstring ]%%