Job and Document Identifiers

Many commands accept job identifiers as input. Job identifiers (LocalJobID and GlobalJobID) are specific arguments for some commands. Local IDs are generated for each user, on each host, for each job.

A job can be referenced by either a local ID or global ID number:

A local ID is represented as a single integer generated by the client. For example:
10
A ServerName, a colon (:), and a number generated by the server represents a global ID. For example:
server1:1019198802

Only you (the person who submits the job) can use the local job ID.
If you omit the server name from the command, the client assumes that the job identifier is a local ID.
You must be authorized to modify jobs belonging to another person and must always use the global ID to do so. See “Authorization ” for further information.

Specific Documents within Jobs

A subset of the commands that accept a job-identifier parameter also permit you to specify a specific document number within a multiple-document job. The document number, if present, is separated by a period (.) from the job identifier. Within each multiple-document job, the documents are numbered starting with 1.

An example of a local ID for document number 1 is:

10.1

An example of a global ID for document number 3 is:

SPOOL1:1022565604.3

Job and Document Identifiers

Technical documentation

» Table of Contents

» Index

Specific Documents within Jobs