pdresubmit command: resubmits jobs

Syntax

pdresubmit [-H host:port] [-c ObjectClass] [-g] [-i][-r "RequestedAttribute …"] 
[-s StyleName] 
[-x "attribute=value …"] [-X AttributesFileName] 
[ServerName:]TargetLogicalDestinationName 
{LocalJobID … | GlobalJobID … | 
[ServerName:]QueueName … | 
[ServerName:]DestinationName …}

pdresubmit -h

Description

Use the pdresubmit command to resubmit an existing job to a specific logical destination. The logical destination can be in the same server as the logical destination to which the job was first submitted or a different server. You can only resubmit jobs that have the current job state of held, pending, retained, or unknown.

If the logical destination specified is in a different server, the old server resubmits the job with all of its current attributes to the new server. InfoPrint includes any default attributes associated with the old server so that the new job remains as similar as possible to the old job. If the new server accepts the job, it assigns a new global job identifier and the old global job identifier becomes not valid.

When you specify the -i flag, InfoPrint Manager deletes all the attributes with values in the default job and default document referenced by the current logical destination attributes destination-initial-value-job and destination-initial-value-document from the job and the job documents. The InfoPrint Manager server updates the job and document objects with the attribute values from the target destination default objects.

Logical destinations and queues can also be arguments for this command. If a logical destination is the argument, InfoPrint resubmits all of the jobs submitted to the old logical destination to the specified new logical destination. If a queue is the argument, InfoPrint resubmits all of the jobs in the old queue to the specified logical destination. InfoPrint validates all of the resubmitted jobs again. If the newly specified logical destination does does not support them, they remain in the queue that they were in originally.

If the new logical destination cannot accept the job for some reason, InfoPrint issues an error message and the job stays where it was.

Note:

InfoPrint does not change the global job identifier for the job if you resubmit the job to a logical destination on the same server.
InfoPrint changes the global job identifier for the job if you resubmit the job to a logical destination on a different server. However, if you are the job-owner, you can still use the same local job identifier.
The resubmit job request is rejected if the move is to another server and the document format is dpf-ipds.

Flags

You can use these flags with the pdresubmit command:

-Hhost: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 {job | queue | destination} DEFAULT=job

Specifies the object class that you want for this command. In the valid classes, destination only applies to logical destinations.

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

-g

Turns off headings.

Using this flag is equivalent to specifying the command attribute headings=false.

-i

Resets the job and document attributes default values.

Using this flag is equivalent to specifying the command attribute ignore-ivo=true.

When the target destination is on the same server, these apply:

Before moving the job to the new destination, InfoPrint Manager does not delete the document-format attribute from the job documents attributes.
The InfoPrint Manager server does not update the job-scheduling attribute. The job-scheduling attribute indicates how the associated job is scheduled.
InfoPrint Manager server attempts to recalculate job-page-count and total-job-octets attributes.
InfoPrint Manager server sets a retention period attribute only if one is not already set in the job. The retention period attributes are job-retain-until (Job only), job-retention-period and retain-forever.

-r {none | briefverbose} DEFAULT=none

Specifies the group of attributes you want InfoPrint to display for the specified job, queue, or destination.

none: Displays no attributes.
brief: Displays a small subset of important attributes for each object.
verbose: Displays a larger subset of important attributes for each object.

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

-s {column | doccol | line} DEFAULT=column

When combined with the -r flag or the requested-attributes command attribute, this flag specifies the format in which you want the attributes displayed.

column: Attribute values are displayed in tabular format, so that values of the same attribute for multiple objects line up in columns.
doccol: For jobs only, job attribute values and the document attribute values for the first document in the job are displayed in column format on the same line.
line: Each attribute is displayed on a separate line.

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

-x"attribute=value …"

Consists of a single attribute string, containing one or more attribute-value pairs.

-XAttributesFileName

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:

Server host and server port specified with the -H parameter.
Server host and server port specified with the PDHOST and PD_SOCKET envirnonment variables.
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 …" 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={job | queue | destination} DEFAULT=job

Specifies the object class you want for this command. In the valid classes, destination only applies to logical destinations.

headings={true | false} DEFAULT=true

Specifies whether you want InfoPrint to display headings for the requested attributes.

requested-attributes={none | briefverbose} DEFAULT=none

Specifies the group of attributes you want InfoPrint to display for the specified job, queue, or destination.

none: Displays no attributes.
brief: Displays a small subset of important attributes for each object.
verbose: Displays a larger subset of important attributes for each object.

style={column | doccol | line} DEFAULT=column

Specifies the format that you want InfoPrint to display the attributes in.

column: Attribute values are displayed in tabular format, so that values of the same attribute for multiple objects line up in columns.
doccol: For jobs only, job attribute values and the document attribute values for the first document in the job are displayed in column format on the same line.
line: Each attribute is displayed on a separate line.

Arguments

Use the argument value to identify the specific object you want to resubmit. If you specify multiple objects, all must belong to the same class and you must separate the object names with spaces.

You must use this argument:

[ServerName:]TargetLogicalDestinationName: Specifies the name of the new logical destination.

You must use one of these arguments with the pdresubmit command:

LocalJobID or GlobalJobID: Specifies the job you want resubmitted as determined by a local or global job identifier. In most cases someone other than the job submitter will resubmit a job and must identify it by the global job ID. Job submitters who do have permission to use pdresubmit, either because they belong to the printq group or because the file permissions have been changed, can identify their own jobs by the local job ID.
[ServerName:]DestinationName: Causes InfoPrint to resubmit to the target logical destination all jobs currently submitted to the specified logical destination.
[ServerName:]QueueName: Causes InfoPrint to resubmit to the target logical destination all jobs that are currently in the specified queue.

Examples

Resubmit jobs
To resubmit jobs server1:1098223002 and server2:1099223003 to logical destination local-lp, enter the command:
```
pdresubmit local-lp server1:1098223002 server2:1099223003
```
Resubmit jobs to a new logical destination and replace the default values
To resubmit job server1:1098223004 from logical destination dept1-lp to logical destination local-lp and to ask to reset the dept1-lp default values and to retrieve the local-lp default values, enter the command:
```
pdresubmit -i local-lp server1:1098223004
```
Resubmit all jobs from one logical destination to another
To resubmit all jobs submitted to logical destination dept1-lp to logical destination local-lp, enter the command:
```
pdresubmit local-lp -c destination dept1-lp
```

RICOH InfoPrint Manager™ for Linux