Browse Prior Art Database

Flush RESUME Controls for Printer Device Driver

IP.com Disclosure Number: IPCOM000060558D
Original Publication Date: 1986-Apr-01
Included in the Prior Art Database: 2005-Mar-08
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Chen, JN: AUTHOR [+4]

Abstract

A method is described to cleanly terminate a print job or to restart a job when a print error occurs. A UNIX*-operating system that runs as a virtual machine on a Virtual Resource Manager (VRM) control program uses supervisor calls (SVCs) to pass data and commands to a VRM Device Driver. The VRM Device Driver controls the device adapter and paces the data to and from the device. Data is sent to the VRM Device Driver in control blocks which it queues up internally. Each queue element sent to the VRM Device Driver is processed individually. There are two basic types of printer errors that can occur: recoverable and non-recoverable. The VRM Print Device Driver cannot usually determine whether an error is recoverable. This decision is best made by an application program.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 65% of the total text.

Page 1 of 1

Flush RESUME Controls for Printer Device Driver

A method is described to cleanly terminate a print job or to restart a job when a print error occurs. A UNIX*-operating system that runs as a virtual machine on a Virtual Resource Manager (VRM) control program uses supervisor calls (SVCs) to pass data and commands to a VRM Device Driver. The VRM Device Driver controls the device adapter and paces the data to and from the device. Data is sent to the VRM Device Driver in control blocks which it queues up internally. Each queue element sent to the VRM Device Driver is processed individually. There are two basic types of printer errors that can occur: recoverable and non- recoverable. The VRM Print Device Driver cannot usually determine whether an error is recoverable. This decision is best made by an application program. Therefore, when a non-fatal error is detected by the VRM Device Driver, it holds processing on the current queue element until it receives a response from a higher level program. In a multi-user, multi-process environment it is important to be able to clear out these pending work requests after an unrecoverable error or job cancellation without having to re-IPL (initial program load) the system. Likewise, in this environment it is very desirable to be able to restart processing these held queue elements after an error condition has been resolved without having to re-IPL the system. If proper housekeeping of VRM Device Driver queue elements is not done,...