Specifications

Sessions
E-21Manual Updates
Session Command Detection and Arguments
At the start of a document data stream, the printer examines the initial
bytes of data to see if it can match the %%Session: ... string. If the
string is found, the mode and argument parameters are extracted to
determine what kind of session matching is desired. If the initial bytes
for the document do not match %%Session: ... or if there are errors
in the mode and argument parameters to the command, the printer
will act as if the command is not present in the job and default to the
Notes Since each subjob may use a different end-of-subjob argument,
the %%Session: ... command sequence must be inserted at the
beginning of each subjob to specify the end-of-subjob argument
for that particular subjob. There are two methods to signal the
end of a subjob, end by count and end by delimiter. Both
methods may be used within one document, but each subjob
may only use one method.
End by Count—You can specify how many bytes are contained
in the current subjob. After the printer reads the required
number of bytes within the current document, the printer
knows that it has reached the end of the subjob. Any data
which comes after this point, within the same connection, is
treated as the beginning of the next subjob.
End by Delimiter String—You can specify a delimiter string to
detect the end of a subjob. Make sure that the specified
delimiter string does not exist in the actual content of the
subjob, however, because it will end the subjob and treat all
remaining data as a new subjob.
Parameter
terminator
Default none
Range <CR>— carriage return
<LF>— line feed
<CR><LF>— carriage return plus line feed
Notes One or more ASCII space characters must be used to separate
each item. Any extra characters between the
argument and the
terminator are discarded.