Method for representing and signaling run-time program conditions

• US 5,455,949 A
• Filed: 09/06/1991
• Issued: 10/03/1995
• Est. Priority Date: 09/06/1991
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Plaetzer, Scott A., Smith, Robert M., Grantz, Jeffrey A., Conder, Ralph O., Tindall, William N. J.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US07/755,708
• Time in Patent Office: 1,488 Days
• Field of Search: 395/700, 395/500, 395/375, 395/275, 395/600, 371/19, 371/12, 364/DIG. 1
• US Class Current: 712/234
• CPC Class Codes: G06F 11/0775 Content or structure details of the error report, e.g. specific table structure, specific error fields
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

An improved method and system is described for generalized handling of conditions occurring during program execution in a computer system having a multi-language Condition Manager (CM). A general signaling routine having object code for an external entry point suitable for linking to application programs written in any language supporting external calls is used. The signaling routine may be used by programs to eliminate the step of checking return codes from subroutines by coding the subroutine to automatically signal the proper condition to the CM which in conjunction with user defined condition handlers takes proper actions in response to the condition. A general condition token which may be used as a feedback token is defined as a condition identifier, a format code for the condition identifier, a severity code for the condition, a control code for a facility identifier, a facility identifier and an optional handle for instance specific information. The signaling routine and the feedback token are used by subroutines which can optionally provide for passing an address, where a feedback token can be stored. The subroutine signals conditions if the severity of the condition is greater than a threshold or else stores a feedback token at the address.

Claims

1. A method for handling a condition occurring during computer program execution, the condition having a quantified severity, comprising the steps of:

(1) calling a service subroutine by the computer program;

(2) passing a selected address, where a feedback token describing the condition can be stored for use by the computer program, to the service subroutine;

(3) executing the service subroutine until completion or until the condition is detected; and

(4) if the severity of the condition is greater than a threshold, then signaling the condition to a Condition Manager for immediate processing of the condition, else storing, by the service subroutine, a feedback token at the selected address, wherein the step of storing the feedback token comprises the steps of;

(a) storing a condition identifier;

(b) storing a format code for the condition identifier;

(c) storing a severity code for the condition;

(d) storing a control code for a facility identifier for the condition; and

(e) storing a facility identifier for the condition.

2. The method of claim 1 wherein the step of storing the feedback token further comprises storing data describing the condition.

3. The method of claim 2 wherein the step of storing by the the service subroutine of the feedback token further comprises the step of storing message insert information for insertion into a message associated with the condition.

4. The method of claim 1 wherein the step of storing the feedback token further comprises the steps of:

(1) storing a condition identifier four bytes in length;

(2) storing a two bit length format code for the condition identifier;

(3) storing a three bit length severity code for the condition;

(4) storing a three bit length control code for a facility identifier for the condition;

(5) storing a three character length facility identifier for the condition; and

(6) storing a four byte length handle for instance specific information for the condition.

5. A method for handling conditions in a computer system comprising the steps of:

(1) detecting a condition;

(2) storing a feedback token describing the condition, the token including;

(a) a condition identifier;

(b) a format code for the condition identifier;

(c) a severity code for the condition;

(d) a control code for a facility identifier; and

(e) a facility identifier;

thereby, recording information about the condition for subsequent use;

wherein said method further comprises a prepatory step of calling from a routine in a program to a subroutine and a last step of returning said feedback token to said routine in said program.

6. The method of claim 5 further comprising the step of storing instance specific information for the condition.

7. The method of claim 6 wherein the step of storing the feedback token further comprises the steps of:

(1) storing a condition identifier four bytes in length;

(2) storing a two bit length format code for the condition identifier;

(3) storing a three bit length severity code for the condition;

(4) storing a three bit length control code for a facility identifier for the condition;

(5) storing a three character length facility identifier for the condition; and

(6) storing a four byte length handle for instance specific information for the condition.

8. The method of claim 6 wherein the step of storing the feedback token further comprises the step of storing message insert information for insertion into a message associated with the condition.

9. The method of claim 5, the computer system having a message utility, for generating and sending messages, the method further comprising the step of passing the feedback token to the message utility.