JP2002366396A - System and program for automatically collecting fault analysis information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make fault analysis information automatically collectable at the time of the occurrence of a fault in a software system or the like in a computer system. SOLUTION: When a fault event in the computer system has occurred, a system for automatically collecting fault analysis information acquires a parameter for fault analysis corresponding to the fault event by collation and coincidence between a fault message ID outputted by fault event extraction processing 11 and a preliminarily registered fault message ID and starts fault analysis information analysis processing 12 to retrieve a preliminarily registered fault analysis information database 18 by the fault message ID and specifies fault analysis information acquisition processing 13 for every fault event and adds the parameter for fault analysis to start this processing and outputs fault analysis information acquired by execution of the fault analysis information acquisition processing to an information file 14 for analysis by a utility program prepared for every fault event.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for automatically collecting failure analysis information for promptly specifying the cause of a failure and processing for responding when a failure occurs in a computer system.

[0002]

2. Description of the Related Art Conventionally, in a computer system,
When a failure (especially a failure of a software system) occurs, the operation of identifying the cause of the failure and acquiring necessary failure analysis information is generally performed manually each time.
In other words, an experienced system developer or system operator can check the output messages of the computer system to identify the failure, specify the failure analysis method, and obtain the failure analysis information. To give instructions for the work. Therefore, the start and execution of the failure analysis information acquisition work are delayed,
In many cases, necessary trace information overflowed and could not be obtained, so that it was often necessary to wait for the same failure to be reproduced.

[0003]

In a computer system, when a failure occurs, it is necessary to identify the cause of the failure and to quickly execute a corresponding process to restore the system. This is because information systems have become key to corporate activities and high reliability and high operability are required. In addition, in order to quickly recover the system, it is necessary to obtain failure analysis information in a timely manner and to quickly transfer the obtained information to the analysis department. further,
In order to enable the system to be operated for 24 hours, automation and labor saving of such operations are required.
However, conventionally, computer system failures
Even if a failure is related to a subordinate program other than the operating system (OS) that is the core of computer control, the information necessary for failure analysis can be automatically collected to identify the cause of the failure. There has been a problem that a failure analysis information automatic collection system has not been developed to enable quick response processing.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and has been made in order to quickly identify the cause of a failure and take appropriate action when a failure occurs in a computer system.
It is an object of the present invention to provide a failure analysis information automatic collection system capable of automatically collecting failure analysis information.

[0005]

Means for Solving the Problems To solve the above-mentioned problems, the invention according to claim 1 relates to a failure analysis information automatic collection system, wherein when a failure event occurs in a computer system, the failure event extraction processing is performed. By collating and matching the failure message ID output by the computer system with a previously registered failure message ID, a failure analysis parameter corresponding to the failure event is acquired, and a failure analysis information analysis process is started. The analysis information analysis processing searches the failure analysis information database registered in advance by the failure message ID, specifies the failure analysis information acquisition processing for each failure event, adds the failure analysis parameter, and specifies the failure analysis information. The failure analysis information acquisition process is started, and the failure analysis information acquisition process is executed. And the failure analysis information, is characterized in that output by prepared has been have utility program for each failure event in the analysis data file.

According to a second aspect of the present invention, there is provided the failure analysis information automatic collection system according to the first aspect, wherein the failure analysis information held in the analysis information file is saved and discharged to a storage medium. It is characterized by:

According to a third aspect of the present invention, there is provided the automatic failure analysis information collection system according to the first aspect, wherein the failure analysis information held in the analysis information file is transmitted to a TSS (Ti
me Sharing System) The feature is to output to terminal.

According to a fourth aspect of the present invention, there is provided the failure analysis information automatic collection system according to any one of the first to third aspects, wherein the failure analysis information stored in the analysis information file is stored. It is characterized in that failure analysis information whose period has expired is automatically deleted.

According to a fifth aspect of the present invention, there is provided the automatic failure analysis information collection system according to any one of the first to fourth aspects, wherein the failure event extraction process acquires all messages displayed on the computer system. A process of comparing the message ID with a fault message ID registered in the fault message ID table in advance, and obtaining a failure analysis parameter based on the matched fault message ID and analyzing the fault analysis information. And processing for activating the processing.

