JPH09134300A - Error log editing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To eliminate the need for starting an error log editing service program in every operating system of every host by performing the primary dump processing of the error log file of every host in a permanent file area and then performing the secondary dump processing to a magnetic tape device. SOLUTION: Receiving a primary dump request, an operating system sorts the error log files 7-0 to 7-n of the inter-host communication enable object hosts 2-0 to 2-n in order of the occurrence time of files and performs the primary dump processing of these error log files in a permanent file area 10. When the primary dump processing of all hosts 2-0 to 2-n are over in the areas 10, an error log editing service program carries out the secondary dump processing to a magnetic tape device 8. Thus it is not required to start an error log editing output service program in every operating system of the hosts 2-0 to 2-n with no consciousness of the number of these hosts.

Description

Detailed Description of the Invention

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an error log editing system, and more particularly to an error log editing system in a file sharing system.

[0001]

2. Description of the Related Art Conventionally, in this type of technology, an error log file of a file sharing system has been collected independently in each host. Therefore, an error log file exists for each host, and when referring to the error log of the entire system collectively, the error log edit output service program is started on each host to obtain information.

[0002]

In the above-mentioned conventional technique, each host collects an error log independently, so that the system operator needs to know the failure status of the entire system by operating system of each host. It was necessary to start the error log edit output service program each time. In addition, there is a problem in that information of individual hosts is manually merged. Further, there is a problem that the burden of this manual work increases in proportion to the number of hosts.

An object of the present invention is to provide an error log editing system in which it is not necessary to start an error log editing output service program for each operating system of each host without considering the number of hosts.

Another object of the present invention is to provide an error log editing system for collecting an error log of the entire file sharing system without manual labor.

[0005]

In order to solve the above problems, an error log editing system according to the present invention is an error log editing system for a file sharing system including a plurality of hosts and an external storage medium. Intermediate file area accessible from all hosts, primary dump means for dumping error log information of each host to this intermediate file area, and error log information of all hosts dumped to the permanent file area to external storage medium And a secondary dumping means for performing the secondary dumping.

Further, in another error log editing system of the present invention, the intermediate file area is a permanent file area.

Further, in another error log editing system of the present invention, the intermediate file area is a temporary file area.

Further, another error log editing system of the present invention is an error log editing system of a file sharing system comprising a plurality of hosts and an external storage medium, wherein a host identification value table for identifying the host and a designation The open means for comparing the determined host identification value with the host identification value in the identification value table and directly opening the error log file of the matched host, and the error log file of the host opened by the opening means are read. It is characterized by including a memory area and means for dumping the error log file read in this memory area to an external storage medium.

Further, another error log editing system of the present invention is an error log editing system of a file sharing system comprising a plurality of hosts and an external storage medium, and a permanent file area accessible from all the plurality of hosts. And a means for dumping the error log file of each host into the permanent file area, and collecting the error log of each host in parallel.

[0010]

BEST MODE FOR CARRYING OUT THE INVENTION Next, an error log editing system of the present invention will be described in detail with reference to the drawings.

Referring to FIG. 1, an error log editing system which is an example of the present invention includes a multi-host control circuit 1, a host group 2, a system-resident volume group 4, an integrated console 5, a magnetic tape device 8 and a magnetic disk device 9. And the printer 12 are connected by channel 3.

The host group 2 includes hosts 2-0, ...
2-n, each operating an operating system independently. The system resident volume group 4 is composed of system resident volumes 4-0, ..., 4-n under the respective hosts 2-0, ..., 2-n, and error log files 7-0, respectively. ..., 7-n and permanent file area 13-0, ..., 13
-N. Each time the operating system operating on each host 2-0, ..., 2-n detects an error in each hardware, each system-resident volume 4-0 ,. The error information is written in each of the error log files 7-0, ..., 7-n of 4-n. The multi-host control circuit 1 is for each host 2-0,
... The communication between hosts is performed between 2-n, and the multi-host shared memory 6 that can be shared among all the hosts is provided. The channel 3 is an interface between each host 2-0, ..., 2-n and a peripheral subsystem such as a storage device. The integrated console 5 is a man-machine interface for system startup of each host of the host group 2, command input by an operator, and job execution. The magnetic disk device 9 has a permanent file area 10 and a temporary file area 11 accessible from all hosts.

