HP Distributed Print Service Administration Guide

Chapter 11 341

Managing Jobs and Supporting Users

Managing Jobs in Queues and Spoolers

Holding a Job

You can hold a job to prevent it from printing for a period of time. An

example might be if a job was submitted and then an error was

discovered in the job. If the -l ﬂag was used with the pdpr command

when the job was submitted, you could hold the job, make the correction

to the source ﬁle, and then release the job. Another example would be if

someone needed to be at the printer device when the job printed; the job

might contain conﬁdential information. Held jobs advance in the queue.

When the appropriate person is at the printer device and the held job is

ﬁrst in the queue, you can release the hold and HPDPS prints the job.

To hold job Spool3:3957400034, enter:

pdmod -x "job-hold=yes" Spool3:3957400034

The value for the current-job-state job attribute changes to held and

the reason, as speciﬁed by the job-state-reasons attribute, is

job-hold-set. Refer to Table 11-3 for a description of these job status

attributes.

A held job remains in the queue indeﬁnitely until the value of the

job-hold is set back to no. The only exception is if the job has a value

speciﬁed for the job-discard-time attribute. If this attribute has a

value, HPDPS discards the job at the speciﬁed time, even if the job is

held.

Releasing a Held Job

Releasing the hold on a job allows HPDPS to schedule the job for

printing.

To release the hold on job Spool3:3957400034, enter:

pdmod -x "job-hold=no" Spool3:3957400034

Assigning a Retention Period for a Job

A user might request that you retain a job in the spooler. They might

want to check the printed output and, if the output is correct, resubmit

the job and specify several copies.

To assign a retention period of two hours for the job Spool2:3947600212,

enter:

pdmod -x "job-retention-period=2:00" Spool2:3947600212