JP2004362495A - Error log information analysis support method, execution device, and processing program - Google Patents

Abstract

[PROBLEMS] Even if a plurality of second programs used by a first program in which an error has occurred are executed and a plurality of pieces of log information of the second program exist, log information necessary for error correction can be efficiently provided. Provide a technology that can collect and support error correction quickly.
An error log information analysis support method for supporting analysis of error log information, comprising the steps of: specifying an error-occurring second program used by a first program in which an error has occurred; Reading the log information of the identified second program generated during the execution time of the first program to create log information display data, and creating the log information display data And supporting the correction of the error that has occurred.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an error log information analysis support device that supports analysis of error log information, and in particular, in an environment in which a plurality of middlewares operate, error log information that supports analysis of error log information when a job that calls each middleware is executed. The present invention relates to a technique that is effective when applied to an analysis support device.
[0002]
[Prior art]
In a conventional computer system, various middleware such as DBMS (Database Management System) and OLAP (Online Analytical Processing) are used, and a user executes a job in which a command for calling those functions is described as a source file. By doing so, it is possible to execute various middleware processes.
[0003]
In the above-described computer system, for example, when an error occurs during execution of a job using the DBMS, error log information indicating the content is recorded as DBMS middleware log information. By collecting the corresponding error log information from the log information of the DBMS middleware, it is possible to investigate the cause of the error occurrence of the job.
[0004]
In addition, as a conventional technique for assisting in investigating the cause of such an error, an information collection / analysis device capable of associating a source program with log information, and information necessary for searching for an error location are set in advance. There is a program error analysis support system or the like that can search for an error occurrence location (for example, see Patent Document 1 or 2).
[0005]
[Patent Document 1]
JP-A-9-259011
[Patent Document 2]
JP-A-9-81418
[0006]
[Problems to be solved by the invention]
In the above prior art, no consideration is given to the environment in which a plurality of middlewares operate, so if an error occurs in a job that uses a plurality of middlewares, the error log information corresponding to the error of the job will indicate which middleware It is not possible to specify whether the information is recorded in the log information. For this reason, in order to check the cause of the error, it is necessary to check all log information generated by the plurality of middlewares in operation or to perform the following operation.
[0007]
First, the abnormal end date and time of the job is checked from the log of the job control middleware, and the most recent error before the date and time is checked by the OS (Operating System) log. From the error log of the OS, determine the middleware that issued the error, look at the middleware log file, examine the error message manually, and then refer to the source file of the program to see where the error could be caused. If the cause of the error is found, correct it.
[0008]
As described above, in the related art, when an error occurs in an environment in which a plurality of middlewares operate, it is necessary to execute the above-described procedure when correcting the error, which is extremely time-consuming. .
[0009]
An object of the present invention is to solve the above-mentioned problem, and to correct an error even when a plurality of second programs used by a first program in which an error has occurred are executed and a plurality of pieces of log information of the second program exist. It is an object of the present invention to provide a technology capable of efficiently collecting necessary log information and quickly supporting error correction.
[0010]
[Means for Solving the Problems]
According to the present invention, in an error log information analysis support device that supports analysis of error log information, error log information of a second program used by a first program in which an error has occurred is collected within the execution time of the first program. Is displayed.
[0011]
According to the present invention, when a function of a second program such as middleware for executing the processing of the command is called from a first program such as a job in which various commands are described, the first processing is performed when the various processing is executed. When an error occurs in the program, first, the one in which the error has occurred is specified among the second programs for executing the command processing in the first program in which the error has occurred.
[0012]
Next, the log information of the specified second program is referred to, the error log information generated within the execution time of the first program is read out of the log information, and the log information including the error log information is read out. Create display data. Then, the contents of the first program in which the error has occurred and the created log information display data are displayed, and the correction of the occurred error is supported.
[0013]
As described above, according to the present invention, for the second program that executes the command processing in the first program in which an error has occurred, error log information generated within the execution time of the first program is collected and displayed. Even when a plurality of middleware as the second program are executed and a plurality of pieces of middleware log information are present, only the log information related to the first program in which the error has occurred is selected and displayed. It is possible to efficiently assist in error correction.
[0014]
As described above, according to the error log information analysis support apparatus of the present invention, the error log information of the second program used by the first program in which an error has occurred is collected and displayed within the execution time of the first program. Even when a plurality of second programs used by the first program in which an error has occurred are executed and a plurality of pieces of log information of the second program exist, log information necessary for error correction is efficiently collected. In this way, it is possible to quickly perform error correction support.
[0015]
BEST MODE FOR CARRYING OUT THE INVENTION
An error log information analysis support device according to an embodiment that supports analysis of error log information will be described below.
[0016]
FIG. 1 is a diagram showing a schematic configuration of the error log information and source file display system of the present embodiment. As shown in FIG. 1, in the system configuration of the present embodiment, a server 3 and a client 1 are connected via a network 5.
[0017]
The client 1, which is an error log information analysis support device, includes an error log investigation processing unit 7 that supports analysis of error log information. In the present embodiment, the client 1 performs processing performed on the server 3 side. Investigate the error log.
[0018]
FIG. 2 is a diagram showing details of the error log investigation processing unit 7 shown in FIG. 1 of the present embodiment and an example of information used by the error log investigation processing unit 7. As shown in FIG. 2, the error log information analysis support device of this embodiment includes a job execution confirmation screen display / error job selection unit 17, a source file tree structure analysis unit 18, an error job use middleware investigation unit 19, a middleware It has an identification unit 20, a log information display table creation unit 21, a tree structure creation unit 22, an error log / source file display unit 23, and an error correction support unit 24.
[0019]
The job execution confirmation screen display / error job selection unit 17 is a processing unit that displays a screen for confirming execution of a job and accepts selection of an error job. The source file tree structure analysis unit 18 is a processing unit that analyzes a source file constituting a job and generates a source file tree structure 26 indicating the structure.
[0020]
The error job use middleware checking unit 19 is a processing unit that checks the middleware used by the job in which the error has occurred. The middleware specifying unit 20 is a program specifying unit that specifies the middleware used by the job in which the error has occurred and in which the error has occurred.
[0021]
The log information display table creator 21 reads out the log information of the specified middleware generated during the execution time of the job, and creates a log information display table 33 of the specific job. A data creation unit, and when an error occurs in another job within the execution time of the job in which the error has occurred, the log information in the log information display table 33 of the created specific job is This is a processing unit that sets corresponding log information to indicate whether the log is a corresponding one.
[0022]
The tree structure creation unit 22 stores, in the source file group 15 constituting the job in which the error has occurred, specific middleware use information indicating a source file using the specified middleware, in the source file tree structure of the job. 26 is a processing unit to be set.
[0023]
The error log / source file display unit 23 is a processing unit that displays error log information and corresponding source files. The error correction support unit 24 is a processing unit that displays the created log information display table 33 of the specific job and supports correction of the generated error.
[0024]
Error log information analysis support device displays job execution confirmation screen / error job selection unit 17, source file tree structure analysis unit 18, error job use middleware investigation unit 19, middleware identification unit 20, log information display table creation unit 21, tree A program for functioning as the structure creation unit 22, the error log / source file display unit 23, and the error correction support unit 24 is recorded on a recording medium such as a CD-ROM, stored on a magnetic disk or the like, and then loaded into a memory. Shall be executed. The recording medium for recording the program may be a recording medium other than the CD-ROM. Further, the program may be installed from the recording medium to the information processing apparatus and used, or the recording medium may be accessed through a network to use the program.
[0025]
FIG. 7 is a diagram showing operations and display screens from the selection of an error job to the display of an error log and a source file according to the embodiment. First, when an error occurs, the job in which the error has occurred is displayed on the job execution confirmation screen 50 of FIG. When the selection of the job (here, JOB_C) from which the error is to be corrected is received from the displayed jobs, the job execution confirmation screen display / error job selection unit 17 is executed, and the selection is made as shown in FIG. The job error candidate middleware list 52 is displayed. Following this display, the source file tree structure analysis unit 18 and the error job use middleware investigation unit 19 are executed in the background.
[0026]
Next, when the selection of the error occurrence time and the error occurrence middleware name 55 is received, the middleware specifying unit 20, the log information display table creating unit 21, and the tree structure creating unit 22 are executed. Here, the middleware specifying unit 20, the log information display table creating unit 21, and the tree structure creating unit 22 may be executed without accepting the selection operation of the error occurrence time and the error occurrence middleware name 55.
[0027]
Next, when a log display button 56 is clicked, a DBMS log screen 58 of JOB_C is displayed as shown in FIG. In addition, upon receiving a click of the file display button 57, an error cause source file display screen 64 is displayed as shown in FIG. When the cause of the error is identified by referring to the JOB_C DBMS log screen 58 and the error cause source file display screen 64, a click of the error correction button 63 is accepted, and candidates for correction items are displayed on the screen. Accept the selection of the item you want to modify. As a result, a correction screen is displayed, and the user corrects the error on this screen.
[0028]
Hereinafter, each figure will be described in detail.
As shown in FIG. 1, the client 1 and the server 3 are connected via a network 5 and have client holding information 2 and server holding information 4 respectively. The client 1 has a job control middleware client 6 and an error log investigation processing unit 7. The client holding information 2 includes a middleware command list 8, middleware log management information 9, and environment parameter related information 10. Has become. The server 3 has middleware such as DBMS middleware 11 and OLAP middleware 12, and the server holding information 4 includes a middleware log 13, job control middleware error information 14, a source file group 15, and job net information 16. ing.
[0029]
Here, the respective functions of the server 3 and the client 1 may be executed by either computer, and the respective information of the client retained information 2 and the server retained information 4 may be retained by either computer. Alternatively, these may be assigned to one computer.
[0030]
As shown in FIG. 2, the middleware command list 8 is information relating commands and middleware in order to investigate middleware used in a source file of an error job.
[0031]
The middleware log management information 9 holds a directory in which log information of each middleware is stored, a middleware log directory structure 27 that holds information on file names, and information on what format the log information is written in. It consists of a log format 28. By using this information, the error log investigation processing unit 7 can analyze the log information.
[0032]
The environment parameter related information 10 includes a log-environment parameter related information 29 having environment parameters related to log information, a directory in which environment parameter information of each middleware is stored, and an environment parameter directory having file name information. It consists of a configuration 30. By using this information, it becomes possible to automatically display environmental parameters related to the generated error log information.
[0033]
The middleware log 13 is log information of middleware executed by the server, and a plurality of pieces of log information are stored for each middleware.
[0034]
The job control middleware error information 14 is information stored in the job control middleware, and holds information relating to a job and a source file, error information, start time, and end time. By using this information, when the user selects an error job, information on the source file, start time, and end time of the job can be obtained.
[0035]
The source file group 15 is all source files of the job executed by the server 3.
The job net information 16 is information held by the job control middleware. The job net information 16 holds inter-job related information 31 that is information of a job execution sequence and job-source related information 32 that is information of a source file to be executed as a job. ing. By using this information, the job control middleware can execute the jobs in a predetermined order.
[0036]
The job execution confirmation screen display / error job selection unit 17 receives the job control middleware error information 14 as input, displays the job execution status, receives an error job selection from the user, and outputs error job information 25. The source file tree structure analysis unit 18 receives the job net information 16 and the source file group 15 as input, and outputs a source file tree structure 26.
[0037]
The error job use middleware checking unit 19 receives the source file tree structure 26 and the middleware command list 8 as inputs, and checks the middleware used in the error job. The middleware specifying unit 20 receives the middleware log management information 9 and the middleware log 13 as inputs, and specifies middleware in which an error has occurred. The log information display table creation unit 21 receives the environment parameter related information 10 as input, edits log information for display, and outputs a log information display table 33 for a specific job.
[0038]
The tree structure creating unit 22 creates a display tree structure including specific middleware use information indicating a source file using the specified middleware. The error log / source file display unit 23 displays log information, related environment parameters, a tree structure, and a source file. The error correction support unit 24 displays a screen for correcting the identified cause of the error. Thereby, error log information corresponding to the error job can be displayed.
[0039]
Here, the job control middleware error information 14 and the job net information 16 are information held by the job control middleware, and the middleware log management information 9, the environment parameter related information 10, and the middleware command list 8 are prepared for this system. Data.
[0040]
Next, the operation of the error log investigation processing unit 7 will be described. The error log investigation processing unit 7 accepts the selection of a job that has caused an error from the job net displayed by the job execution confirmation screen display / error job selection unit 17. Then, the source file tree structure analysis unit 18 examines the source file called from the selected job based on the job-source related information 32, and analyzes the files of all layers called from the source file. I do.
[0041]
The error job use middleware checking unit 19 checks the commands registered in the middleware command list from all the files analyzed by the source file tree structure analyzing unit 18 and checks the middleware used in the selected job.
[0042]
The middleware specifying unit 20 searches the used middleware log for error log information generated during the error job execution time, based on the middleware log directory configuration 27, the log format 28, and the middleware log 13. The error found here is the cause of the error of the selected job.
[0043]
The log information display table creation unit 21 converts the log information into an easily viewable format and stores the log information in the log information display table 33 of the specific job. The tree structure creation unit 22 stores in the source file tree structure 26 specific middleware use information indicating whether the middleware specified by the middleware specifying unit 20 is used.
[0044]
The error log / source file display unit 23 displays the error log, the file tree structure, and the source file of the error cause. The error correction support unit 24 displays an editing screen when the user corrects based on the information displayed on the error log / source file display unit 23.
[0045]
FIG. 3 is a flowchart illustrating a processing procedure of the middleware specifying unit 20 of the present embodiment. The execution time indicating the start time and the end time of the error job is obtained from the error job information 25 (step 34), and then the used middleware checked by the error job use middleware checking unit 19 is obtained (step 35).
[0046]
The middleware log 13 is checked on the basis of the middleware log management information 9 on the used middleware obtained in step 35, and whether or not error log information is generated within the execution time obtained in step 34 is checked. If it is extracted (step 36).
[0047]
Next, the error occurrence time and the error occurrence middleware name in the extracted log information are displayed in the selected job error candidate list window (step 37).
[0048]
FIG. 4 is a flowchart illustrating a processing procedure of the log information display table creation unit 21 according to the present embodiment. In step 38, the middleware log management information 9 and the middleware log 13 are acquired. In step 39, the middleware log 13 is analyzed based on the log format 28, and in step 40, the specific middleware log information within the execution time is edited as a log information display table 33 for the specific job.
[0049]
FIG. 5 is a flowchart illustrating a processing procedure of the tree structure creation unit 22 of the present embodiment. It is checked whether or not all the files in the source file tree structure of the selected job use the specified middleware (step 41). If the specified middleware is used, the source file tree structure table is used. Then, specific middleware use information indicating that the specified middleware is being executed is stored (step 42).
[0050]
FIG. 6 is a flowchart showing a processing procedure of the error correction support unit 24 of the present embodiment. First, when the user specifies a correction portion on the screen of the error log / source file display section 23, the user clicks the error correction button 63 (step 43).
[0051]
Next, correction item candidates are displayed on the screen (step 44), and selection of an item to be corrected is accepted (step 45). A screen for changing the number of programs to be executed at the same time according to the selected correction item is displayed (step 47), an environment parameter editing screen is displayed (step 48), and a source file editing screen is displayed (step 48). Step 49) is performed, and the user corrects the error on this screen. Here, the correction items (step 47, step 48, step 49) may be other items. The editing of the environment parameters and the editing of the source file may be performed on the JOB_C DBMS log screen 58 and the error cause source file display screen 64.
[0052]
FIG. 7A shows a screen of the job execution confirmation screen display / error job selection unit 17. The job execution status can be confirmed on the job execution confirmation screen 50 at the time of job execution or after execution. When an error occurs, the display attribute is changed and displayed like the job display 51 of JOB_C.
[0053]
Upon receiving a click on the job in which the error has occurred, the list of selected job error candidate middleware 52 shown in FIG. 7B is displayed. This corresponds to step 37. Here, the selected job name 53, the error occurrence time, and the error occurrence middleware name 55 are displayed.
[0054]
When the selection of the error occurrence time and the error occurrence middleware name 55 and the click of the log display button 56 are accepted, the DBMS log screen 58 of JOB_C in FIG. 7C is displayed. The log information 61 is log information converted into an easy-to-view format. The environment parameter information is an environment parameter related to the log information 61.
[0055]
Further, upon receiving a click on the file display button 57 of the selected job error candidate middleware list 52, an error cause source file display screen 64 shown in FIG. 7D is displayed, and upon receiving a click on a file name in the file tree structure 66, The contents of the file selected in the file tree structure 66 are displayed in the selected file source code 67. In addition, upon receiving a click on the error correction button 63, a screen display process corresponding to the correction item of the error correction support unit 24 is performed.
[0056]
FIG. 8 is a diagram illustrating an example of a usage table according to the present embodiment. FIG. 8A is a table of the job control middleware error information 14.
This is information held by the job control middleware, and is created by the job control middleware. It holds the association between the job name 68 and the source file name 69, and information on the start time 70, end time 71, and end status 72 of the job.
[0057]
FIG. 8B is a table of the source file tree structure 26.
This is a table created in the source file tree structure analysis unit 18 and step 42. The table shows the parent file 73 and the child file 75 for representing the tree structure of the source file, and whether the file uses the specified middleware. It stores information on the parent file specific middleware use 74 and the child file specific middleware use 76 to be represented.
[0058]
If the file in the parent file 73 column uses the specified middleware, “Y” is recorded in the parent file specifying middleware use column 74, and if not, “N” is recorded. If the file in the child file 75 column uses the specified middleware, "Y" is recorded in the child file specifying middleware use column 76, and if not, "N" is recorded.
[0059]
FIG. 8C is a table of the middleware log directory configuration 27.
This represents the correspondence between the middleware name 77 and its log storage directory 78, and this table is prepared in advance.
[0060]
FIG. 8D is a table of the middleware log format 28.
This is used for registering the middleware log information in advance, extracting the middleware error in step 36, and editing the log file for display in step 40. This table includes a middleware name 79, a first item 80 of a log, a first item edit format 81, and the like, and this table is prepared in advance.
[0061]
FIG. 8E is a table of the middleware command list 8. This associates the middleware with the execution command, and is composed of a middleware name 84 and a command name 85. This table is prepared in advance.
[0062]
FIG. 9 is a diagram illustrating a continuation of the use table according to the present embodiment. FIG. 9F is a table of the log-environment parameter related information 29.
This is to associate a middleware error No. with an environmental parameter related to the middleware error No. The middleware error No. 86 includes an environment parameter 87. This table is prepared in advance.
[0063]
FIG. 9G is a table of the environment parameter directory structure 30.
This represents the correspondence between the middleware name 88 and its environment parameter storage directory 89, and this table is prepared in advance.
[0064]
FIG. 9H shows the log information display table 33 of the specific job, which is obtained by converting the log information of the middleware into an easy-to-view format, such as a belonging job name 90, an error occurrence time 91, error information 92, an environmental parameter 93, and the like. Consists of
[0065]
With the system described so far, the error log information of the middleware when an error occurs in a job and the source file of the job can be easily displayed.
[0066]
However, if an error occurs in another job that is being executed in the same time zone as the execution time of the job in which the error occurred, and it is not possible to specify which job the middleware error log information corresponds to There is.
[0067]
FIG. 10 is a diagram illustrating a specific example of error log information when an error occurs in the same time zone when a plurality of processes are executed according to the present embodiment. In FIG. 10, when another job is executed in the same time period as the execution time of the job in which the error has occurred, the case where the error log information can be identified by the timing of the error occurrence and the case where the error log information cannot be determined Is represented.
[0068]
FIG. 10 is described separately for the time zone of a, the time zone of b, and the time zone of c.
In the time zone a, since JOB_E has been completed normally, only JOB_C issues an error. Therefore, since the error log information generated during the time period a can be determined to be due to the error issued by JOB_C, it can be seen that the error log information corresponding to JOB_C has been determined.
[0069]
In the time zone c, JOB_D has been completed normally, so that only JOB_F issues an error. Therefore, since the error log information generated in the time period of c can be determined to be due to the error issued by JOB_F, it can be seen that the error log information corresponding to JOB_F is also determined.
[0070]
In the time period b, both JOB_C and JOB_F have issued an error. Therefore, the error log information generated in the time period b is due to the error issued by JOB_C or JOB_F, and the error log information is JOB_C or JOB_C. It turns out that it corresponds to any of JOB_F.
[0071]
As described above, when an error occurs in both jobs in a job executed in the same time zone, it is necessary to add a process for indicating whether or not the corresponding error log information is determined.
[0072]
FIG. 11 is a flowchart illustrating a processing procedure when an error occurs in the same time zone during multiple executions of this embodiment. First, at step 37, an error occurrence time and an error occurrence middleware name 55 are displayed in the selected job error candidate middleware list 52. At this time, if a plurality of pieces of error log information are extracted, a plurality of error occurrence times and error occurrence middleware names 55 are displayed. Then, after the processing, the processing of the processing flow of FIG. 11 is executed.
[0073]
Further, corresponding log information for indicating which job the log information in the log information display table 33 of the specific job corresponds to is added to the log information display table 33 of the specific job, and the log information is added. Used for display. Although two jobs are executed in FIG. 10, the same processing can be performed even when three or more jobs are executed.
[0074]
In the processing flow of FIG. 11, first, in step 95, it is checked whether an error has occurred in another job within the execution time of the selected job. That is, referring to the table in FIG. 8A, after searching for another job having an execution time zone overlapping with the execution time zone of the selected job, checking the end status of the job, Read out.
[0075]
In step 96, referring to the result of the investigation in step 95, it is determined whether or not an error has occurred in another job during the execution time period of the selected job. If not, the corresponding log information is set to "confirmed" in step 97, and the corresponding log information is stored in the log information display table 33 of the specific job in step 98.
[0076]
If an error has occurred in another job during the execution time period of the selected job, the process proceeds to step 99, where the error occurrence time and the error occurrence middleware name 55 displayed in the selected job error candidate middleware list 52 are displayed. Accept the selection.
[0077]
In step 100, the error-occurring middleware received by the selection is compared with middleware used in a file in the source file tree structure of the other job, and the error-occurring middleware accepted by the selection is selected by the selected job. It is determined whether it is being used by another error job in the same time zone.
[0078]
If the error occurrence middleware accepted by the selection is not used in another error job, the correspondence between the selected job and the error log information is established. In step 98, the corresponding log information is stored in the log information display table 33 of the specific job.
[0079]
When the error-occurring middleware received by the selection is used in another error job, as information indicating that the error log information corresponds to either the selected job or the other error job, "Undetermined" is set as the corresponding log information (step 101), and the corresponding log information is stored in the log information display table 33 of the specific job in step 98.
[0080]
The error log / source file display unit 23 performs processing for distinguishing from the case of “determined” by changing the display attribute, such as changing the color when the corresponding log determination information is “undetermined”. Thereby, the user can distinguish whether the corresponding log determination information is “determined” or “undetermined” on the screen.
[0081]
Here, the corresponding log information is set to “determined” or “undetermined”. However, the degree of error information determination may be calculated and this value may be used as the corresponding log information. For example, history information that associates an error command in a job with its error log information is accumulated, and as in step 101, certain error log information corresponds to any of a plurality of jobs. When the status becomes the error log information, the probability that the command which caused the error in each job corresponds to the error log information is obtained from the history information as the degree of error information determination, and the value is used as the corresponding log information.
[0082]
As described above, in the present embodiment, when an error occurs in a certain job using the middleware, the middleware that has issued the error can be specified from among the plurality of executed middlewares, and the corresponding error log information can be specified. Can be displayed, so that the cause of the error can be efficiently identified. Also, even if an error occurs in another job within the execution time of the job in which the error occurred, candidates for error log information that may correspond can be listed. Can reduce man-hours at the time of testing.
[0083]
As described above, according to the error log information analysis support device of the present embodiment, error log information of the second program used by the first program in which an error has occurred is collected within the execution time of the first program. In the case where a plurality of second programs used by the first program in which an error has occurred are executed and a plurality of pieces of log information of the second program exist, the log information necessary for error correction is efficiently displayed. And error correction can be quickly performed.
[0084]
【The invention's effect】
According to the present invention, error log information of a second program used by a first program in which an error has occurred is collected and displayed during the execution time of the first program, and use of the first program in which an error has occurred is used. Even if a plurality of second programs are executed and a plurality of pieces of log information of the second program exist, it is possible to efficiently collect log information necessary for error correction and quickly perform error correction support. It is possible.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a schematic configuration of an error log information and source file display system according to an embodiment.
FIG. 2 is a diagram showing details of the error log investigation processing unit 7 shown in FIG. 1 of the present embodiment and an example of information used by the error log investigation processing unit 7;
FIG. 3 is a flowchart illustrating a processing procedure of a middleware specifying unit 20 of the embodiment.
FIG. 4 is a flowchart illustrating a processing procedure of a log information display table creation unit 21 according to the present embodiment.
FIG. 5 is a flowchart illustrating a processing procedure of a tree structure creation unit 22 of the embodiment.
FIG. 6 is a flowchart illustrating a processing procedure of an error correction support unit 24 according to the present embodiment.
FIG. 7 is a diagram illustrating operations from display of an error job to display of an error log and a source file, and a display screen according to the embodiment.
FIG. 8 is a diagram illustrating an example of a use table according to the present embodiment.
FIG. 9 is a diagram illustrating a continuation of the use table according to the embodiment;
FIG. 10 is a diagram illustrating a specific example of error log information when an error occurs in the same time zone when a plurality of processes are executed according to the embodiment;
FIG. 11 is a flowchart illustrating a processing procedure when an error occurs in the same time zone during multiple executions of the embodiment.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Client, 2 ... Client holding information, 3 ... Server, 4 ... Server holding information, 5 ... Network, 6 ... Job control middleware client, 7 ... Error log investigation processing unit, 8 ... Middleware command list, 9 ... Middleware log management Information, 10 ... Environment parameter related information, 11 ... DBMS middleware, 12 ... OLAP middleware, 13 ... Middleware log, 14 ... Job control middleware error information, 15 ... Source file group, 16 ... Job net information, 25 ... Error job information, 26 ... source file tree structure, 27 ... middleware log directory structure, 28 ... log format, 29 ... log-environment parameter related information, 30 ... environment parameter directory structure, 31 ... inter-job related information, 32 ... job-source related information, 3 ... Table for displaying log information of specific job, 17 ... Display of job execution confirmation screen / error job selection unit, 18 ... Source file tree structure analysis unit, 19 ... Middleware investigation unit using error job, 20 ... Middleware specification unit, 21 ... Table creation unit for log information display, 22: tree structure creation unit, 23: error log / source file display unit, 24: error correction support unit, 50: job execution confirmation screen, 51: job display, 52: selected job error candidate Middleware list, 53: Selected job name, 54: Error occurrence middleware list, 55: Error occurrence time and error occurrence middleware name, 56: Log display button, 57: File display button, 58: DBMS log screen, 59: Selected job name , 60: selected middle name, 61: log information, 62: environmental parameter information 63: error correction button, 64: error source file display screen, 65: selected job name, 66: file tree structure, 67: selected file source code, 68: job name, 69: source file name, 70: start time, 71: End time, 72: End status, 73: Parent file, 74: Use of parent file specific middleware, 75: Child file, 76: Use of child file specific middleware, 77: Middleware name, 78: Log storage directory, 79: Middleware Name, 80: first item, 81: first item edit format, 82: nth item, 83: nth item edit format, 84: middleware name, 85: command name, 86: middleware error No., 87: environmental parameter , 88: Middleware name, 89: Environment parameter storage directory, 90: Affiliation job Item name, 91: error occurrence time, 92: error information, 93: environmental parameters.

