pdresume command: enables paused objects to resume operation

Syntax

pdresume [-H host:port] [-c ObjectClass] [-m "MessageText"]     
[-x "attribute=value …"] [-X AttributesFileName]     
{LocalJobID … | GlobalJobID … |     
ServerName … | [ServerName:]DestinationName … |     
[ServerName:]QueueName …}

pdresume -h

Description

Use the pdresume administrative command to cause InfoPrint to restart paused jobs, actual destinations, queues, or servers.

Note: Use the pdresume and pdpause commands to allow or prevent output from the object, whereas you use the pdenable and pddisable commands to allow or prevent input to the object.

Flags

You can use these flags with the pdresume command:

-H host:port

Identifies the host and port of the InfoPrint Manager server used for communication. When not specified, the command follows the Configuration logic to define the host and socket.

-c {destination | queue | job | server} DEFAULT=destination
Specifies the object class you want for this command. In the valid classes, destination is an actual destination.
    Note:
  • You cannot resume PSF upload-TCP/IP-attached physical printers.
  • You cannot resume an AnyPlace queue

Using this flag is equivalent to specifying the command attribute operation-class.

-m "MessageText"
Specifies the message you want associated with the specified destination, queue, job, or server. You can use this message to indicate the reason for resumption or to provide any other comments.

When resuming a server, InfoPrint propagates the message to the message attribute of the actual destinations and queues residing in the server. InfoPrint does not change the server message attribute.

If the command operates on a job, you can list this message by specifying requested-attributes=job-message-from-administrator with the pdls command. If the command operates on a destination, queue, or server you can list this message by specifying requested-attributes=message with the pdls command.

If you do not specify the -m flag, the message already stored with the object remains unchanged.

Using this flag is equivalent to specifying the command attribute message.

-x "attribute=value …"
A single attribute string, consisting of one or more attribute-value pairs.
-X AttributesFileName
Specifies the name of a file containing attribute and value pairs that you want InfoPrint to insert at the current point in the command.

Using this flag is equivalent to specifying the command attribute attributes.

-h
Displays a command-specific help message containing information about command syntax and flags. If you use this flag with any other flag or attribute, InfoPrint recognizes only the -h flag.

Configuration logic

The command determines which server host and server port to use based on this sequence:

  1. Server host and server port specified with the -H parameter.
  2. Server host and server port specified with the PDHOST and PD_SOCKET envirnonment variables.
  3. Uses the defaults for PDHOST=localhost and PD_SOCKET=6874.
Note: This configuration logic enables multiple commands to run on a single machine communicating with one or more InfoPrint Manager servers.

Command attributes

You can specify these attributes in a -x "attribute=value …" string or in an attributes file designated with the -X AttributesFileName flag.

attributes=AttributesFileName
Specifies the designated attributes file that InfoPrint reads and inserts at the current point in the command. This file contains attribute and value pairs that InfoPrint uses to expand the command.
operation-class={destination | queue | job | server} DEFAULT=destination
Specifies the object class you want for this command. In the valid classes, destination is an actual destination.
    Note:
  • You cannot resume PSF upload-TCP/IP-attached physical printers.
  • You cannot resume an AnyPlace queue.
message="MessageText"
Specifies the message you want to associate with the specified destination, queue, job, or server. You can use this message to indicate the reason for resumption or to provide any other comments.

When resuming a server, InfoPrint propagates the message to the message attribute of the actual destinations and queues residing in the server. InfoPrint does not change the server message attribute.

If the command operates on a job, you can list this message by specifying requested-attributes=job-message-from-administrator with the pdls command. If the command operates on a destination, queue, or server, you can list this message by specifying requested-attributes=message with the pdls command.

If you do not specify the message attribute, the message already stored with the object remains unchanged.

Arguments

Use the argument value to identify the specific destination, queue, job, or server you want to start processing again (resume operating). If you specify multiple objects, all of the objects must belong to the same class and you must separate the object names with spaces.

You can use these arguments with the pdresume command:

LocalJobID… or GlobalJobID
Specifies the job you want to resume as determined by a local job identifier or global job identifier. In most cases, someone other than the job submitter will resume a job and must identify it by the global job ID. Job submitters who do have authority to resume jobs can identify their own jobs by the local job ID.

A resumed job does not automatically return to its previous state. For example, if the job-hold or print-after attributes of a paused job were modified, returning to its previous state would cause InfoPrint to hold the job even after it was resumed.

Resuming a job that was not previously assigned to an actual destination allows InfoPrint to schedule it.

Resuming a job that was processing when it was paused causes InfoPrint to restore it to the pending state and try to schedule it on the original actual destination. If the original destination is not available, InfoPrint schedules the job on another actual destination that can support the job checkpoint format and begins processing the job where it stopped. If InfoPrint cannot find another actual destination that supports the checkpoint format, InfoPrint places the job in the held state. You can resubmit the job, which means that InfoPrint will start the job from the beginning.

Resuming a job that had any attributes modified while it was paused causes it to restart from the beginning.

[ServerName:]DestinationName
Specifies the destination you want to resume operation.

Resuming an actual destination allows it to start processing jobs that InfoPrint has assigned to it.

[ServerName:]Queue
Specifies the queue you want to resume operating.

Resuming a queue resumes the distribution of jobs to actual destinations associated with that queue.

ServerName
Specifies the server on which you want the command to operate. A server does not have a paused state. Issuing the command to a server resumes all of the paused queues and actual destinations that are located in that server. The queues can then continue to distribute jobs to actual destinations; and the actual destinations can start processing jobs.

Examples

  • Resume an actual destination

    To resume actual destination Csrv-pp and issue a message, enter the command:

    pdresume -m "Toner refilled" Csrv-pp

  • Resume a queue

    To resume the queue Div1-q, enter the command:

    pdresume -c queue Div1-q

  • Resume all queues and actual destinations in a server

    To resume all of the queues and actual destination in the server Mrk-server3, enter the command:

    pdresume -c server Mrk-server3

Suggested reading

For more information, see Attributes file.