IPDS jobs are handled in transaction mode. The transaction mode must be enabled in the Settings Editor via "Transaction printing - Settings". After transaction mode is enabled, the printer must be switched on-line either in the control panel, or through the Settings Editor via "Transaction printing - Settings". Then, the printer can make contact with the host.
Transaction jobs are never stored in the job history of the printer.
The stop button can be pressed on the printer or on the host side. In case of a job abort, all jobs in the print queue that are pending for printing are aborted. Partial sets are ejected. All pages which are being processed by the IPDS interpreter will be deleted. All pages present in the buffer of the printer will be printed. When a set without any finishing options is being printed, printing stops at the next sheet. When a set with finishing options is being printed, printing stops when the set is ready.
When the job abort comes from the control panel, the host schedules the cancellation for the running job. Jobs which are waiting to be printed are not affected by the job abort.
There are three types of errors:
Runtime contradictions,
Soft errors,
Hard errors.
Runtime contradictions occur when resources requested by the IPDS data stream are not available. Printing does not start and a message is shown on the control panel. The operator is requested to solve the contradiction. When the contradiction is solved, printing starts.
Soft errors occur when the printer is not available due to a paper jam. The operator is requested to remove the jammed paper. When the jammed paper is removed, the printer continues printing. When the setting "Output recovery" is set to "Normal" in the Settings Editor, the printer uses the internal page recovery to print the rest of the job correctly. When the setting "Output recovery" is set to "Suppress" in the Settings Editor, the host recovers the job when a paper jam occurs.
Hard errors occur due to a hardware defect in the printer. In this case, the printer cannot use the internal page recovery. The job must be recovered by the host.