US4922491A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Input/output device service alert function
Assignee: International Business Machines Corp
•
Filing: 1988-08-31
•
Granted: 1990-05-01
•
Expires: 2008-08-31
Abstract
Abstract A method of automatically detecting and analyzing exception events occurring in a computer peripheral subsystem connected to a host computer system includes maintaining a Subsystem Environment data base comprising information relating to the current configuration of the computer peripheral subsystem, and usage and error information relating to the peripheral subsystem. A Problem Description procedure is conditionally invoked when the data in the Subsystem Environment data base reflects an exception event that indicates either a clear or a probable need for service attention to the peripheral subsystem. The Problem Description procedure includes creating from stored rules a view of the Subsystem Environment data base relevant to the exception event, and developing a Problem Profile (record) describing the exception event. The Problem Profile record is compared to the Problem Profile data base to determine if the current exception event relates to a problem already recorded in the data base. If a match is found, the matching record is updated with new information from the current record. Otherwise, the current record is entered as a new problem. If the Problem Profile indicates that the exception event is a repeat of a problem already recorded in the Problem Profile data base, the matching profile record is updated to reflect the new Problem Profile data. A Problem Evaluation procedure is conditionally invoked. The Problem Evaluation procedure is not invoked if the updated problem record (not the new Problem Profile) from the Problem Profile data base has already been reported to the host system and a service action is pending. If operations of the peripheral subsystem have been disrupted or degraded beyond the limits of acceptable subsystem performance, a service alert message is generated. The service alert message is inserted into the Problem Profile record in the Problem Profile data base, and the service alert message is transmitted to the host system. The service alert message contains a variety of information for the subsystem user and for the repair technician.
Inventors
- 👤 Jerry L. Coale
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-26 18:29
CPC Classifications
G; G06; G06F; G06F11/00; G06F11/22; G06F11/2257; G06F11/07; G06F11/0703; G06F11/0706; G06F11/0745; G06F11/079; G06F11/30; G06F11/34; G06F11/3466; G06F11/3485
Claims Analysis
Total Claims: 14
Claim 1
Independent Claim
357 words
In a computer peripheral subsystem connected to a host computer system, a method of automatically detecting and analyzing exception events occurring in said peripheral subsystem comprising: maintaining a Subsystem Environment data base comprising information relating to the current configuration of said computer peripheral subsystem and usage and error information relating to said peripheral subsystem; conditionally invoking a Problem Description procedure when the data in said Subsystem Environment data base reflects an exception event that indicates either a clear or a probable need for service attention to said peripheral subsystem, said Problem Description procedure comprising: creating from stored rules a view of said Subsystem Environment data base relevant to said exception event; developing a current Problem Profile record describing said exception event; scanning a Problem Profile data base comprising Problem Profile records of previously occurring exception events to relate said current Problem Profile record to a Problem Profile record that already exists in said Problem Profile data base; if said current Problem Profile record matches an existing Problem Profile record in said Problem Profile data base, and said existing Problem Profile record indicates that a service action is pending for the covered problem, updating said existing Problem Profile record; if said current Problem Profile record matches an existing Problem Profile record in said Problem Profile data base, and said existing Problem Profile record indicates that a service action is not pending for the covered problem, updating said existing Problem Profile record and invoking a Problem Evaluation procedure; if said current Problem Profile record does not match an existing Problem Profile record in said Problem Profile data base, adding said current Problem Profile record to said Problem Profile data base; wherein said Problem Evaluation procedure comprises: examining said current Problem Profile record in view of stored rules relating to acceptable subsystem performance; and if operations of said peripheral subsystem have been disrupted or degraded beyond the limits of acceptable subsystem performance, generating a service alert message, and inserting said service alert message into said Problem Profile record, updating said existing Problem Profile record in said Problem Profile data base, and transmitting said service alert message to said host system.
Claim 2
Dependent Claim
357 words
In a computer peripheral subsystem connected to a host computer system, a method of automatically detecting and analyzing exception events occurring in said peripheral subsystem comprising: maintaining a Subsystem Environment data base comprising information relating to the current configuration of said computer peripheral subsystem and usage and error information relating to said peripheral subsystem; conditionally invoking a Problem Description procedure when the data in said Subsystem Environment data base reflects an exception event that indicates either a clear or a probable need for service attention to said peripheral subsystem, said Problem Description procedure comprising: creating from stored rules a view of said Subsystem Environment data base relevant to said exception event; developing a current Problem Profile record describing said exception event; scanning a Problem Profile data base comprising Problem Profile records of previously occurring exception events to relate said current Problem Profile record to a Problem Profile record that already exists in said Problem Profile data base; if said current Problem Profile record matches an existing Problem Profile record in said Problem Profile data base, and said existing Problem Profile record indicates that a service action is pending for the covered problem, updating said existing Problem Profile record; if said current Problem Profile record matches an existing Problem Profile record in said Problem Profile data base, and said existing Problem Profile record indicates that a service action is not pending for the covered problem, updating said existing Problem Profile record and invoking a Problem Evaluation procedure; if said current Problem Profile record does not match an existing Problem Profile record in said Problem Profile data base, adding said current Problem Profile record to said Problem Profile data base; wherein said Problem Evaluation procedure comprises: examining said current Problem Profile record in view of stored rules relating to acceptable subsystem performance; and if operations of said peripheral subsystem have been disrupted or degraded beyond the limits of acceptable subsystem performance, generating a service alert message, and inserting said service alert message into said Problem Profile record, updating said existing Problem Profile record in said Problem Profile data base, and transmitting said service alert message to said host system.
Claim 3
Dependent Claim
33 words
The method of claim 1, wherein said step of conditionally invoking said Problem Description procedure comprises examining said Subsystem Environment data base in view of rules describing normal performance and possible exception events.
Claim 4
Dependent Claim
93 words
The method of claim 2, wherein said step of conditionally invoking said Problem Description procedure additionally comprises examining the data regarding said exception event to determine if said exception event is a soft event or a hard event, and wherein: if said exception event is a hard event, invoking said Problem Description procedure; and if said exception event is a soft event, examining said exception event against a set of rules to determine if a threshold criterion has been exceeded, and invoking said Problem Description procedure if said threshold criterion has been exceeded.
Claim 5
Dependent Claim
57 words
The method of claim 3, wherein said step of examining said exception event against a set of rules to determine if a threshold criterion has been exceeded comprises examining said exception event against a subset of rules relating to the type of exception event and the portion of said computer peripheral subsystem relating to said exception event.
Claim 6
Dependent Claim
35 words
The method of claim 4, wherein determining if a threshold criterion has been exceeded comprises determining that a trend of related exception events have been detected within a common portion of said computer peripheral subsystem.
Claim 7
Dependent Claim
176 words
A computer peripheral subsystem for connection to a host computer system, comprising: an input/output device connected for receiving operation commands and data from said host computer system; an error detection and recovery system comprising means for detecting exceptions in the operation of the input/output device and attempting recovery of such error events; memory for maintaining a Subsystem Environment data base relating to the computer peripheral subsystem, including data on the physical configuration of said computer peripheral subsystem, a subsystem usage log, an exception log, fault criteria, and problem procedures; means for updating the subsystem usage log and the exception log in response to usage and exception information generated by said input/output device and said error detection and recovery system; means for testing data received by said subsystem usage log and said exception log against said stored fault criteria; means for characterizing the subsystem physical configuration, the subsystem usage log, and the exception log for the current fault type; and means for analyzing the data with the problem procedures to determine if a service action is required.
Claim 8
Dependent Claim
176 words
A computer peripheral subsystem for connection to a host computer system, comprising: an input/output device connected for receiving operation commands and data from said host computer system; an error detection and recovery system comprising means for detecting exceptions in the operation of the input/output device and attempting recovery of such error events; memory for maintaining a Subsystem Environment data base relating to the computer peripheral subsystem, including data on the physical configuration of said computer peripheral subsystem, a subsystem usage log, an exception log, fault criteria, and problem procedures; means for updating the subsystem usage log and the exception log in response to usage and exception information generated by said input/output device and said error detection and recovery system; means for testing data received by said subsystem usage log and said exception log against said stored fault criteria; means for characterizing the subsystem physical configuration, the subsystem usage log, and the exception log for the current fault type; and means for analyzing the data with the problem procedures to determine if a service action is required.
Claim 9
Dependent Claim
44 words
The computer peripheral subsystem of claim 6 additionally comprising: means for determining the service requirements if a service action is determined to be required; and means for storing in said memory a service alert record comprising a record of the service actions called for.
Claim 10
Dependent Claim
25 words
The computer peripheral subsystem of claim 7 additionally comprising means for sending to said host computer system a message when a service action is required.
Claim 11
Dependent Claim
199 words
In a computer peripheral subsystem connected to a host computer system, a method of automatically detecting and analyzing exception events occurring in said peripheral subsystem, the computer peripheral subsystem including an input/output device connected for receiving operation commands and data from said host computer system, and an error detection and recovery system comprising means for detecting error events in the operation of the input/output device and attempting recovery of such exception events, the method comprising: storing in a memory a Subsystem Environment data base relating to said computer peripheral subsystem, including data on the physical configuration of said computer peripheral subsystem, a subsystem usage log, an exception log, fault criteria, and problem procedures; updating the subsystem usage log and the exception log in response to usage and exception event information generated by said input/output device and said error detection and recovery system; when a current exception is detected, testing data received by said subsystem usage log and said exception log against said stored fault criteria; characterizing the subsystem physical configuration, the subsystem usage log, and the exception log for said current exception; and analyzing the characterized data with said problem procedures to determine if a service action is required.
Claim 12
Dependent Claim
199 words
In a computer peripheral subsystem connected to a host computer system, a method of automatically detecting and analyzing exception events occurring in said peripheral subsystem, the computer peripheral subsystem including an input/output device connected for receiving operation commands and data from said host computer system, and an error detection and recovery system comprising means for detecting error events in the operation of the input/output device and attempting recovery of such exception events, the method comprising: storing in a memory a Subsystem Environment data base relating to said computer peripheral subsystem, including data on the physical configuration of said computer peripheral subsystem, a subsystem usage log, an exception log, fault criteria, and problem procedures; updating the subsystem usage log and the exception log in response to usage and exception event information generated by said input/output device and said error detection and recovery system; when a current exception is detected, testing data received by said subsystem usage log and said exception log against said stored fault criteria; characterizing the subsystem physical configuration, the subsystem usage log, and the exception log for said current exception; and analyzing the characterized data with said problem procedures to determine if a service action is required.
Claim 13
Dependent Claim
38 words
The method of claim 9 additionally comprising: determining the service requirements if a service action is determined to be required; and storing in said memory a service alert record comprising a record of the service actions called for.
Claim 14
Dependent Claim
21 words
The method of claim 10 additionally comprising sending to said host computer system a message when a service action is required.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1993-04-30 | 1993-10-30 | 1994-05-01 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 1997-04-30 | 1997-10-30 | 1998-05-01 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2001-04-30 | 2001-10-30 | 2002-05-01 | $7700.00 | Window Closed / Lapsed |