XEROX-JOB-MONITORING-TC
AI MIB Summary
The XEROX-JOB-MONITORING-TC module provides standardized textual conventions and explanatory definitions for the Xerox Job Monitoring MIB to facilitate the precise tracking of printer and multifunction device job states, status codes, and lifecycle events. By decoupling these data type definitions from the core MIB, the module ensures stable SNMP-based monitoring of Xerox print subsystems without requiring version updates to the primary management information base.
File: 40jobtc.dfm, .mib, .pdf, .txt Version: 5.11.pub This textual-convention module defines textual- conventions for use with the Job Monitoring MIB, module: XEROX-JOB-MONITORING-MIB. Also the explanatory material with this module explains the Job Monitoring MIB. These textual-conventions and explanations are in a separate module from the Job Monitoring MIB, so that they may be republished when additional enums are added or more explanatory material is added without needing to republish the Job Monitoring MIB, thus increasing the stability of the Job Monitoring MIB. Copyright 1996-2002 Xerox Corporation. All Rights Reserved.
Main OID:
xcmJobMonTC.1.3.6.1.4.1.253.8.58
27
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
xcmJobMonTCFile: 40jobtc.dfm, .mib, .pdf, .txt Version: 5.11.pub This textual-convention module defines textual- conventions for use with the Job Monitoring MIB, module: XEROX-JOB-MONITORING-MIB. Also the explanatory material with this module explains the Job Monitoring MIB. These textual-conventions and explanations are in a separate module from the Job Monitoring MIB, so that they may be republished when additional enums are added or more explanatory material is added without needing to republish the Job Monitoring MIB, thus increasing the stability of the Job Monitoring MIB. Copyright 1996-2002 Xerox Corporation. All Rights Reserved. MODULE-IDENTITY .1.3.6.1.4.1.253.8.58 |
xcmJobServiceTypesOIDThe root of all job service type OIDs defined in the Job Monitoring MIB TC. Also use these same OIDs for Xerox extensions to ISO DPA. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2 |
xcmJobServiceScanToFileOIDScan-to-file The scan-to-file job service scans one or more documents and stores the result in one or more (1) local files, (2) files in a distributed file system or (3) files in a document repository, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.1 |
xcmJobServiceScanToPrintOIDScan-to-print The scan-to-print job service scans one or more documents and prints the results on a local printer or on a network printer, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.2 |
xcmJobServiceScanToFaxOIDScan-to-fax The scan-to-fax job service scans one or more documents and faxes the results using a local fax or on a network fax, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.3 |
xcmJobServiceScanToMailListOIDScan-to-mail-list The scan-to-mail-list job service scans one or more documents and distributes the results using the distribution list specified by the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.4 |
xcmJobServiceFaxToFileOIDFax-to-file The fax-to-file job service accepts one or more documents via inbound fax and stores the result in one or more: (1) local files, (2) files in a distributed file system or (3) files in a document repository, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.5 |
xcmJobServiceFaxToPrintOIDFax-to-print The fax-to-print job service accepts one or more documents via inbound fax and prints the results on a local printer or on a network printer, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.6 |
xcmJobServiceFaxToMailListOIDFax-to-mail-list The fax-to-mail-list job service accepts one or more documents via inbound fax and distributes the results using the distribution list specified by the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.7 |
xcmJobServicePrintOIDPrint The print job service accepts one or more documents submitted with the job print service request, referenced from the job request in a distributed file system or document repository and prints on a network printer, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.8 |
xcmJobServiceFileToFaxOIDFile-to-fax The file-to-fax job service accepts one or more documents submitted with the job print service request, referenced from the job request in a distributed file system or document repository and faxes the results using a local fax or on a network fax, depending on the prescriptive instructions submitted with the job service request. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.9 |
xcmJobServiceFileToMailListOIDFile-to-mail-list The file-to-mail-list job service accepts one or more documents submitted with the job service request, referenced from the job request in a distributed file system or document repository and distributes the results using the distribution list specified by the prescriptive instructions submitted with the job service request. The file-to-mail-list service permits a user to compose a compound job whose sub-job produces a file, such as a scan-to-file, and whose subsequent sub-jobs use the file as input, such as a sub-job to file-to-mail-list and a second (parallel) sub-job to print from the same file. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.10 |
xcmJobServiceCopyOIDCopy The copy job service reads images (via xerography, scanner, etc.) and writes (prints) those images (with a pipeline delay of zero or more images) on a local marker sub-unit (copy service need NOT write a disk or other secondary storage file of the copy images). Compare with 'xcmJobServiceScanToPrint' (strictly used for digital scanners - scan to print service shall ALWAYS write a disk or other secondary storage file of the whole document, i.e., the set of copy images). The key distinction, from an Image Processing point of is that, for a copy (or local copy) job the IIT (input - scan) and IOT (output - marker) are WELL-TUNED with respect to each other to produce the best quality and the best performance. Whereas for ScantoPrint the target IOT (or the its capabilities) are not assumed to be known at the time scanning and in order to achieve best quality, there is often an additional step of image processing that the systems needs to go through (often called Image Interoperability Services). Usage: A copy job service shall ALWAYS expose an 'xcmHrDeviceCopier' (scanner and marker are invisible) in the IETF HR MIB, XCMI HRX MIB, and XCMI Job Monitoring MIB. Usage: A scan to print job service shall ALWAYS expose an 'xcmHrDeviceScanner' and an 'hrDevicePrinter' (marker) in the IETF HR MIB, XCMI HRX MIB, and XCMI Job Monitoring MIB. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.11 |
xcmJobServiceFileToFileOIDFile-to-file The file-to-file job service accepts one or more documents submitted with the job print service request, referenced from the job request in a distributed file system or document repository and stores the result in one or more: (1) local files, (2) files in a distributed file system or (3) files in a document repository, depending on the prescriptive instructions submitted with the job service request. The initial intent of this job service is support the transfer of a file to a device's hard drive. When the file transfer is complete, the file-to-file job is complete. It is expected that a user will eventually process the file from the device hard drive, but that action starts a new job. This service might be used in the processing of a secure-print action. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.2.12 |
xCmJobMonTCDummy OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.58.999 |
xCmJobMonTCJobServiceTypeOIDDummy - DO NOT USE XcmJMJobServiceTypeOID .1.3.6.1.4.1.253.8.58.999.1 |
xCmJobMonTCJobStateDummy - DO NOT USE XcmJMJobState .1.3.6.1.4.1.253.8.58.999.2 |
xCmJobMonTCJobStateReasonsDummy - DO NOT USE XcmJMJobStateReasons .1.3.6.1.4.1.253.8.58.999.3 |
xCmJobMonTCJobXStateReasonsDummy - DO NOT USE XcmJMJobXStateReasons .1.3.6.1.4.1.253.8.58.999.4 |
xCmJobMonTCJobX2StateReasonsDummy - DO NOT USE XcmJMJobX2StateReasons .1.3.6.1.4.1.253.8.58.999.5 |
xCmJobMonTCDocTypeDummy - DO NOT USE XcmJMDocType .1.3.6.1.4.1.253.8.58.999.6 |
xCmJobMonTCDocFileNameTypeDummy - DO NOT USE XcmJMDocFileNameType .1.3.6.1.4.1.253.8.58.999.7 |
xCmJobMonTCDocStateDummy - DO NOT USE XcmJMDocState .1.3.6.1.4.1.253.8.58.999.8 |
xCmJobMonTCDocOutputMethodDummy - DO NOT USE XcmJMDocOutputMethod .1.3.6.1.4.1.253.8.58.999.9 |
xCmJobMonTCGroupSupportDummy - DO NOT USE XcmJMGroupSupport .1.3.6.1.4.1.253.8.58.999.10 |
xCmJobMonTCImpsCountTypeDummy - DO NOT USE XcmJMImpsCountType .1.3.6.1.4.1.253.8.58.999.11 |
xCmJobMonTCMediumTypeDummy - DO NOT USE XcmJMMediumType .1.3.6.1.4.1.253.8.58.999.12 |