All MIBs › XEROX-JOB-MONITORING-MIB › xcmDevicesAssignedTable
xcmDevicesAssignedTable
Module: XEROX-JOB-MONITORING-MIB
OID (symbolic): XEROX-JOB-MONITORING-MIB::xcmDevicesAssignedTable
OID (numeric): 1.3.6.1.4.1.253.8.59.7.1
Node type: OBJECT-TYPE
Access: not-accessible
Description:
This table contains the hrDeviceIndex values and states of the device(s) to which this job has been assigned, if the job has been assigned to a physical device by the job service provider. If the job service provider has not (yet) assigned the job to a device, there shall not be any rows in this table for the job. Some implementations assign jobs to physical devices when the job is submitted which is called early binding. Other implementations delay assigning jobs to physical devices until the physical device is ready to accept another job which is called late binding. Late binding is used when load balancing between several physical devices.
NOTE: Some systems may assign a job to more than one device and progress part of the job on each. Therefore, the device state is represented as a table. For example, print systems that only assign a job to a single printer, need only implement a single row of this table. As another example, multifunction devices/systems that scan and print, in order to implement a copy service may either: 1. assign a simple job to at least two devices: a scanner and a printer or 2. create a compound job with a single device assigned to each contained sub-job.
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4 | private | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4.1 | enterprises | ANIROOT-MIB |
| 1.3.6.1.4.1.253 | xerox | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8 | xeroxCommonMIB | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59 | xcmJobMonMIB | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.7 | xcmDevicesAssigned | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.7.1 | xcmDevicesAssignedTable | XEROX-JOB-MONITORING-MIB |
FAQ
Why is xcmDevicesAssignedTable empty for a job I just submitted?
Some print systems use late binding — they don't assign a job to a physical device until that device is actually free and ready to print, which supports load balancing across a pool of printers. If a job hasn't been picked up by a device yet, there simply won't be a row for it in this table; check back once the job leaves the queue.
A job I submitted shows up assigned to two different devices in this table — is that a bug?
Not necessarily. Some systems split a job across more than one physical device and track the progress of each part separately — for example, a copy job on a multifunction system might assign the scan portion to one device and the print portion to another. Multiple rows for the same job are how the MIB models that.