According to a sixth aspect of the present invention, there is provided the automatic failure analysis information collection system according to any one of the first to fifth aspects, wherein the failure analysis information analysis processing is performed when the failure message ID indicates that the program is abnormally terminated. Consists of a process of registering failure occurrence information in a program status management table in a failure analysis information database in order to wait for the end of a job using an abnormally terminated program. If
It is a process of additionally registering the sub file name of the dump in the line having the same job occurrence number in the program status management table. If the failure message ID is abnormal termination of the job, the program status management table is written by the job occurrence number in the message. Search to obtain failure analysis information, calculate the message acquisition section at the time of the occurrence of the failure event from the date and time of the occurrence of the failure event, start the message acquisition process using the message acquisition section as a start parameter, and analyze the message of the failure period for the above analysis. In the information file, the memory dump table in the failure analysis information database is searched by the failure program name, the memory dump information is acquired in the analysis information file, and the file dump table in the failure analysis information database is replaced with the failure program name. Search by job name and save file dump information in the above analysis information file Consists processing Tokusuru, if a fault message ID is other than the above abnormal termination, failure message information table in the failure analysis information database message I
D, retrieve the job name of the failure analysis information acquisition program corresponding to the failure message ID, and start the failure analysis information acquisition program JCL (Job Control Language).
e) Acquire the name, activate the specified JCL, acquire the failure analysis information in the analysis information file, calculate the message acquisition section at the time of the failure event occurrence from the failure event occurrence date and time, and determine the message acquisition section. A message acquisition process is started as a start parameter, and a message of a failure period is acquired in the analysis information file.

According to a seventh aspect of the present invention, there is provided the automatic failure analysis information collection system according to the sixth aspect, wherein the memory dump information in the failure analysis information database is specified by a pair of a dump start address and a size. Then, a memory dump acquisition processing program is started using the acquired memory dump information as a start parameter, and a memory dump is acquired in the analysis information file.

The invention according to claim 8 relates to the automatic failure analysis information collection system according to claim 6, wherein the designation of the memory dump information in the failure analysis information database is based on the start JCL name of the memory dump processing program. It is characterized in that the specified JCL is activated and a memory dump is acquired in the analysis information file.

According to a ninth aspect of the present invention, there is provided the failure analysis information automatic collection system according to the sixth aspect, wherein designation of file dump information in the failure analysis information database is performed.
Performed by a pair of dump file name and file type,
It is characterized in that a file dump acquisition processing program is activated by using the acquired file dump information as a start parameter, and a file dump is acquired in the analysis information file.

The invention according to claim 10 is the same as the claim 6.
According to the failure analysis information automatic collection system described above, the file dump information in the failure analysis information database is specified by specifying the startup JCL name of the file dump processing program, and the specified JCL is started to perform the file dump. The analysis information file is acquired.

The invention according to claim 11 is the first invention.
11. In the failure analysis information automatic collection system according to any one of Items 10 to 10, the failure analysis information acquisition processing is executed by a utility program of the basic program, and in the case of message acquisition processing, the failure analysis information acquisition processing is performed by the basic program. It consists of the process of extracting the message in the specified section from the message log file and outputting it to the above information file for analysis. In the case of the memory dump acquisition process,
At the time of abnormal termination of the program, the section specified by the memory image file acquired by the basic program is edited into a predetermined image and output to the analysis information file. In the case of a database file dump acquisition process, a specified database is converted into a sequential file, edited into the predetermined image, and edited into the analysis information file. In the case of the system evaluation information acquisition process, the process of extracting and editing the performance data of the specified section from the system performance log file acquired by the basic program and outputting it to the analysis information file In the case of various types of trace information acquisition processing, Arm and said basic program are extracted and edited trace data for the specified interval from the trace file that collected as trace information is characterized by comprising a process of outputting to the analysis information file.

The invention according to claim 12 is the first invention.
1. The failure analysis information automatic collection system according to item 1, wherein the predetermined image is an alphanumeric kana (ANK) and a hexadecimal image.

According to a thirteenth aspect of the present invention, there is provided a program for automatically collecting failure analysis information, the program being executable by a computer. It is characterized by comprising a program for performing processing.

