Browse Prior Art Database

Customized Handling of Application Errors Under OS/2

IP.com Disclosure Number: IPCOM000108127D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 3 page(s) / 119K

Publishing Venue

IBM

Related People

Fuchs, L: AUTHOR [+4]

Abstract

Disclosed is an OS/2* application called the Error Handler, which can generically handle errors which are generated by custom applications running in an OS/2 environment.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Customized Handling of Application Errors Under OS/2

       Disclosed is an OS/2* application called the Error
Handler, which can generically handle errors which are generated by
custom applications running in an OS/2 environment.

      Customarily when a OS/2 application is developed, the
application developer is responsible for handling errors which could
result from the application.  The following is a brief example:
 Begin
  open file
   if file not there
     then
      print an error message "Error File Not Found"
        End.

      With the Error Handler application, when a program detects an
error it can send an error message to the error handler. The error
handler application will then be responsible for processing the
error.

      The following paragraph outlines the contents of an error
message sent to the Error Handler.  Each error is identified by a
two-character prefix and a three-digit error number. The error prefix
is used to type errors. For example, an error prefix 'CO', may be
selected to represent a communication error. An error number
identifies a specific error within a given error type. For example,
error CO 001 may be defined to be a communication error caused by a
bad token ring cable connection.  The error prefixes and error
numbers are specified at system design time. The error message
received by the error handler process contains the following
information:
     -origin application name
     -error prefix
     -error number
     -error arguments (up to 5)

      The error handler application, upon retrieving an error message
from its interprocess message queue, determines the error number and
error prefix.  Once the error prefix is determined, the error handler
constructs a filename by substituting the error prefix in to the
template 'ERRTXT__.MSG in place of the underline characters. For
example, when a CO type error is received, the file name
'ERRTXTCO.MSG' is constucted. This filename is then used as the name
of the error description filename. The error description file
contains descriptive text for each of the different errors of a given
type. After the error description filename is built, the record
number that corresponds to the error number is read from this file.

      The record read from the description file has the following
format:

                 ...