QMS 1725 SLS, Руководство пользователя

Страница: 117 / 328

End Job Mode
3-15 Daily Operations
Common Reasons to Use End Job Mode
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:
n
Multiple print jobs with little or no time delay and with no EOD
commands have been sent to the printer and the message win-
dow displays only one active job.
n
Multiple print jobs of the same printer language have been sent to
the printer and they print on the same page. (For example, you
send the AUTOEXEC.BAT file with no EOD command followed
with little or no time delay by the CONFIG.SYS file, and they both
print on the same page.)
n
Multiple print jobs of different printer languages “run” together as
if they are a single print job. (For example, you send a PCL print
job followed by a PostScript print job, and the PCL job prints and
is followed by what appears to be program code instead of your
PostScript print job.)
n
You want to print multiple jobs with header pages.
n
You want to print multiple jobs where job separation is important.
When your printer is in ESP mode, printing multiple jobs through the
serial and parallel protocols and end job mode is not set, ESP tech-
nology interprets the emulation for only the first job. The print jobs
that follow are interpreted as being the same emulation as the first
job. For example, if there are two print jobs, the first a PCL file with no
EOD command, and the second a PostScript file with a Ctrl-D (a
PostScript end-of-file character)—ESP technology interprets the
emulation of the first job correctly. But since the first print job has no
EOD command, it “runs” into the second job, and even though the
second job is PostScript, it prints in PCL.
Using the EOD Commands
Since the serial and parallel protocols may not be able to detect an
EOD automatically, due to a lack of an EOD command in some printer
languages, you can insert an EOD command at the end of your file to