In the automatic failure analysis information collection system of the present invention, the computer system is provided with a failure analysis information automatic collection program, so that a failure occurrence in an application program other than the computer operation system, a control program for forming middleware, and the like. At this time, since information necessary for failure analysis can be automatically collected, it is possible to quickly identify the cause of the failure and quickly perform processing for dealing with the failure.

[0019]

Embodiments of the present invention will be described below with reference to the drawings. The description will be specifically made using an embodiment. FIG. 1 is a block diagram showing a configuration of an automatic failure analysis information collection system according to an embodiment of the present invention;
FIG. 2 is a flowchart showing the flow of the failure event extraction process, FIGS. 3 and 4 are flowcharts showing the flow of the failure analysis information analysis process, FIG. 5 is a flowchart showing the flow of the analysis information acquisition process, and FIG. 7 is a flowchart showing a flow of a failure analysis information saving process, FIG. 7 is a flowchart showing a flow of a process of deleting saved analysis information, FIG. 8 is a diagram showing contents of a program state management table, and FIG. 9 is a file dump information table. FIG. 10 is a diagram showing the contents of a memory dump information table, FIG. 11 is a diagram showing the contents of a message information table, and FIGS. 12 and 13 are diagrams showing the contents of a control file table. FIG. 14 shows the contents of a subfile name assignment rule table.

Automatic failure analysis information collection system 1 of this example
0 is a failure event extraction process 11, a failure analysis information analysis process 12, and an analysis information acquisition process 13 as shown in FIG.
And an analysis information file (private SYSOUT) 14,
The failure analysis information save processing 15, the storage failure analysis information deletion processing 16, and the storage cartridge magnetic tape (CGM)
T) 17 and a failure analysis information database (DB) 18
, A parameter file 19, and a failure message ID table 20. In the figure, solid arrows indicate the flow of control, and broken arrows indicate the flow of data.

The failure event extraction processing 11 is to input the message ID of the failure message displayed on the computer system,
If the message is a failure message registered in advance by comparing it with a message ID registered in the failure message ID table, a parameter for failure analysis is acquired from the failure message, and a failure analysis information analysis process 12 is performed. Start The failure analysis information analysis processing 12 includes the failure occurrence information when the failure message ID indicates abnormal termination of the program.
In the case of abnormal program termination dump acquisition, register the dump file name in the program status management table, and in the case of job abnormal termination, acquire failure analysis information from the program status management table and start message acquisition processing, In addition to activating the dump acquisition process and activating the file dump acquisition process, in other cases, indexing the message information table by the failure message ID, activating the failure analysis information acquisition process, and activating the message acquisition process, After waiting for the end of the failure analysis information acquisition processing, the failure analysis information save processing is started.

The analysis information acquisition processing 13 is performed by a utility program provided by the operation system (OS), and is executed by a message acquisition processing, a memory dump acquisition processing, various failure analysis information acquisition processing, and a system management function (S
MF) Execute the dump acquisition process and the trace dump acquisition process, and output the result to each sub file of the analysis information file 14. Analysis information file (private SYSOUT)
Numeral 14 saves various sub-files output by the analysis information acquisition process 13 as failure analysis information of the user. The failure analysis information save processing 15 extracts an empty CGMT from the work tape group and saves the CGMT for storage.
Then, the failure analysis information is extracted from the analysis information file 14 based on the failure occurrence date and time and the job occurrence number, and output to the storage CGMT 17. After the output, save C
GMT 17 is discharged from the CGMT library device. The storage outage analysis information deletion processing 16 includes a failure analysis information DB 18
Then, the number of days of non-retention is obtained from the control file table, and the non-retention failure analysis information is deleted from the program state management table of the failure analysis information DB 18, and the non-retention sub-file is deleted from the analysis information file 14.

The saving CGMT 17 saves the subfile output in the failure analysis information saving process 15 in the CGMT library device, and then is discharged from the CGMT library device. The failure analysis information DB 18 stores a program status management table, a file dump information table, a memory dump information table, a message information table, and a control file table required in the failure analysis information analysis processing 12. The parameter file 19 holds various parameters for failure analysis. The failure message ID table 20 is
It holds the ID of the registered failure message.

