Browse Prior Art Database

Printer Device Driver Error Reporting

IP.com Disclosure Number: IPCOM000060562D
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 which allows a user program to dynamically specify a minimum device error severity which is to be reported, and which provides detailed device error information. User programs typically do not have knowledge of where program output is directed. The output may be in a file, or it may go to a device. Such programs are usually not prepared to handle device errors if they should occur. On the other hand, certain user programs may have the job of servicing a device. These types of programs would certainly be interested in device errors. The details of this method are described for the UNIX* operating system running as a virtual machine on the Virtual Resource Manager (VRM) control program. The VRM control program is similar in concept to the IBM VM/370 control program.

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

Page 1 of 1

Printer Device Driver Error Reporting

A method is described which allows a user program to dynamically specify a minimum device error severity which is to be reported, and which provides detailed device error information. User programs typically do not have knowledge of where program output is directed. The output may be in a file, or it may go to a device. Such programs are usually not prepared to handle device errors if they should occur. On the other hand, certain user programs may have the job of servicing a device. These types of programs would certainly be interested in device errors. The details of this method are described for the UNIX* operating system running as a virtual machine on the Virtual Resource Manager (VRM) control program. The VRM control program is similar in concept to the IBM VM/370 control program. Printer errors are divided into two severities of errors. The least severe are intervention errors. These errors are usually corrected with human intervention. An example of this type of error is the "out of paper" condition. The most severe are fatal errors. These are errors for which there is no apparent recovery. An example of a fatal error is the printer adapter failing to respond. The default error reporting level is to report fatal errors. If a fatal error occurs during a write system call, the program would be informed of such an error with an error number signifying a hardware error. If an intervention error occurs, that error is not re...