JPH08314769A - Fault information sampling method - Google Patents

Abstract

PURPOSE: To provide a fault information sampling method which supports the analysis of a fault factor by providing a step to designate the inquiry of a fault content when fault information is sampled and a step to sample the fault information as holding the state of an address space. CONSTITUTION: When abnormality occurs in an operating system provided with multiplex virtual storage function, an input means 2 informs the fault acceptance means 1 of the fault information managing program of an OS of it. The fault acceptance means 1 performs the confirmation and inquiry of the fault content from the input means 2 via the input means 2, and delivers the fault content to a fault judging means 3. The fault judging means 3 judges an inputted fault content and the state of the system, and decides a fault sampling method, and delivers it to a fault information sampling process 4. The fault information sampling process 4 outputs the fault information to a fault information output device 5, and uses it as the input information of an analyzing means 6 for fault factor. In this way, when the abnormality such as the one in which despatch is disabled after a job is executed, etc., occurs, the fault information is sampled as holding job information.

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD The present invention relates to a method for collecting fault information of an operating system capable of having a multiple virtual memory function of an electronic computer system, and in particular, execution of a job that is not dispatched after execution, has no response, or remains swapped out. In the event of an error that does not occur, when information about the table related to the job scheduling (execution control) of the operating system or the table related to the program execution status is required, the error status is retained and the failure information is collected. This is a method of collecting failure information suitable for analyzing failure factors.

[0002]

2. Description of the Related Art An operating system (described in the manual "Program Product VOS3 / AS Supervisor Overview") that can have the multiple virtual memory function of an electronic computer system is not dispatched or swapped out for some reason after the job is executed. It is necessary to have a function that collects the information necessary for analyzing the cause of failure when an error that does not occur, such as being left unattended, and forcibly terminates the job after the collection is completed. By the forced termination means, it is possible to cancel the influence on the whole system due to the suspended state of the job (memory resource secured state, state of exclusion, etc.). Further, the job can be re-executed. An example of this is the manual “Program Product VOS3 / A
S System operation ”,“ DUMP command function, C
ANCEL command (DUMP operand specification) function "
And manual "Program product VOS3 / AS
There is a "space function only for dump" described in "Center operation".

[0003]

The collection of failure information in the operating system supports investigation and analysis of the cause, repairs of defective programs, tuning of system resources (CPU, real storage device and input / output device), reliability, It is an important way to improve usability and availability. Therefore, it is necessary to collect information while maintaining the state at the time of occurrence of an abnormality, but there are the following problems with the above-mentioned conventional technology.

(1) In the information gathering by the DUMP command, since the gathering process is performed in the address space given to the designated job name, the state at the time of abnormality changes and correct information cannot be gathered. Further, the system common area can be collected from all address spaces, but the job specific area (user region or job work area) relating to the execution state of the program cannot be collected.

(2) In the case of the DUMP command or the CANCEL command (with the DUMP operand specified), it cannot be collected when the address space is in an unexecutable error. Therefore, the collection of fault information must be performed with the system stopped.

The object of the present invention is to provide a job (address space).
It is to provide a failure information collection method that supports analysis of failure factors by being able to collect failure information while maintaining the state of.

[0007]

In order to solve the above problems, the method has a step of designating a fault content inquiry when collecting fault information and a step of collecting fault information while maintaining a state of an address space.

[0008]

In the operating system capable of having the multiple virtual memory function, if an abnormality occurs such that the job is not dispatched after execution, or there is no response,
When the center manager learns from the user or the operator that an abnormality has occurred, he / she handles the fault. Make a request to collect failure information to investigate the cause of failure, and after the completion of collection, forcibly terminate the job and suppress the effect on the entire system. When a failure information collection request (such as inputting a DUMP command) is issued, the failure content is inquired. Judge the fault content that was responded (sunk, no response, swapped out, etc.) and the system status. After that, the job is set to the non-executable state in order to retain the job state. By collecting the system common area and then collecting the job unique area from another address space, the job status can be retained. After collection is completed, the job is returned to the executable state so that it can be forcibly terminated.

In this way, by determining the content of the fault and collecting the information while holding the state at the time of the fault, it is possible to reliably collect the fault information at the time of occurrence of an abnormality, and the information necessary for analyzing the fault factor. It is possible to provide a failure information collection method that can collect

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a block diagram of a management program for accepting a failure, determining a failure content, and collecting failure information when an abnormality occurs in an operating system having a multiple virtual memory function. Hereinafter, this configuration diagram will be described.

When an abnormality occurs, the input means 2 informs the failure reception means 1 of the failure information management program of the operating system. The fault receiving means 1 confirms or inquires about the fault content from the input means 2 through the input means 2,
The failure content is passed to the failure determination means 3. The failure determination means 3 determines the failure content and the system status that have been input, determines the failure information collection method, and passes it to the failure information collection processing 4. The failure information collection processing 4 outputs the failure information to the failure information output device 5 and uses it as the input information of the failure factor analysis means 6.

FIG. 2 is a table showing the input contents related to the failure receiving means. The table diagram will be described below.

