XEROX-JOB-MONITORING-MIB :: xcmJobProcessAfter

MIB Reference — IPNetwork Monitor · Updated September 12, 2026

All MIBsXEROX-JOB-MONITORING-MIBxcmJobProcessAfter

xcmJobProcessAfter

Module: XEROX-JOB-MONITORING-MIB

OID (symbolic): XEROX-JOB-MONITORING-MIB::xcmJobProcessAfter

OID (numeric): 1.3.6.1.4.1.253.8.59.15.1.1.1

Node type: OBJECT-TYPE

Type: DateAndTime

Access: read-only

Description: Specifies the calendar date and time of day after which the server is to process the job on the specified device. The server shall hold the job in the held state until the specified date and time.

NOTE: In this MIB, this object applies to any type of job, not just print jobs and so this object is a generalization of the ISO DPA attribute which is only for print jobs.

ISO DPA: Job-print-after This attribute specifies the calendar date and time of day after which the print-job shall become a candidate to be scheduled for printing [processing].

If the value of this attribute is in the future, the server shall set the value of the job's current-job-state to held and add the job-print-after-specified value to the job's job-state- reasons attribute and shall not schedule the print-job for printing until the specified date and time has passed. When the specified date and time arrives, the server shall remove the job-print-after-specified value from the job's job-state- reason attribute and, if no other reasons remain, shall change the job's current-job-state to pending so that the job becomes a candidate for being scheduled on printer(s).

[For purposes of this MIB, the agent shall return the DEFVAL if the job did not specify this attribute and disregard the next paragraph.] The server shall assign an empty value (see DPA 9.1.2) to the job-print-after attribute when no print after time has been assigned, so that the job shall be a candidate for scheduling immediately.

What is xcmJobProcessAfter?

This read-only DateAndTime specifies the date and time after which the job becomes eligible for processing, before which the server holds it in the held state; an all-zero value means no such restriction was specified. An admin sees a job held with this reason as expected behavior for a deliberately delayed print (such as an overnight batch job) rather than a fault.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.253.8.59.15.1.1.1
snmpwalk -v2c -c public <target> XEROX-JOB-MONITORING-MIB::xcmJobProcessAfter

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.253.8.59.15.1.1.1.1
snmpget -v2c -c public <target> XEROX-JOB-MONITORING-MIB::xcmJobProcessAfter.1

Start monitoring Xerox network printers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XEROX-JOB-MONITORING-MIB::xcmJobProcessAfter OID value, configure state conditions and alerts, and monitor any Xerox network printers from a single console.

OID Breakdown

Upper-level ancestors (12 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.253xeroxXEROX-COMMON-MIB
1.3.6.1.4.1.253.8xeroxCommonMIBXEROX-COMMON-MIB
1.3.6.1.4.1.253.8.59xcmJobMonMIBXEROX-COMMON-MIB
1.3.6.1.4.1.253.8.59.15xcmJobGenSpoolingExtXEROX-COMMON-MIB
1.3.6.1.4.1.253.8.59.15.1xcmJobGenSpoolingExtTableXEROX-COMMON-MIB
1.3.6.1.4.1.253.8.59.15.1.1xcmJobGenSpoolingExtEntryXEROX-COMMON-MIB
Numeric OIDNameModule
1.3.6.1.4.1.253.8.59.15.1.1.1xcmJobProcessAfterXEROX-JOB-MONITORING-MIB