xcmJobServiceCopyOID 1.3.6.1.4.1.253.8.58.2.11

Copy 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.