Next, a first embodiment of the error log editing system of the present invention will be described in detail with reference to the drawings.

Referring to FIGS. 1 and 2, the system operator activates the error log edit output service program 201 as one job on the operating system in an arbitrary host, and the error log is set as an edit target in this program. The host number and format information for determining the output format of the error log information requested by the system operator are given (step 2).
1). This format information includes, for example, time, device type, device name, media name and the like. The error log edit output service program 201 issues a primary dump request to the operating system of the host executing this program (step 22).

Upon receipt of this request, the operating system sends the error log files 7-0, ..., 7-n under the host to the operating system of another target host capable of communication between the hosts and the permanent file. A request for a primary dump to area 10 is issued (step 23).

The operating system of each target host that has received this request receives the error log file 7-0,
..., 7-n are sorted in the order of occurrence time, and dump processing is performed to the permanent file area 10 (step 25).
When this dump processing ends, information indicating that the dump processing of the error log file has been completed for each host is written to the error log file. This information can prevent the error log information dumped at this time from being dumped again. When the primary dump processing is completed, this operating system reports the completion to the operating system running the error log edit output service program 201 (step 26).

Upon receipt of this report, the operating system reports the completion to the error log edit output service program (step 27).

Error log edit output service program 2
01 completes the primary dump processing to the permanent file areas 10 of all the target hosts, and executes the dump processing to the magnetic tape device 8 (step 29).

Error log editing service program 201
Performs a sort process and an edit process according to the format information for sorting given when the program is started (step 2A). Output processing of the edited result to the printer 12 is executed (step 2B), and the program 20
1 ends.

Referring to FIG. 3, the primary dump file 100 of each host comprises a failure log 110 and a trace information log 120. The failure log is a log referred to by the system operator such as a failure information log when an I / O error occurs to a peripheral device, and the trace information log is a system such as trace information of an operating system table when a failure occurs. This is the log referenced by the designer.

Referring to FIG. 4, the dump file 200 generated after the end of the dump process (step 29) includes a management information record 210 and a failure log 110-of each host.
, 110-n and trace information logs 120-0, ..., 120-n of each host are arranged in this order. The management information record 210 holds the head addresses of the failure logs 110-0, ..., 110-n for each host and the trace information logs 120-0, ..., 120-n of each host. The dump file has a structure sandwiched between the management information records 210 for each error log collection operation, and each management information record 210 holds the address of the next management information record 210. Error log editing service program 2 for this dump file 200
01 Sort processing and editing processing (step 2A) are performed according to the format information given at the time of starting. For example, if the format information is time, sorting is performed in the order of error occurrence time.

As described above, in the first embodiment of the present invention, the error log file of each host is primarily dumped to the permanent file area 10 and secondary dumped to the magnetic tape device 8. It is not necessary to start the error log edit output service program for each operating system of each host without being aware of the number, and the error log of the entire file sharing system can be collected manually.

Next, a second embodiment of the error log editing system of the present invention will be described in detail with reference to the drawings.

This embodiment is different from the above-mentioned first embodiment in that the temporary file area 11 is used in place of the permanent file area 10 in the primary dump processing.

Referring to FIG. 1 and FIG. 5, the system operator activates the error log edit output service program 301 as one job on the operating system in an arbitrary host, and the error log is to be edited in this program. Information is provided to determine the host number and the output format of the error log information requested by the system operator (step 31). The error log edit output service program 301 issues a primary dump request to the operating system of the host executing this program (step 32).

Upon receipt of this request, the operating system sends the error log files 7-0, ... Issue a request to primary dump to area 11 (step 3
3).

The operating system of each target host that has received this request uses the error log file 7-0,
..., 7-n are sorted in order of occurrence time, and dump processing is performed to the temporary file area 11 (step 34). The subsequent operation is similar to that of the first embodiment described above.

