System and method for software error early detection and data capture

• US 5,119,377 A
• Filed: 06/16/1989
• Issued: 06/02/1992
• Est. Priority Date: 06/16/1989
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Long, Kenneth J., Cobb, Paul R., Lennon, Christopher J.
• Primary Examiner(s): Smith, Jerry
• Assistant Examiner(s): Hua, Ly V.
• Application Number:
  US07/367,403
• Time in Patent Office: 1,082 Days
• Field of Search: 371/12, 371/16.1, 371/19, 371/29.1, 371/21.6, 364/267.8, 364/267.91
• US Class Current: 714/38.11
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

A process for detecting software errors in a computer program and automatically gathering diagnostic data limited to the error to be resolved. Error detection code is placed within the software program during program development. When an error or failure is detected, this process is called and captures only the data required to debug the software error. The error detection code notifies the process of which data to capture by selecting entries from a table within the process. This table, known as an Application Data Table (ADT), contains the layout and format of all data areas used by the calling problem program and information required to build a generic alert and send the generic alert to a computer network monitor program. This process is only called conditionally when an error is detected. It is completely idle until such a condition occurs.

Claims

1. A method of detecting and diagnosing software errors in a computer software program executing on a computer processor system comprising the steps of:

defining the internal structure of the computer software program and recording said internal structure in at least one predefined table in a disk file;

placing error detection points within said computer software program which are activated individually by the occurrence of a software error to signal when diagnostic data is to be collected;

responsive to the receipt of a signal to collect diagnostic data generated by an activated error detection point, transferring control of said computer software program to a data collection and reporting routine;

collecting and storing diagnostic data based on a first set of keyword-value pairs passed by the activated error detection point on a macro call to said data collection and reporting routine, and the computer software program internal structure contained in said predefined table;

generating a unique software symptom string under control of the data collection and reporting routine; and

recording said software symptom string in a software program error log.

2. The method of claim 1 further comprising the steps of constructing a software error generic alert and forwarding said software error generic alert to a network monitor.

3. The method of claim 2 wherein the step of defining the internal structure of the computer software program includes coding a set of predefined macros as a separate job in parallel with the coding of said computer software program to determine the diagnostic data to be collected and the type of software error generic alert to be built.

4. The method of claim 1 further including the step of returning control back to the computer software program after said diagnostic data is collected and continuing with computer software program execution.

5. The method of claim 1 wherein said software symptom string contains a second set of keyword-value pairs which uniquely describe and identify the software error.

6. The method of claim 5 wherein the software symptom string contains the computer software program name, the computer software program version and release level, the computer software program module that detected the error, and a unique error detection point identifier.

7. The method of claim 1 wherein said predefined table contains identifying information for the corresponding computer software program, the layout and format of each data structure and control block used by the said computer software program, the category of the software error, the cause of the software error detected, and the action required to resolve the software error.

8. The method of claim 1 wherein the step of placing error detection points within said computer software program includes locating macro calls to the data collection and reporting routine at points within said computer software program that can be reached only if a software error occurs.

9. The method of claim 1 wherein the step of collecting and storing diagnostic data includes loading said predefined table into memory from the disk file, and based on the first set of keyword-value pairs contained in the macro call to the data collection and reporting routine, collecting from computer software program storage the data identified by said first set of keyword-value pairs and writing said collected data to a dump file.

10. The method of claim 9 wherein the software problem error log contains an identification of the processor and operating system executing the computer software program, the date and time the data collection and reporting routine was invoked, the name of the dump file containing said collected data, an identification of the problem computer software program, and the unique software symptom string.

11. A system for detecting and diagnosing software errors in a computer software program executing on a computer processor system comprising:

table means for generating at least one predefined table that is representative of the internal structure of said computer software program and for saving said predefined table in a disk file;

error detection means located at error detection points within said computer software program for detecting the occurrence of a software error and for interrupting execution of said program; and

data collection and reporting means, cooperative with said error detection means and said table means for collecting data from memory that represents diagnostic data for the software error and for generating a software symptom string, said data collection and reporting means being actuated by the receipt of a macro call from said error detection means, said macro call identifying selected entries in said predefined table that contain the location in memory of said diagnostic data.

12. The system of claim 11 including means cooperative with said data collection and reporting means for constructing a software error generic alert based on said identified selected entries in said predefined table and forwarding said generic alert to a network monitor.

13. The system of claim 11 wherein said data collection and reporting means generates an error record for said software error and records said error record in an error log.

14. The system of claim 11 wherein said data collection and reporting means records said diagnostic data and software symptom string in a data file.

15. The system of claim 11 wherein said data collection and reporting means returns control to said computer software program after said diagnostic data is collected.