Hereinafter, the operation of the automatic failure analysis information collection system of this example will be described with reference to FIG. In the computer system, when a failure event 101 occurs during the execution of business software or the like and a failure message 102 is output from the computer system, the failure analysis information automatic collection system 10 executes the business program or The failure message ID of the failure message 102 output by the OS and the failure message I registered in advance in the failure message ID table 20
D is collated, and when they match, a failure analysis parameter corresponding to the failure message is obtained from the parameter file 19, and the failure analysis information analysis processing 12 is started by adding the parameter. Next, the failure analysis information analysis processing 12 searches the contents registered in advance in the failure analysis information DB 18 by the failure message ID, thereby obtaining the analysis information acquisition processing 1 for each failure event.
3 and add a parameter for failure analysis to it.
Invoke the specified analysis information acquisition process. Next, in the analysis information acquisition processing 13, failure analysis information is acquired using a utility program prepared for each failure event in the failure analysis information file 103, and the obtained failure analysis information is analyzed. Output to file 14. Then, the failure analysis information output to the analysis information file 14 is saved in the storage CGMT 17 by the failure analysis information save processing 15 and is discharged from the CGMT library device. In addition, the storage outage analysis information deletion processing 16
As a result, of the failure analysis information output to the analysis information file 14, the one whose storage period has expired is deleted. Note that, instead of being output from the analysis information file 14 to the storage CGMT 17 by the failure analysis information save processing 15, the information may be output to a TSS (Time Sharing System) terminal 104.

Next, the function of the fault event extraction processing 11 will be described in detail with reference to FIG. In the failure event extraction processing 11, a failure message 1 is sent from the computer system.
When 02 occurs, all messages to be displayed on the computer system are acquired (step S101).
Then, the failure message ID table 20 is searched (step S102), and it is sequentially checked whether or not the inputted failure message ID is registered in the failure message ID table 20 in advance. If the search result (step S103) indicates that the corresponding failure message ID has not been found, the process returns to step S101 to continue collating the failure message. As a result of the search, when a corresponding failure message ID is found, the parameter file 1
9 to obtain parameters for failure analysis (step S104), and activate the failure analysis information analysis processing 13 (step S105). If the displayed message is not a registration message, ignore it.

Next, the function of the failure analysis information analysis processing 12 will be described in detail with reference to FIGS. When the failure analysis information analysis processing 12 is started by the failure event extraction processing 11, the processing is distributed to each of the following processings in accordance with the failure message ID extracted in the failure event extraction processing 11 (step S201). First, if the failure message ID is abnormal termination of the program, failure occurrence information (failure event occurrence date and time, applicable job name, job occurrence number (key information for accessing the job), program name)
Program status management table 181 in failure analysis information DB 18
(Step S202), and waits for the end of the job using the abnormally ended program. If the failure message ID is the program abnormal end dump acquisition end, the sub-file name of the dump is additionally registered in the failure analysis information DB 18 in the row having the same job occurrence number in the program status management table 181 (step S2).
03) Wait for the end of the job using the abnormally terminated program.