In the second embodiment, the deletion processing for the temporary file area 11 is not left to the operator, but the error log editing output service program side temporarily reserves the file area and executes the deletion processing. The area 11 is deleted and the execution ends.

As described above, in the second embodiment of the present invention, the error log files 7-0, ..., 7-n are dumped to the temporary file area 11 accessible from all hosts. It is possible to use resources effectively without requiring a file area and collect error logs collectively without human intervention.

Next, a third embodiment of the error log editing system of the present invention will be described in detail with reference to the drawings.

In this embodiment, the dump processing is not directly assigned to the operating system of the host to be dumped, but is directly executed by the error log edit output service program side, so that the permanent file area or the temporary file area that has been allocated in advance can be obtained. A method that does not require a large intermediate file area is realized.

Referring to FIGS. 1 and 6, the error log edit output service program 401, which is input as a job by an arbitrary host by the system operator, is started (step 41). At this time, the host identification value indicating the host to be edited in the error log and the information for determining the output format of the error log information requested by the system operator are given, and the target host identification value is held as a table. . The host has a host identification value table that stores the host identification values of the hosts that make up the entire system, and the content of the counter indicating the content of this table is reset to 0 (step 42).
The host identification value of the host to be dumped provided by the system operator is compared with the host identification value in the host identification value table (step 44), and the error log of the host in which both match is found. The error log file is directly opened from 401, read out onto the multi-host shared memory 6, and dump processing is performed (step 45). At this time, the information in the error log is sorted by the time of occurrence. The information of the error log acquired by this dump processing is written in the magnetic tape device 8 (step 46). It is determined whether or not the series of dump processing described above has been executed for all error log files of all target hosts (step 47), and if not executed for all target hosts, the entire system is configured. A counter indicating the contents of the host identification value table of the host to be operated is incremented, and the series of operations described above is repeated for the next host. When the above operation is executed for all target hosts, the dump processing ends.

The error log merge / sort processing and various edit output processing (step 49) are the same as the processing (step 2A) described in the description of the first embodiment. Finally, output to the printer 12 (step 5
0), the error log editing service program 401 ends.

As described above, in the third embodiment of the present invention, the error log edit output service program directly opens the error log file of each host instead of leaving the dump processing to the operating system of the dump target host. I did it. Then, the data is read onto the multi-host shared memory 6. For this reason, since an intermediate file for temporarily performing the dump process is unnecessary, it is possible to efficiently and collectively edit the error log without human intervention.

Next, a fourth embodiment of the error log editing system of the present invention will be described in detail with reference to the drawings.

Referring to FIGS. 1 and 7, the error log editing service program 501 (parent job) is handled by the system operator as one job on any host i.
Is started. At the same time, the program is given information for determining the number of the host whose error log is to be edited and the form of the error log file required by the system operator. The parent job 501 is a primary dump processing execution program (child job) 502-0 ,. . . , 502-n are requested (step 51).

The operating system i0 of the host i that has received this request sends the child jobs 502- to the operating systems of all the configured target hosts.
0,. . . , 502-n start request (step 5
2). The parent job 501 confirms whether or not a communication request from the operating system i0 of the host i to the operating system of the host j (0 ≦ j ≦ n, j ≠ i) is normally received, and temporarily enters the sleep state ( Step 55).

The operating system j0 of the host j receives the request sent to each host using the inter-host communication function (step 53). This operating system j0 has child jobs 502-0 ,. . . , 5
02-n is started (step 56).

The activated child jobs 502-0 ,. . . ,
502-n reads the information of the error log file under its own host, and can access the permanent file areas 13-1 ,. . . , 13-n (step 5
7).

When all the error log file information has been written, the child jobs 502-0 ,. . . , 502
-N is completed, and the job completion notification indicates that the child jobs 502-0 ,. . . , 502-n for the host operating system j (0 ≦ j ≦ n, j ≠ i) (step 58). Child job 502-
0,. . . , 502-n confirm that the notification to the operating system j0 of their own host has been normally accepted, and end the execution (step 60).

