Change the default medium for the third document of job 1 on the default spooler

pdmod -x "default-medium=a" 1.3

10. pdpause

Name

pdpause - pause a job, physical printer, queue, or spooler.

Synopsis

pdpause [-c class_name] [-m message_text] [-x extended_attribute_string ... ]

[-X attribute_filename ... ] object_instance ...

Use this command to display help about pdpause.

pdpause -h

Description

Use the pdpause command to pause a pending or held print job, a physical printer, a queue, or a spooler. The following items should be considered when using this command:

• If you specify any other object or an invalid object, such as a logical printer or a supervisor, an error results. Specifying an object that is already paused also results in an error.

• The current state of the object is changed to paused. Using the pdls or the pdq command will list the state of the object.

• You may pause both enabled and disabled objects.

• A paused object can be resumed using the pdresume command.

• Although paused physical printers, queues, and spoolers do not process jobs, they can continue to accept and respond to requests such as pdls.

• When the paused object is a job:

— Only pending or held jobs can be paused

— A specific document within the job cannot be paused.

— There is no time limit for how long a job can be paused. A paused job will not print until it is resumed.

— A job cannot be rescheduled until it is resumed.

— The command fails if the job was already submitted to the supervisor for printing.

PDPAUSE

• When the paused object is a physical printer:

— When paused, it stops printing as soon as possible. When resumed, it continues printing from where it left off.

— Some printing devices can stop printing in the middle of a job when the printer is paused. When the printer is resumed, the job continues printing. There is no need to resubmit the job.

— Some printing devices cannot stop printing in the middle of a job when the printer is paused. Even though the printer is paused, the current job finishes printing before the pdpause command takes effect.

— While it is in the paused state, the spooler associated with the printer will not schedule new jobs.

— If the printer is not printing when paused, it still needs to be resumed in order to start printing again.

— Jobs sent to a paused printer will not be scheduled until the printer resumes printing.

• When the paused object is a queue:

— A paused queue will not submit jobs to associated physical printers.

— The state of each logical printer associated with the queue does not change, but jobs submitted will be in a pending state.

— The state of each job currently in the paused queue does not change.

• When the paused object is a spooler:

— It will not submit jobs to supervisors.

— The logical printers associated with the spooler continue to accept new jobs.

access level End user. End users can use pdpause to pause their own jobs.

Operator. Operators can use pdpause on jobs, physical printers, queues, and spooler objects.

PDPAUSE

Options

The following options are supported for pdpause.

-c class_name

This option specifies the class, or type, of object that is to be paused.

arguments The values allowed for class_name are the following:

• printer (Physical printer only.) The default value.

• job

• queue

• server (Spooler only.)

Note: The OPERANDS section describes the specific object_instance that is associated with each class.

If you use the -x string option or the -X file option, the comparable attribute type and value is the following:

class=class_name

-m message_text

Use this option to include a message about the object that you are pausing. For example, when a physical printer is to be paused, the message attached to the printer might be:

-m "Printer1 paused, not currently printing jobs."

If you use the -x extended-attribute-string option or the -X

attribute_filename option in the pdpause command, the comparable client attribute type and value is the following:

For physical printers, queues, and spoolers:

message=message_text For jobs:

job-message-from-administrator=message_text The option will look like this:

-x "message= 'Printer1 paused, not currently printing jobs' "

To retrieve a message of this type, use the pdls command, specify the job or document, and include the following option:

-r message

PDPAUSE

-x extended_attribute_string

Use this option to specify a series of attribute=value pairs on the command line that will be processed by the pdpause command.

attributes Object attributes cannot be used in the -x option.

You can specify the following client attributes:

• attributes

• class

• message

syntax Follow the syntax rules for attribute value strings listed in the Overview chapter of the PrintXchange Command Line Interface Reference Guide.

Note: You can produce the same result by including the

extended_attribute_string in an attribute file and identifying that file as the attribute_filename in the -X option.

-X attribute_filename

The -X option identifies an attribute file to be read by the command.

When the pdpause command executes, the attribute data included in the file is processed at the current point in the command line as though it had been specified with the -x option.

attributes Object attributes cannot be used in the -X option. Refer to the -x section for a list of the client attributes that may be used.

Note: Refer to the Overview chapter of the PrintXchange Command Line Interface Reference Guide for information on developing an attribute file.

PDPAUSE

Operands

The value of the object_instance in the operand is based on the value of the -c class_name option or the class=class_name attribute.

Note: Multiple objects of the same class can be paused simultaneously by specifying multiple object instances.

printer_name ... When class equals printer, the value of printer_name is the name of the physical printer to be paused.

Note: Although you cannot pause a logical printer, you can use the pddisable command to prevent a job from being submitted through a logical printer.

[spooler_name:]job_id ... When class equals job, the value of job_id is the unique identifier that points to the job that is to be paused.

Note: If [spooler_name:] is not specified, the default spooler is assumed.

queue_name ... When class equals queue, the value of queue_name is the name of the queue to be paused.

spooler_name ... When class is server, the value of spooler_name is the name of the spooler to be paused.

PDPAUSE

Examples