All MIBs › XEROX-JOB-MONITORING-MIB › xcmDocFormat
xcmDocFormat
Module: XEROX-JOB-MONITORING-MIB
OID (symbolic): XEROX-JOB-MONITORING-MIB::xcmDocFormat
OID (numeric): 1.3.6.1.4.1.253.8.59.12.1.1.6
Node type: OBJECT-TYPE
Type: XcmPrtInterpreterLangFamily
Access: read-only
Description: The interpreter language family enum value registered by IANA is used according to the Printer MIB (RFC 1759). See prtInterpreterLangFamily. For the Job Monitoring MIB, an index into the prtInterpreterTable is not used, since the exact format of the document need not conform exactly to one of the printer's intepreters and, furthermore, the device need not even be a printer (so that the Printer MIB need not be used for non-printers).
For scan-to-file jobs, the xcmDocFormat object specifies the document format desired as a result of the scan.
ISO DPA: Document-format This attribute identifies the overall print document format used for the document. It consists of three elements, a document-format, a document-format-variants and a document- format-version. The latter two elements are optional. The document-format element identifies a particular family of document formats, of which there may exist several versions or variants. The document-format-variants and document-format-
version elements identify a specific instance of a document format. The variant refers to a particular functional subset of a format. For example, the format PostScript has variants of level 1 and level 2, and the format PCL has several variants, including PCL4 and PCL5. The version distinguishes among successive releases of the same basic format and variant. For example, successive versions of Xerox Interpress include versions 2.0, 2.1, 3.0, 3.1, etc.
What is xcmDocFormat?
This read-only object identifies the document's overall print-language family (e.g. PostScript, PCL) using the IANA-registered interpreter-language enum from the Printer MIB, or for scan-to-file jobs, the desired output format of the scan. An admin checks this when a document fails to print correctly, to confirm the device actually supports the document's format, such as PCL versus PostScript.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.253.8.59.12.1.1.6 snmpwalk -v2c -c public <target> XEROX-JOB-MONITORING-MIB::xcmDocFormat
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.253.8.59.12.1.1.6.1 snmpget -v2c -c public <target> XEROX-JOB-MONITORING-MIB::xcmDocFormat.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::xcmDocFormat 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-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.12 | xcmDocGenBasic | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.12.1 | xcmDocGenBasicTable | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.12.1.1 | xcmDocGenBasicEntry | XEROX-COMMON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.253.8.59.12.1.1.6 | xcmDocFormat | XEROX-JOB-MONITORING-MIB |