If the failure message ID is abnormal termination of the job, the program status management table 181 is searched by the job occurrence number in the failure message, and failure analysis information (failure event occurrence date and time, job name, job occurrence A number (key information for accessing a job), a program name, and a subfile name of a program abnormal end dump are acquired (step S204), and the following processing is performed. If there is no failure analysis information as a result of the search, it is ignored.

First, the message acquisition section at the time of occurrence of a failure event is calculated from the failure event occurrence date and time, and the message acquisition processing is started using the message acquisition section as a start parameter (step S205). , The message of the failure period is acquired in a sub-file of the analysis information file 14. Next, the memory dump acquisition process is started (step S206), and the memory dump information table 183 in the failure analysis information DB 18 is searched for by the failure program name by the message dump acquisition process 132 (FIG. 5). To get. If there is no memory dump information as a result of the search, the memory dump is not acquired. At this time, there are two formats for specifying the memory dump information. One format is a format for specifying a pair of a dump start address and a size. In this case, the memory dump acquisition processing program is activated using the acquired memory dump information as a startup parameter, and the memory dump is acquired in a sub-file of the analysis information file 14.
Another format is a JCL that starts a memory dump acquisition processing program so that the acquisition range can be specified in detail.
(Job Control Language) This format specifies a name. In this case, the designated JCL is started, and a memory dump is acquired in a sub-file of the analysis information file 14.

Next, a file dump acquisition process is started (step S207), and various failure analysis information acquisition processes 13 are executed.
4 (FIG. 5), the file dump information table 182 in the failure analysis information DB 18 is searched for the failure program name and the job name to acquire the file dump information. If there is no file dump information as a result of the search, the file dump is not acquired. At this time, there are two formats for specifying the file dump information. One format is a format for specifying a pair of a dump file name and a file type. In this case, the file dump acquisition processing program is started using the acquired file dump information as a start parameter, and the file dump is acquired as a sub-file of the analysis information file 14. Another format is to start JCL of a file dump processing program so that the acquisition range can be specified in detail.
This is a format to specify the first name. In this case, the specified JC
Start L and analyze the file dump for the information file 1 for analysis.
Acquire in 4.

If the failure message ID is a failure message other than abnormal program end, abnormal program end dump acquisition, and abnormal job end, the failure analysis information DB1
8, the message information table 184 in the failure message ID
To start the failure analysis information acquisition process for each failure message ID (step S208), and execute the individual failure analysis information acquisition process 134B for each failure information among the various failure analysis information acquisition processes 134 (FIG. 5). Execute. In this case, the job name of the failure analysis information acquisition processing program corresponding to the failure message ID is extracted, the activation JCL name of the failure analysis information acquisition processing program is designated, the designated JCL is activated, and the failure analysis information is retrieved. Obtained in the analysis information file 14. If there is no message ID as a result of the search, the failure analysis information is not obtained.

Next, the message acquisition section at the time of occurrence of the failure event is calculated from the failure event occurrence date and time, and the message acquisition processing is started using the message acquisition section as a start parameter (step S209), and the message acquisition processing 131 (FIG. 5). As a result, the message of the failure period is obtained in a sub-file of the analysis information file 14. Next, the process waits for the end of the failure analysis information acquisition process started in steps S204 to S209, and when all the failure analysis information acquisition processes are completed, starts the failure analysis information save process (step S210), and executes the failure analysis. Information save processing 15
(FIG. 6).

Next, the function of the analysis information acquisition processing 13 will be described in detail with reference to FIG. Analysis information acquisition processing 1
3 is a utility program as follows:
It is provided as part of the OS. In the message acquisition process 131, the message log file 10 in the failure analysis information file 103 acquired by the OS
From 31, a message in a designated section is extracted and output to the message print subfile 141 of the analysis information file 14. In the memory dump acquisition process 132, the memory image file (abort dump file 103) acquired by the OS when the program ends abnormally
From 2), specify the designated section as alphanumeric kana (ANK) and 16
The image is edited into a hexadecimal image and output to the memory dump sub-file 142 of the analysis information file 14. In the system evaluation information (SMF) dump acquisition process 133, the OS
System performance log (SMF) file 1 acquired by
From 033, the performance data of the designated section is extracted and edited, and output to the SMF dump subfile 143 of the analysis information file 14.

In the various failure analysis information acquisition processing 134, a file specified in the various files 1034 acquired by the OS is used as a file dump acquisition processing.
The data is edited into ANK and hexadecimal images and output to the file dump sub-file 144 of the analysis information file 14. As a file dump acquisition process for the database, the database specified in the various files 1034 acquired by the OS is temporarily converted into a sequential file, edited into an ANK and a hexadecimal image, and then analyzed. 14 file dump subfiles 14
4 is output. In the trace dump acquisition process 135, the trace data of the designated section is extracted and edited from various trace files 1035 collected as trace information by the OS and the program, and is extracted to the trace dump subfile 145 of the analysis information file 14. Output. The trace extracting / editing program is provided as a support program for the program for collecting the trace.

