JPH04135247A - Factor trace-back system at end of program abnormality - Google Patents

Abstract

PURPOSE:To enable even a user who has not so much technical knowledge to easily study the factor of an abnormal end of a program by saving the contents obtained at the abnormal end, analyzing a command given from a terminal equipment to check the saved contents, displaying the check result on a terminal equipment, and also outputting the check result after editing it. CONSTITUTION:When the abnormal end of a program occurs, an operating system displays an end code and saves the contents of a main storage. Then a user starts an analysis program 6 and produces a command through a terminal equipment 7. Thus the user reads the data necessary for study of the factor of the abnormal end out of a main storage saving part 5 and outputs these data to the equipment 7 and a printer 8. In other words, the user designates a desired place to be retrieved based on a program source list and the program 6 retrieves a program component element library 4 based on the command received from the equipment 7. Then the program 6 takes out the necessary information to refer to the part 5 and outputs this reference result to the user. Thus even such a user who has no knowledge of a program execution load module can easily study the factor of the program abnormality.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a cause weekend method when a program terminates abnormally.
In particular, the present invention relates to a weekend method for determining the cause of an abnormal termination of a program in an information processing system by using a user or a terminal device.

[Conventional technology]

The conventional weekend method is a computer system in which many online programs or batch programs are running, and when a program terminates abnormally, the cause of the abnormal termination is displayed on the terminal device using an exit code. The contents of the main memory at the time of abnormal termination were saved to the auxiliary memory. In this case, the cause has to be analyzed manually by the user by analyzing the above-mentioned termination code and saved contents.

[Problem to be solved by the invention]

The above-mentioned conventional weekend method for causing abnormal program termination requires outputting a large amount of the saved contents to the printing device and calculation of complicated addresses in the main memory, especially in order to check the contents of the main memory that have been saved. In order to do this, knowledge of the program execution load module is required, and it has the disadvantage that it takes a lot of time to find the cause.

[Means to solve the problem]

Causes when a program ends abnormally according to the present invention The weekend method uses a translation program that creates a program component library at the same time as it translates a source program into an execution load module, and saves main memory information to commands from a terminal device at the time of abnormal end. and an analysis program that analyzes the information based on the information and outputs the result to the terminal device or printing device.

〔Example〕

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of the cause weekend method when a program ends abnormally according to the present invention.

Normally, a source program 1 shown in FIG. 1 is composed of instructions and a data area, and a name is given to the data area or a group of instructions. Therefore, the translation program 2 creates an execution load module 3, and at the same time creates an index that allows the address to be searched by the above-mentioned name when analyzing an abnormal termination, and outputs this to the program component library 4.

FIG. 2 is a flowchart showing an example of the operation of the cause weekend method when a program ends abnormally in this embodiment.

As shown in FIG. 2, when the program terminates abnormally in step 21, the operating system displays an exit code and saves the main memory contents in step 22.Next, in step 23, the user The analysis program 6 is started, and in step 24, a command is given from the terminal device 7 to read data necessary for investigating the cause from the main memory saving section 5 and output it to the terminal device 7 or the printing device 8.

FIG. 3 is a flowchart showing an example of the operation of the analysis program 6 of this embodiment.

As shown in Figure 3, when analysis program 6 is started,
In step 31, commands from the user are given interactively via the terminal device 7. Then, based on the source list of the program, the user specifies the location not to be searched using the line number or name of the source list. Next, in step 32, the analysis program 6 searches the program component library 4 based on instructions from the user, and in step 3
3, the information necessary to refer to the main memory save unit 5 is extracted and the main memory save unit 5 is referred to. And step 3
In step 4, the results are output to the user.

Note that an output method such as an output device and an editing method can be specified by a user's command.

〔Effect of the invention〕

As explained above, in the weekend method for causing abnormal program termination of the present invention, when a computer system program terminates abnormally, the user can interactively give a simple command to determine the cause of the abnormal termination. This has the effect that even users with little specialized knowledge of computer systems can easily investigate.

FIG. 3 is a flowchart showing an example of the operation of the analysis program of this embodiment.

]... Source program, 2... Translation program,
3... Execution load module, 4... Program component library, 5... Main memory saving unit, 6... Analysis program, 7... Terminal device, 8... Printing device.

Claims (1)

[Claims] Mainly, when a business processing program terminates abnormally, in order to quickly inform the user of the cause, the contents at the time of abnormal termination are saved, the commands from the terminal device are input, and the commands are analyzed. We will investigate the contents of the evacuation,
A method for tracing the cause of an abnormal program termination, characterized by displaying the result on the terminal device, editing the result, and outputting the result to a printing device.