For ROC non-direct Report output, if the device driver for that output device is a system-supplied device driver, and the device is not defined in the COMS Configuration file as REMOTELP, then the appropriate system-supplied device driver is not invoked, and output is sent directly to the output device.

For ROC non-direct Report output, if a device driver for that output device is specified, and the terminal model is defined as REMOTELP, then the device driver is invoked before the output is sent to the output device. This path can be seen in the figure ROC Delivery Mechanism, proceeding from the ROC Transform to the System Device Driver.

If you supply your own device driver for an output device, the Prints/Reprints software passes any appropriate ROC non-direct Report printer output through that device driver before sending it to the output device.

To ensure that your own device drivers are invoked, some output lines are prefixed by a NULL character as the first character in the line. If the presence of this NULL character is likely to interfere with the actual output from the printing device, your device driver should delete this character before releasing the line for printing.

Before creating a device driver, you must be aware that the lines of Report output processed by File Transform are fully formatted for printing; that is, they already contain all the required terminal control codes.