Claims (6)

In an error log information analysis support method for supporting analysis of error log information,
Identifying a second program used by the first program in which the error has occurred, in which the first program has an error; and specifying the first program in the log information of the identified second program. Reading data generated during the execution time to create log information display data; and displaying the created log information display data to assist in correcting the error that has occurred. Error log information analysis support method. 2. The error log information according to claim 1, wherein a file using the specified second program is displayed in a file configuring the first program to assist correction of an error. 3. Analysis support method. Setting, in a tree structure indicating files constituting the first program, usage information indicating a file using the specified second program, and setting a file using the specified second program; The error log information analysis support method according to claim 1, wherein the error information is displayed in a tree structure according to the usage information. When an error has occurred in another program within the execution time of the first program, the log information in the created log information display data corresponds to either the first program or another program. The error log information analysis support method according to any one of claims 1 to 3, wherein the error log information analysis supporting method is displayed. In an error log information analysis support device that supports analysis of error log information,
A program specifying unit that specifies an error in the second program used by the first program in which the error has occurred; and the first information in the log information of the specified second program. A log information display data generation unit that reads data generated within the execution time of the program to generate log information display data, and displays the generated log information display data to assist in correcting the error that has occurred. An error log information analysis support device, comprising: In a program for causing a computer to function as an error log information analysis support device that supports analysis of error log information,
A program specifying unit that specifies an error in the second program used by the first program in which the error has occurred; and the first information in the log information of the specified second program. A log information display data generation unit that reads data generated within the execution time of the program to generate log information display data, and displays the generated log information display data to assist in correcting the error that has occurred. A program that causes a computer to function as an error correction support unit that performs the operation.

Images