XcmJMJobStateReasons

  • Base type Integer32
  • Range 0 — 2147483647

This representation is bit-encoded, so that multiple reasons can occur at once. Each bit corresponds to an ISO DPA OID for the same reason. The MIB enum value is given by: value = 2 ** (last arc of DPA id-val-reasons-xxx OID -1) id-val-reasons-documents-needed = 1.0.10175.1.6.19.1 See the Xerox Job Model Specification, Phase 1 or later for the specification of which job-state-reasons values may be used with which job states. ISO DPA: Job-state-reasons This attribute identifies the reason or reasons that the job is in the held, [processing,] terminating, retained, or completed state. The server shall indicate the particular reason(s) by setting the value of the job-state-reasons attribute. When the job is not in any of these states, the server shall set the value of the job-state-reasons attribute to the empty set. The following standard values are defined: jobIncoming 0x1 The job has been accepted by the server or device, but the server or device is expecting (1) additional operations from the client to finish creating the job and/or (2) is accessing/accepting document data. NOTE - this reason has been renamed from the ISO DPA 'documents-needed' to the IPP 'job-incoming' which has been generalized to include the condition before the job has been closed by the client. (id-val-reasons-documents-needed) jobHoldSet 0x2 The value of the job's job-hold attribute is TRUE. (id-val- reasons-job-hold-set) jobProcessAfterSpecified 0x4 The value of the job's job-process-after attribute has specified a time specification that has not yet occurred. Renamed from ISO DPA job-print-after-specified. (id-val- reasons-job-process-after-specified) requiredResourcesNotReady 0x8 At least one of the resources needed by the job, such as media, fonts, resource objects, etc., is not ready on any of the physical device's for which the job is a candidate. (id-val-reasons-required-resources-not-ready) successfulCompletion 0x10 The job completed successfully. (id-val-reasons-successful completion) completedWithWarnings 0x20 The job completed with warnings. (id-val-reasons-completed- with-warnings) completedWithErrors 0x40 The job completed with errors (and possibly warnings too). (id-val-reasons-completed-with-errors) cancelledByUser 0x80 The job was cancelled by the user using the CancelJob request. (id-val-reasons-cancelled-by-user) cancelledByOperator 0x100 The job was cancelled by the operator using the CancelJob request. (id-val-reasons-cancelled-by-operator) abortedBySystem 0x200 The job was aborted by the system. (id-val-reasons-aborted- by-system) logfilePending 0x400 The job's logfile is pending file transfer. (id-val- reasons-logfile-pending) logfileTransferring 0x800 The job's logfile is being transferred. (id-val-reasons- logfile-transferring) The following bits are from IPP (and start at the high end of the bits definitions): jobOutgoing 0x40000000 Configuration 2 only: The server is transmitting the job to the device. The remaining bits are reserved for future standardization and shall not be used by conforming implementations. This is the equivalent of a type 2 enum.