The job identifier generated on the system that the agent is instrumenting. The job identifier is generated by the job service provider when it accepts a submit job request from a job service requester using whatever job submission protocol that the job service provider supports.

This job identifier is for each job and sub job submitted. The job service provider promote a simple job request to a compound job, if the job service needs access to multiple devices, such as a scanner and a printer or to two printers, or to a printer and a fax. See the textual conventions for a more complete description of compound jobs.

The xcmJobIdentifierOnSystem is used as one of the indexes into each job and document table, along with the HrDeviceIndex from the Host Resources MIB which is an index value for each different job service instance (analogous to each instance of a logical printer in ISO DPA).

NOTE: Different jobs on different systems may have the same job identifier. Additional information is needed to make the job identifier unique in the network, such as the server or system component name.

See also xcmJobIdentifierUpstream in this group.

ISO DPA: Job-identifier This attribute provides the job-identifier for this job on the server. The server shall generate a job-identifier value that

is unique on that server, but need not be unique across the distributed environment. [In other words, the server's name need not be part of the job-identifier.]

The value of the job-identifier attribute shall be returned by the server as part of the PrintResult in the first Print operation for the job (see 8.2.1). The client shall pass its value as part of the PrintArgument in subsequent Print operations for the same job.