Browse Prior Art Database

Error Control Resource Compilation Table

IP.com Disclosure Number: IPCOM000117010D
Original Publication Date: 1995-Dec-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 69K

Publishing Venue

IBM

Related People

Jensen, B: AUTHOR [+3]

Abstract

Disclosed is a procedure for simplifying a program interface to a diagnostic data collection facility used by application programs when a logic error is detected. The name of this procedure is called the Error Control Resource Compilation Table (ECRCT).

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

Error Control Resource Compilation Table

      Disclosed is a procedure for simplifying a program interface to
a diagnostic data collection facility used by application programs
when a logic error is detected.  The name of this procedure is called
the Error Control Resource Compilation Table (ECRCT).

      First Failure Support Technology (FFST)*, a software service
package, processes error events and generates a number of diagnostic
data outputs.  To access the services of FFST, an application must
code a number of call statements in order to inform FFST what
diagnostic services (i.e., dump, error log, message, notification)
are required and what data is to be processed by these services.  The
call statements can get quite large and the number can vary from
three to eight.  In order to minimize the number of calls and the
data that needs to be passed on each call, the ECRCT methodology was
invented.

      ECRCT is a procedure by which all static data normally passed
on the call to FFST is now placed into a table in a file using a
user-friendly format.  Each static data item (e.g., application name,
message number) was removed from the FFST call and placed in a table
entry using order-independent keywords.  Each entry in the file has
an identifier, called a Probe ID, which names the entry.  There is
one entry for each FFST Probe (i.e., FFST call).  An example of an
entry for a single FFST Probe call follows:
  /* Table entry 1 */
  ProbeID(payroll_ent1)        /* name of entry            */
  ApplicationName(payroll1)    /* name of application         */
  ApplVersion(2)               /* application version   */
  MessageNumber(PAY0006)       /* message to be displayed/logged  */
  MessageLog(yes)              /* log the message   */
  ErrorLog(yes)                /* make an er...