US5455949A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method for representing and signaling run-time program conditions
Assignee: International Business Machines Corp
•
Filing: 1991-09-06
•
Granted: 1995-10-03
•
Expires: 2011-09-06
Abstract
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.
Inventors
- 👤 Ralph O. Conder
- 👤 Jeffrey A. Grantz
- 👤 Scott A. Plaetzer
- 👤 Robert M. Smith
- 👤 William N. J. Tindall
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 05:15
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/542; G06F11/00; G06F11/07; G06F11/0703; G06F11/0766; G06F11/0775; G06F2201/00; G06F2201/865
Claims Analysis
Total Claims: 11
Claim 1
Independent Claim
163 words
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.
Claim 2
Independent Claim
163 words
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.
Claim 3
Dependent Claim
20 words
The method of claim 1 wherein the step of storing the feedback token further comprises storing data describing the condition.
Claim 4
Dependent Claim
37 words
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.
Claim 5
Dependent Claim
91 words
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.
Claim 6
Independent Claim
103 words
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.
Claim 7
Independent Claim
103 words
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.
Claim 8
Dependent Claim
17 words
The method of claim 5 further comprising the step of storing instance specific information for the condition.
Claim 9
Dependent Claim
91 words
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.
Claim 10
Dependent Claim
31 words
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.
Claim 11
Dependent Claim
32 words
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.
References Cited (Backward Citations)
US4240137A
Cited
US4493034A
Cited
US4488227A
Cited
US4980820A
Cited
US4819233A
Cited
US5175855A
Cited
US5103498A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1998-10-02 | 1999-04-03 | 1999-10-03 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2002-10-02 | 2003-04-03 | 2003-10-03 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2006-10-02 | 2007-04-03 | 2007-10-03 | $7700.00 | Window Closed / Lapsed |