Next, the function of the failure analysis information saving process 15 will be described in detail with reference to FIG. At the start of the failure analysis information save processing 15, an empty CGMT is extracted from a work tape group in a CGMT library device (not shown) (step S301), and is set as a storage CGMT 17. Next, a failure analysis information sub-file (message print sub-file) created in the case of a job abnormal termination in the failure analysis information analysis processing 12 and a failure message other than program abnormal termination, abnormal termination dump acquisition termination, and job abnormal termination. 141, memory dump subfile 14
2, SMF subfile 143, file dump subfile 144, trace dump subfile 145)
Is extracted from the analysis information file 14, and the
One sub-file is output as one file to the storage CGMT 17 secured in 301 (step S302).
The extraction condition in this case is “job occurrence number” or “failure occurrence date and time” embedded in the subfile name.
Note that the conditions for giving a subfile name are described in FIG.
This is shown in the control file table of FIG. After outputting the file, the storage CGMT 17 is discharged from the CGMT library device (step S303).

Next, with reference to FIG. 7, the function of the out-of-storage analysis information deletion processing 16 will be described in detail. In the storage outage analysis information deletion processing 16, first, the failure analysis information DB
The storage days of the failure analysis information are extracted from the control file table 185 of FIG. 18, and the storage end date is obtained by subtracting the storage days from the current day (step S401). Next, from the program state management table 181 of the failure analysis information DB 18, the failure analysis information whose failure occurrence date and time is out of storage is extracted and deleted (step S402). Next, from the analysis information file 14, sub-files of the failure analysis information (message print sub-file 141, memory dump sub-file 142, SMF sub-file 143, file dump sub-file 144) for which the sub-file creation date and time are out of storage , Trace dump subfile 14
5) is deleted (step S403).

Hereinafter, various tables used in the automatic failure analysis information collection system of this example will be described. The program state management table 181 of the failure analysis information DB 18 storing the failure event information of the program described above is shown in FIG.
Has the contents exemplified in FIG. The program status management table 181 manages the name of a program in which a failure has occurred, the date and time of occurrence of the failure, and the like.

The file dump information table 182 of the failure analysis information DB 18, which stores the file dump information and the DB dump information, has the contents illustrated in FIG. The file dump information table 182 manages a file name and a database name collected when a failure occurs.

The memory dump information table 183 of the failure analysis information DB 18, which stores the memory dump information of the program, has the contents illustrated in FIG. This memory dump information table 183 manages memory area information collected when a failure occurs.

The failure analysis information acquisition target message I
The message information table 184 of the failure analysis information DB 18 storing the D information has the contents illustrated in FIG. The message information table 184 manages a message ID that triggers automatic collection of failure analysis information, failure analysis information to be collected, and the like.

The control file table 185 of the failure analysis information DB 18 storing the control information of the automatic failure analysis information collection system has the contents exemplified in FIGS. The control file table 185 manages parameter information necessary for controlling the automatic failure analysis information collection system of this example.

The criterion for assigning the storage subfile name of the failure analysis information acquired in the automatic failure analysis information collection system of this example is exemplified by a subfile name assignment rule table 186 shown in FIG. The subfile name assignment rule table 186 summarizes the rules for assigning subfile names to subfiles that hold information obtained by collecting failure analysis information.

As described above, in the failure analysis information automatic collection system of this example, when a failure event occurs, an event to be analyzed by the failure event extraction processing, acquisition of analysis parameters, The analysis information analysis process is started, the failure analysis information analysis process specifies the failure analysis information, and the analysis information acquisition process corresponding to the failure event is started. The failure analysis event is acquired and output to the analysis information file, and the failure analysis information output to the analysis information file is saved to the storage CGMT and discharged by the failure analysis event saving process. At the time of occurrence, it becomes possible to quickly execute the process of identifying the cause of the failure and acquiring the failure analysis information.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and there may be design changes within the scope of the present invention. Even this is included in the present invention. For example, in the above embodiment, the failure analysis information of the analysis information file 14 is saved and saved in the storage CGMT 17,
Although the subsequent failure analysis is performed, the present invention is not limited to this. By outputting the information from the analysis information file 14 to the TSS terminal 104, the failure analysis may be performed using the computer system in a time sharing manner. it can. As the TSS terminal 104, a printer device, a character display device, a graphic display device, or the like can be used. An automatic failure analysis information collection system according to the present invention includes a central processing unit (CPU), a RAM (Random Access Memory) serving as a work area of the CPU, and an HDD (Hard Disc) storing programs and various databases.
Drive), an input / output unit, and the like, the CPU is realized by reading and executing a failure analysis information automatic collection program stored in advance in the HDD for failure analysis information automatic collection processing. You.