When an error occurs that the job executed in the electronic computer system is not patched after execution, does not respond, or remains swapped out, the input means 2 is used to notify the operating system of collection of failure information. This is the content to be specified. Job name input section 2-
Specify the job name (job identifier) where the error occurred in 1,
The abnormality content input unit 2-2 specifies an abnormality content identifier such as not dispatched, no response, or swapped out, and the collected information input unit 2-3 schedules an operating system job necessary for analyzing the cause of failure. An input unit is provided for designating a collection information identifier representing a table name related to the table or a table name related to the execution state of the program.

FIG. 3 is a table diagram of a system common area table management section and a job unique area table management section related to a job (address space) for determining the failure content. The table diagram will be described below.

In the operating system capable of having the multiple virtual storage function, the tables and programs relating to the execution status of jobs are included in the system common area table section 3-1 and the job unique area table section 3-2. The system common area table unit 3-1 includes an address space management unit 3-1-1 that can determine the execution state of a job (address space) from all address spaces. The address space management unit can determine the job status even when an error occurs in which the address space cannot be executed. The address space management unit 311 includes a job name 3111, an address conversion segment table 3112 for converting a virtual address of the multiple virtual storage function into a real address, information 3113 indicating an execution state of the address space, and a flag 3114 for controlling failure information to be collected. Information 3115 indicating the state of the program being executed in the address space and address 3116 indicating the job unique area table are provided.

The job unique area table unit 3-2 manages detailed information of a program (task) actually executed in a job (address space), a table 321 relating to execution control of the task, and a virtual of virtual storage function. An address conversion page table 322 for converting an address into a real address, a table 323 for controlling the state of a program loaded from an external storage device, and an area 324 loaded with the program are provided. It is possible to judge an abnormal state and collect failure information by using these tables and areas.

FIG. 4 and FIG. 5 are flowcharts of the fault information collection processing. Hereinafter, this flowchart will be described.

40 The job name input section is compared with the job name storage section of the address space management section of the system common area to obtain the error occurrence address space management section.

41 The collection information is obtained by comparing and judging the abnormality content input section and the collection information input section with the information related to the job in the obtained address space section.

42 As a result of comparison and judgment, it is checked whether or not the address space has a failure. If NO, it ends. If YES, the process of 43 is performed.

43 In order to maintain the state at the time of abnormality, the address space execution state flag is set to the inhibition state.

44 It is checked whether or not it is necessary to collect the system common area table section. If YES, the process of 47 is performed. NO
If so, the process of 45 is performed.

It is checked whether or not it is necessary to collect the 45 job unique area table section. If NO, the process of 46 is performed. If YES, 48 processing is performed.

The 46 address space execution status flag is reset to the stopped status and the processing is terminated.

The 47 system common area is output. Then, the process of 45 is performed.

It is checked whether the 48 faulty address space is in the swap-out state. If NO, the process of 49 is performed. If YES, 50 processes are performed.

The contents of the job unique area table portion of the faulty address space are read out by the address conversion by the 49 access register conversion. Output the read contents. afterwards,
The process of 46 is performed.

50 The contents of the job specific area table portion of the faulty address space stored in the auxiliary storage device are read out using the swapping function. Output the read contents. Then, the process of 46 is performed.

[0030]

According to the present invention, in an operating system capable of having a multiple virtual memory function,
It is possible to provide a failure information collection method in a computer system that enables collection of failure information while maintaining the status of the job when an abnormality occurs such that the job is not dispatched after execution or there is no response.

Since the information can be collected while maintaining the job status, it is possible to collect the fault information and analyze the cause of the fault without fail, thereby improving the efficiency of program maintenance, shortening the analysis time, and improving the center service. It is possible to provide a method of collecting fault information in an electronic computer system that enables it.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an abnormal occurrence, a failure information collection request process, and a failure content determination and collection process in a multiple virtual storage function.

FIG. 2 is a table diagram of failure reception means.

FIG. 3 is a table diagram of failure determination means.

FIG. 4 is a flowchart (part 1) of failure information collection processing.
Is.

FIG. 5 is a flowchart (part 2) of failure information collection processing.
Is.

[Explanation of Codes] 1 ... failure acceptance means, 2 ... input means, 2-1 ...
Job name input section, 2-2 ... Abnormality content input section, 2-3 ... Collection information input section, 3 ... Failure determination means, 3-1 ... System common area table section, 3-1-1 ... Address space management section, 3111 ... Job name storage section, 3112 ... Address conversion segment table storage section, 3113 ... Address space execution status flag, 3114 ... Fault information collection control flag, 3115 ... Program execution status flag, 3116
... job unique area table section address, 3-2 ... job unique area table section, 321 ... task control table section, 322 ... address conversion page table storage section, 32
3 ... Program control table section, 324 ... Program loading area section, 4 ... Fault information collection processing, 5 ... Fault information output device, 6 ... Fault factor analysis means.

Claims (2)

[Claims] 1. In an operating system capable of having a multiple virtual memory function for a job (batch processing program, online transaction processing program and conversation processing program) executed in an electronic computer system, when an error occurs in which a job is not scheduled after execution. , A failure information collection method having a step of inquiring about the content of the failure and designating the failure information collection while judging the system state. 2. A fault information collecting method having a step of collecting fault information while maintaining the status of a job when an abnormality occurs without stopping the operating system by the fault information collecting method.