Technical information

When sending print jobs through the serial and parallel protocols,
some applications and their printer drivers append an end-of-docu-
ment command (EOD) to each print job to ensure that each file prints
correctly. The reason for this is that some protocols and print queuing
systems send print jobs to the printer as one continuous data stream
(one print job immediately following another).
However, some applications are limited in printer language and are
unable to produce an EOD command. The lack of an EOD command
can cause some print jobs to be “run” together. The ESP technology
(capable of receiving print jobs from all supported emulations simulta-
neously) incorporated in your QMS 1725E Print System examines the
first part of each print job to determine its emulation. Once the emula-
tion is identified, the print job processes without checking for any
changes in emulation until an EOD is received. This minimizes any
slowdown during the sensing process. To help ESP technology deter-
mine the proper emulation of successive print jobs, the printer must
be able to identify the end of job for each job.
Therefore, unless a wait timeout (the amount of time the printer is
waiting on data from the host) occurs and ends each print job, or
unless you add an EOD command between each file being printed
through these protocols, some print jobs may be interpreted by the
printer as one job with the same emulation. See chapter 4,”Printer
Configuration,” for more information on emulation timeout.
When printing multiple jobs with little or no time delay and with no
EOD command between each job, the serial and parallel protocols
may be unable to detect an end of job automatically. So the End Job
Mode feature on QMS Crown printers was designed to allow you to
set the end of document for print jobs being sent through these proto-
cols.
If you are printing via the serial and parallel protocols, and one of the
following conditions exists, you may need to set the end job mode: