JPS61216049A - System supervisory system - Google Patents

Abstract

PURPOSE:To grasp the working state of each program by supervising the presence or absence of a response with respect to a supervisory interruption transmitted to a wording program and considering the program to be a trouble when a normal response is not present. CONSTITUTION:When the supervisory interruption 21-1 is received from a system supervising equipment 3, a supervisory monitor 221 in the program 21 supervises a period from the time when the execution of a subtask 212 starts to the time when the execution terminates, and considers the subtask 222 to be normal when it terminates during the prescribed period and to be a trouble when it does not terminate. In such a way the supervisory monitor 211 suppresses the response with respect to the supervising equipment 3 when a trouble develops on the execution of a business program 212. If the supervisory monitor 211 itself is troubled, naturally the response with respect to the supervising equipment 3 is not returned. Actions of supervisory monitors 221 and 231 in programs 22 and 23 and those of business programs 22 and 232 are equal to that of the program 21.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Application of the Invention] The present invention relates to a system monitoring method, and particularly to a system monitoring method for ascertaining the operating status of a program running in a central processing unit of a computer.

[Background of the invention]

2. Description of the Related Art In a system monitoring system for an electronic computing system, a technique for reporting a failure to a monitoring device when a failure occurs in a device constituting the system is well known. However, recently there has been an increasing need to understand the situation leading up to the occurrence of a failure. For example, as seen in Japanese Patent Laid-Open No. 59-125967, there is a monitoring system that collects and records past failure information for each device. is also being carried out. However, although this technology can acquire the failure history of each device, it does not mention the technology of acquiring the operation history of programs running on the central processing unit 4&, and it is hoped that the technology will advance in this direction. .

[Purpose of the invention]

SUMMARY OF THE INVENTION An object of the present invention is to solve the above-mentioned problems, and to provide a system dramatization method for acquiring operation history information of a program running on a central processing unit.

[Summary of the invention]

The present invention is a system monitoring method comprising a central processing unit on which a program is run and a system monitoring device that monitors the operating status of the program, wherein the program is started or terminated by the system monitoring device when the program is started or terminated. When a monitoring interrupt is received from the system monitoring device, the response is returned to the system monitoring device, and the system monitoring device monitors the response to the monitoring interrupt sent to the program and sends a normal response. The system is characterized by a system monitoring method that considers the failure of the program when there is no failure, and records the start and end of the program, the identification of the failure, and the time.

[Embodiments of the invention]

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a configuration diagram of a system according to the present invention. 11
．． 12. 13 is the central processing unit of the computer; 3 is the system monitoring device commonly connected to these 4 devices; 5
1, 52, and 53 are central processing units 11 and 12, respectively.
, 11 and the system monitoring device 5, and provides direct control.

It is a transmission line based on the communication line interface specifications, etc. 21, 22, 25, and 24 are programs executed by the central processing unit; in the example of FIG.
Although shown for an example executed by the central processing unit @Tt1S, a certain program may be executed by another central processing unit. 21-1゜22-1.23-1 and 24-
1 are programs 21, 22, 23 and 2, respectively.
Issue a monitoring interrupt from the system monitoring device 3 to 4,
This shows the state in which the response returns to system monitor @#5.

FIG. 2 is a block diagram showing the configuration of the system monitoring device 3. As shown in FIG. Adapter 50-1, 30-2, and 30-3
are central processing units 11, 12 . and 13, and controls data transfer between each central processing unit and the system monitoring device lt5. The control mechanism 31 is a part that controls the entire system monitoring device 3, and the central processing unit 4!
The clock mechanism 32 is a part that issues monitoring interrupts to devices 11, 12, and 13 and receives responses thereto.The clock mechanism 32 is a clock that provides time for the program's operation history, and also handles monitoring It also serves as a timer used by the pressure control mechanism 31 to monitor the issuing interval and response time.The memory@f53 is a storage device in which program operation history information collected by the control mechanism 31 is stored.Editing mechanism 34 is a mechanism for editing the operation history information of the program stored in the memory value/location 33;
6 is a display device to which program history information edited by the editing mechanism 34 is output. The keyboard 37 is an input device through which an operator provides input information to the system monitoring device 3, such as specifying a program for which history information should be displayed.

FIG. 3 is a configuration diagram showing the configuration of programs in the central processing units @IIt, 11 and 12 and the bad reputation of the system monitoring device 3. Operating system (O8)
20 is the program 21 or the programs 22 and 2
This is a control program that intervenes between the system monitoring device 3 and the system monitoring device 3, and is a program that manages and controls these programs.

The program 21 is a monitoring monitor 211 and a business program 2.
It consists of 12. The monitoring monitor 211 checks the operating status of the business program 212 and
0 to the system monitoring device 3 to start and stop monitoring.

Also, when receiving the monitoring interrupt 21-1 from the system monitoring value #3 via 0820, if the business program 212 is operating normally, the system monitoring interrupt 21-1 is sent via 0820.
A response is returned to 11. The monitoring monitor 211 usually runs as a main task, and the business program 212 runs as a subtask. Therefore, checking the operating status of the business program 212 means that, for example, the monitoring monitor 211 monitors the time from the start of execution to the end of this subtask, and if the subtask ends within a predetermined time, it is considered normal, and the subtask ends within the predetermined time. Otherwise, it is considered as a failure of the subtask, that is, a failure of the business program 212. In this way, the monitoring monitor 211 suppresses the response to the system monitoring device 3 if mW is generated while executing the business program 212.

Stop. Moreover, if a failure occurs in the monitoring monitor 211 itself,
Of course, no response is returned to system monitor-jli-1t5. Monitor 2 in program 22 or 23
21 and business program 222 or monitoring monitor 23
1 and the operation of the business program 232 are also exactly the same as in the case of the program 21 described above.

In addition, program 24 that operates in other central processing #13
The same applies to

FIG. 4 is an example of a procedure showing the communication status of commands and responses for system monitoring between the system monitoring aits and the programs 21 and 22. The first two digits of the numbers in parentheses following monitoring interrupts, responses, and monitoring stops are program identification symbols; for example, 10 indicates program 2.
1 and 20 indicate a program 22. The last two digits indicate the type of command or response; 01 is a monitoring start command or its response, 02 is a monitoring interrupt or its response,
03 indicates a monitoring stop command or its response.

Below is an example of this system monitoring procedure above.

The operation of this embodiment will be explained with reference to the explained components. First of all, the director of Program 21.

Visual monitor 211 via 0820 and transmission line 51.

and sends a monitoring start command (1001) to the system monitoring device 3.
), this is the system monitoring device.

The control mechanism 31 receives this command and sends a monitoring start response (100
1), this information and the clock mechanism 32
The time obtained by The editing machine 5134 edits the information written in this memory@1f55 to create output information for the display S6. The response (1001) is sent to the monitor 211 of the program 21 via 0820. Next, control mechanism 3
1 issues a monitoring interrupt (1002) periodically, and this
320 to the monitoring monitor 211 of the program 21, and since the business program 212 is normal, the monitoring monitor 211 sends a monitoring interrupt response (
1002) is returned. The control mechanism 31 uses the clock mechanism 32 to monitor the time until the monitoring interrupt response (1002) is returned. In this way, you can monitor your system at regular intervals! The sequence of sending a supervisory interrupt (too2) by ft5 and transmitting a supervisory interrupt response (1002) from the program 21 continues. Also, when the program 22 issues the start monitoring (2001), it is processed by the system monitoring device 3 in the same way as above, and the start monitoring response (2001) is processed by the system monitoring device 3.
) is returned. Next, system monitoring value #3 is program 2
A monitoring interrupt (2002) is periodically issued to the program 22, and the program 22 returns a monitoring interrupt response (2002).

In this way, system monitoring device 3 and program 21
When the monitor 211 detects a fault in the business program 212 or a fault occurs in the monitor 211 itself during the program 21 while communication of monitoring interrupts and their responses continues between the system monitoring device 3 and the system monitoring device 3. The program 21 responds to the monitoring interrupt (1002) issued by
Since no response is returned from the control mechanism 31, the control mechanism 31 detects a timeout of the time monitoring. The control mechanism 31 regards this as a failure of the program 21 and stores this failure information and the time obtained by the clock mechanism 32 into the storage device 33. The editing mechanism 34 edits the information written in the storage device 35 to create output information for the display 36. Further, the program 22 issues a monitoring stop (2003) indicating the stop of the program for the system monitoring value #3.