This child job 502-0 ,. . . , 502
Host operating system j0 executing -n
Uses the inter-host communication function to execute the child job 502-
0,. . . , 502-n are normally terminated, the operating system i0 of the host i in which the parent job 501 is executing is notified (step 59).

Operating system i0 of host i
Notifies the sleeping parent job 501 of the notification of the child job execution end notification from all target hosts (step 61).

Upon receiving the report, the parent job 501 resumes the wake-up execution from the sleep state (step 62), and the error log file information 13-1 ,. . . ,
A dump process to the magnetic tape device 8 is executed by inputting 13-n (step 63).

With the dump processing completed normally and the error log information for all hosts merged into the dump file, the error log information is edited in an output format according to the purpose using this dump file as input. A merge / sort process for outputting and various edit output processes are executed (step 64). The merge / sort process and the various edit output processes that perform the edit output of this error log file
The process is the same as the process (step 2A) described in the description of the first embodiment. The execution of the parent job 501 ends when the editing result is output to the printer 12.

In the fourth embodiment of the present invention, the permanent areas 13-1 ,. . . , 13-
Although n is used as an example, the present invention is not limited to this example and various forms are included.

As described above, in the fourth embodiment of the present invention, the child jobs 502-0 ,. . . , 5
Since the 02-n are operated in parallel, the system operator can collect and edit the error log files of all the hosts to be dumped in parallel.

[0047]

As is apparent from the above description, according to the present invention, there is provided an error log editing system which does not need to start the error log editing output service program for each operating system of each host without considering the number of hosts. Can be provided.

Further, according to the present invention, the error log of the entire file sharing system can be collected manually.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration diagram of an example of an error log editing system of the present invention.

FIG. 2 is a diagram showing a processing flow of the first embodiment of the present invention.

FIG. 3 is a diagram showing an example of a temporary dump file according to an embodiment of the present invention.

FIG. 4 is a diagram showing an example of a dump file according to an embodiment of the present invention.

FIG. 5 is a diagram showing a processing flow of a second embodiment of the present invention.

FIG. 6 is a diagram showing a processing flow of a third embodiment of the present invention.

FIG. 7 is a diagram showing a processing flow of a fourth embodiment of the present invention.

[Explanation of symbols]

1 multi-host control mechanism 2-0, ..., 2-n host 3 channels 4-0, ..., 4-n system resident volume 5 integrated console 6 shared memory between multi-hosts 7-0 ,. 7-n Error log file 8 Magnetic tape device 9 Magnetic disk device 10 Permanent file area 11 Temporary file area 12 Printer 13-0, ..., 13-n Permanent file area 100 Temporary dump file 110 Fault log 120 Trace information log 200 Dump file 210 management information record

Claims (5)

[Claims] 1. In an error log editing system of a file sharing system comprising a plurality of hosts and an external storage medium, an intermediate file area accessible from all the plurality of hosts, and error log information of each host in the intermediate file area. An error log editing system comprising: a primary dump means for dumping the error log information and a secondary dump means for dumping the error log information of all hosts dumped in the permanent file area to an external storage medium. 2. The error log editing system according to claim 1, wherein the intermediate file area is a permanent file area. 3. The error log editing system according to claim 1, wherein the intermediate file area is a temporary file area. 4. An error log editing system of a file sharing system comprising a plurality of hosts and an external storage medium, a host identification value table for identifying the host, a designated host identification value and a host identification of the identification value table. Open means for comparing the values and directly opening the error log file of the matched host, a memory area for reading the error log file of the host opened by the opening means, and an error read in this memory area An error log editing system comprising means for dumping a log file to an external storage medium. 5. An error log editing system for a file sharing system comprising a plurality of hosts and an external storage medium, wherein a permanent file area accessible from all the plurality of hosts, and an error log of each host in the permanent file area. An error log editing system comprising: a means for dumping a file; and collecting error logs of the respective hosts in parallel.