Océ imagePRESS C7010VPS series, Technical Manual

Page: 44 / 362

Spool full handling
New jobs are not accepted anymore when the amount of free space in the spool area falls below
the low-water mark. If a spool-full is encountered while storing a job on the disk, the reception is
aborted and the job deleted. The LPD protocol will cause the remote host to sent the job again
later on.
Shutdown/reboot
All jobs of the printer spool queue will be restored after a restart/reboot/shutdown of the
controller.
The LPD protocol will handle the recovery of jobs that were only partially received. The sending
host will retransmit them when the controller becomes available again.
Priority in case of multiple print files
Multiple files that are submitted by one lpr command are treated as multiple jobs on the
imagePRESS C7010VPS series. Multiple files are printed in the order they were submitted and
jobs submitted through another interface will not be printed in between.
Job size
A job can only be printed if it fits in the queue. If the job is too big for the spool area, the
controller will not be able to accept it. The job then remains blocked in the lpd queue on the
remote host.
If the job size is set to 0 or to a value above 125*10^12, the LPD supposes that the job size is
unknown. In this case the job is always processed as a streaming job.
Job ID
The Job ID that is shown to the user via lpq is the Job ID the Controller has assigned to the job,
not the Job ID the remote host originally assigned to it.
This is NOT conform to the RFC standard. The Job ID that is displayed should be the one
generated by the remote host.
Any application that stores the Job ID for future reference (e.g. print servers) will have problems
tracking the jobs' progress. These applications consider the job as disappeared while the job is
still queued but under a different Job ID. Also, an lprm using the stored Job ID will fail.
LPD behaviour
44 Chapter 3 - The LPD connection
imagePRESS C7010VPS series v2.2