End Job Mode

Emulation Temporary:

256 KB

Disk Cache:

36 KB

System Use:

128 KB

Total Memory:

12288

PostScript Emulation VM:

1026716

VM allocated:

89940

VM remaining:

936776

Paper Size:

11" x 17"

Resolution:

600

End Job Mode

When sending print jobs through the serial and parallel protocols, some applications and their printer drivers append an end-of-document 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).

But the problem with this system is that some applications are limited by the printer language and are unable to produce an EOD com- mand. This becomes even more problematic when you’re printing to a QMS 1660 Print System, where print jobs of all supported emulations can be received simultaneously. ESP technology examines the first part of each print job to determine its emulation. Once the emulation is identified, the print job processes without further checking. This minimizes any slowdown resulting from the sensing process. To help ESP technology determine 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 and may “run” together. See chap ter 4,”Printer Con- figuration,” for more information on emulation timeout.

5-24

QMS 1660 Print System Reference