[0044]

As described above, according to the present invention, an application program and middleware other than the core program in the computer system are formed by providing the computer system with the automatic failure analysis information collection system. When a fault related to a software system with a subordinate position, such as a control program, occurs, failure analysis information is automatically collected, so that when a failure occurs, information necessary for subsequent failure analysis is timely collected. In addition, it is possible to acquire the failure promptly, so that the cause of the failure and the processing for dealing with the failure can be quickly executed. Also, since such failure analysis information can be obtained automatically,
This makes it possible to automate the operation of the computer system and to save the operation of the computer system.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of an automatic failure analysis information collection system according to an embodiment of the present invention.

FIG. 2 is a flowchart illustrating a flow of a failure event extraction process.

FIG. 3 is a flowchart illustrating a flow of a failure analysis information analysis process.

FIG. 4 is a flowchart illustrating a flow of a failure analysis information analysis process.

FIG. 5 is a flowchart showing a flow of analysis information acquisition processing.

FIG. 6 is a flowchart illustrating a flow of a failure analysis information saving process.

FIG. 7 is a flowchart illustrating a flow of a process for deleting stored analysis information;

FIG. 8 is a diagram showing the contents of a program status management table.

FIG. 9 is a diagram showing contents of a file dump information table.

FIG. 10 is a diagram showing the contents of a memory dump information table.

FIG. 11 is a diagram showing the contents of a message information table.

FIG. 12 is a diagram showing the contents of a control file table.

FIG. 13 is a diagram showing the contents of a control file table.

FIG. 14 is a diagram showing the contents of a subfile name assignment rule table.

[Explanation of symbols]

 10 Failure Analysis Information Automatic Collection System 11 Failure Event Extraction Processing 12 Failure Analysis Event Analysis Processing 13 Analysis Information Acquisition Processing 14 Analysis Information File 15 Failure Analysis Information Saving Processing 16 Saved Analysis Information Deletion Processing 17 Storage CGMT (Storage Medium) ) 18 Failure analysis information database (DB) 19 Parameter file 20 Failure message ID table 181 Program status management table 182 File dump information table 183 Memory dump information table 184 Message information table 186 Control file table 186 Subfile name assignment rule table

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B042 GA01 GA10 GC17 JJ17 KK07 KK08 KK13 KK14 KK15 LA20 MA05 MA14 MB04 MC17 MC18 MC36 5B076 AA07 AA08 CA01 CA09 5B085 AA08 AC05 AC14 AC16 BA04 BG04 CA02

Claims (13)

