Browse Prior Art Database

Error Message Generation in a Heterogeneous Environment

IP.com Disclosure Number: IPCOM000100612D
Original Publication Date: 1990-May-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Hoffman, RD: AUTHOR

Abstract

Disclosed is a method for generating meaningful error messages based on diagnostic information from other products, without requiring the message files of those products.

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

Error Message Generation in a Heterogeneous Environment

       Disclosed is a method for generating meaningful error
messages based on diagnostic information from other products, without
requiring the message files of those products.

      In SQL database products, diagnostic information is typically
returned in a structure containing several fields called the SQLCA.
The fields of the SQLCA include an error code and a list of tokens.
Based on the code, a message can be selected from a message file, and
the tokens can be inserted into this message to provide a coherent
description of the error and its context.

      For example, assume that a diagnostic structure is returned
having error code -104 and the tokens "SABLE", "CREATE", and "TABLE".
 Based on the error code, the following message is selected:
      An unexpected token "&1" was found following "&2".
      Expected tokens may include "&3".
Token insertion leads to the following message:
 An unexpected token "SABLE" was found following "CREATE".
      Expected tokens may include "TABLE".

      This process is complicated in a heterogeneous environment,
where error codes from different products may not always agree.  A
range of solutions present themselves.

      One extreme solution is to keep a message file for each
product.  This allows exact message production, at the expense of
extra files (usually large) and the significant maintenance burden of
keeping each file synchronized with its product.  At the other
extreme, no processing at all is provided for non-local products.
Instead, a generic message such as:
ERROR = xxx; PRODUCT = yyy; TOKENS = ... can be produced, at the
expense of clarity and ease of use.

      The following solution avoids the pitfalls of both methods, to
produce a message which is often identical to the message produced by
the first method, at a much smaller cost.
      1.  ...