, the control mechanism 31 responds to this command with a monitoring stop response (2
oos), write this information and the current time to the storage device 33, and then execute the program 2 in the same manner.
Information on the stoppage of monitoring regarding No. 2 and its time are recorded as operation history information.

Time 41 is the time when the system monitoring device 3 puts the program 21 under the monitoring state, and time 42 is the time when the program 22 is put under the monitoring state.

FIG. 5 is a flowchart showing the flow of processing in the control mechanism 31. The control mechanism 31 includes a central processing unit (tll,
Check whether the information sent from 12 and 15 is a monitoring start code. If it is a monitoring start code, the specified program is system monitoring! ! 113, and if not, an alarm is output and a message is output on the display 36 via the input/output control section 55. If the program has been registered, the start information and start time of the storage area 17c in the storage device 153 corresponding to the program identification symbol are recorded. Next, the control mechanism 31 starts monitoring the program, issues a monitoring interrupt at regular time intervals, and monitors whether there is a response within the monitoring time. If there is no response to the monitoring interrupt, the failure information and time are recorded. When the response to the monitoring interrupt is to stop monitoring or when a command to stop monitoring is received from the program, stop information and stop time are recorded.

FIG. 6 shows the format of program operation history information recorded in the storage device 33. The storage IAatss is divided into areas for storing operation history information for each program. For example, area 55-1 is program 21
The area 33-2 is for the program 22, and the area 55-4 is for the program 24. (each two in this area) IJ
consists of a field 51 in which the time is written and a field 52 in which a symbol indicating the start of monitoring, failure, or termination of monitoring is written.

Finally, returning to FIG. 2, the operation of the editing mechanism 34 will be explained. When the operator specifies a program distinction symbol from the keyboard 37 and issues an operation history output command, this command input via the input/output control unit 35 is interpreted by the control mechanism 31, and then the editing mechanism 34 is activated. be done. The editing mechanism 34 stores information about the specified program in the storage device 33.
Extract the operation history information from , edit it, and display it on display 3.
Output on 6. The statistical information to be output according to the parameters input by the operator includes, for example, the operating status of the program during a certain period, the change in program operating rate, the number of failures per month, and the distribution of the number of failure hours per occurrence. is possible.

Note that if the computer is not operated 24 hours a day, and the computer operation end time elapses during a program failure, there may be cases where an accurate failure time cannot be determined. In this case, if the operation end time is constant, the editing mechanism 54 can correct the program operation time or failure time based on this time. If this time is not constant, by commanding the end of operation from the keyboard 37, the editing mechanism 34 creates operation history information with this time as the time for forced termination of the program, and the editing mechanism 34 uses this information to Program run time or failure time can be compensated.

〔Effect of the invention〕

According to the system monitoring method of the present invention, since the operating status of each program can be ascertained, accurate program operation history information can be obtained.

[Brief explanation of the drawing]

Fig. 1 is a block diagram showing an example of the system configuration, Fig. 2 is a block diagram showing an example of the system monitoring @Fugu, Fig. 3 is a block diagram showing an example of the program structure in the central processing @
The figure shows communication between the system monitoring device and the program++
FIG. 5 is a flowchart showing the processing flow of the control mechanism in the system monitoring device, and FIG. 6 is a diagram showing the format of the operation history information stored in the storage device of the system monitoring device. be. 11.12. L5...Central processing unit, 21-24...
- Program, 211.221.251... Surveillance monitor, 3... System monitoring device. 1st Figure 2 Figure 5 + Figure 5

Claims (1)

[Claims] 1. A system monitoring system comprising a central processing unit on which a program is run and a system monitoring device that monitors the operating status of the program, wherein the program instructs the system monitoring device to start or end the program at the time of starting or ending the program. In addition, when a monitoring interrupt is received from the system monitoring device, the response is returned to the system monitoring device, and the system monitoring device monitors whether there is a response to the monitoring interrupt sent to the program and detects a normal response. A system monitoring method characterized in that if the program does not exist, it is regarded as a failure of the program, and the start and end of the program, identification of the failure, and the time thereof are recorded.