[Claims] When a failure event occurs in a computer system, the failure event extraction process matches the failure message ID output by the computer system with a failure message ID registered in advance, thereby determining the failure event. A corresponding failure analysis parameter is acquired, a failure analysis information analysis process is started, and a failure analysis information database registered in advance by the failure message ID is searched by the failure analysis information analysis process, and the failure analysis information is retrieved for each failure event. The failure analysis information acquisition process is specified, the failure analysis parameter is added, the failure analysis information acquisition process is started, and the failure analysis information acquired by executing the failure analysis information acquisition process is replaced with the failure analysis information. The information file for analysis is provided by a utility program prepared for each event. Failure analysis automatic information collection system and outputs the. 2. The failure analysis information automatic collection system according to claim 1, wherein the failure analysis information stored in the analysis information file is saved and discharged to a storage medium. 3. The failure analysis information automatic collection system according to claim 1, wherein the failure analysis information held in the analysis information file is output to a TSS (Time Sharing System: hereinafter) terminal. 4. The failure analysis information whose storage period has expired among the failure analysis information stored in the analysis information file is automatically deleted. Automatic failure analysis information collection system. 5. The fault event extracting process includes a process of acquiring all messages displayed on a computer system, a process of comparing the message ID with a fault message ID registered in a fault message ID table in advance. 5. A process according to claim 1, further comprising the step of: acquiring a parameter for failure analysis based on the collated and matched failure message ID and activating the failure analysis information analysis process. Sampling system. 6. When the failure message ID indicates abnormal termination of the program, the failure analysis information analysis process stores the failure occurrence information in the failure analysis information database in order to wait for the end of a job using the abnormally terminated program. If the failure message ID indicates that the program has abnormally ended dump acquisition, the sub-file name of the dump is added to the program status management table in the row having the same job occurrence number. If the failure message ID is abnormal termination of the job, the program status management table is searched by the job occurrence number in the message to acquire failure analysis information, and the message acquisition section when the failure event occurs is calculated from the failure event occurrence date and time. And start the message acquisition process with the message acquisition section as the startup parameter. To obtain the message of the failure period in the analysis information file, retrieve the memory dump table in the failure analysis information database by the failure program name, acquire the memory dump information in the analysis information file, and retrieve the failure analysis information database. The file dump table in the file is searched by the failure program name and the job name, and the file dump information is acquired in the analysis information file. If the failure message ID is other than the abnormal termination, the failure analysis information database And retrieve the job name of the failure analysis information acquisition program corresponding to the failure message ID,
Start of failure analysis information acquisition program JCL (Job Control
l Language: Abbreviated below) JCL specified by acquiring the name
To obtain the failure analysis information in the analysis information file, calculate the message acquisition section at the time of the occurrence of the failure event from the date and time of the occurrence of the failure event, and start the message acquisition process using the message acquisition section as a startup parameter to start the failure. The failure analysis information automatic collection system according to any one of claims 1 to 5, comprising a process of acquiring a message of a period in the analysis information file. 7. The memory dump information is designated in the failure analysis information database by a pair of a dump start address and a size, and a memory dump acquisition processing program is started by using the acquired memory dump information as a start parameter. The failure analysis information automatic collection system according to claim 6, wherein the information for analysis is acquired in the analysis information file. 8. Specifying the memory dump information in the failure analysis information database by specifying a startup JCL name of a memory dump processing program, and
7. The automatic failure analysis information collection system according to claim 6, wherein the system is activated to acquire a memory dump in the analysis information file. 9. A method of designating file dump information in the failure analysis information database by using a pair of a dump file name and a file type, and activating a file dump acquisition processing program using the acquired file dump information as a start parameter. 7. The automatic failure analysis information collection system according to claim 6, wherein a dump is obtained in the analysis information file. 10. Designation of file dump information in the failure analysis information database is performed by designating a startup JCL name of a file dump processing program, and launching the specified JCL to store a file dump in the analysis information file. 7. The automatic failure analysis information collection system according to claim 6, wherein the failure analysis information is acquired. 11. The failure analysis information acquiring process is executed by a utility program of the basic program. In the case of a message acquiring process, a message in a specified section is extracted from a message log file acquired by the basic program. In the case of the memory dump acquisition process, the section designated by the memory image file acquired by the basic program is edited into a predetermined image at the time of abnormal termination of the program, and the analysis information file is output. In the case of the file dump acquisition process, the process consists of editing the specified file into the predetermined image and outputting the same to the analysis information file. File of the database The processing includes converting, editing into the predetermined image, and outputting to the analysis information file. In the case of the system evaluation information acquisition processing, the performance data of the specified section is specified from the system performance log file acquired by the basic program. Extraction / editing and output to the analysis information file. In the case of various types of trace information acquisition processing, the trace data of a specified section is specified from the trace files collected as trace information by the program and the basic program. The failure analysis information automatic collection system according to any one of claims 1 to 10, comprising a process of extracting / editing and outputting the information to the analysis information file. 12. The method according to claim 1, wherein the predetermined image is an alphanumeric character (A).
13. The automatic failure analysis information collection system according to claim 11, wherein the failure analysis information is a hexadecimal image. 13. A failure analysis information automatic collection program which is a program executable on a computer, and which comprises a program for executing the processing of the failure analysis information automatic collection system according to claim 1. Description: program.