JP2009163566A - Job analysis support apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for effectively analyzing the present conditions of business systems. <P>SOLUTION: A job analysis support apparatus refers to job relevant information for indicating dependence of a plurality of jobs, and arranges the plurality of jobs in one line on the basis of the dependence. The job analysis support apparatus sets a set of a job and job attribute information indicating the attribute of the job, and lists and displays a list of the job set in a job list screen 280. When a user selects either job set in the job list screen 280, a data set corresponding to the selected job set is listed and displayed. When the data set is selected, an element set corresponding to the selected data set is listed and displayed. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a business system, and more particularly to a technique for analyzing the current state of a business system.

  Business systems that support the operation of companies and public facilities, so-called enterprise systems, are now being introduced as the foundations of large and small organizations. The business system aggregates, accumulates, analyzes, and processes data obtained from node terminals and databases, and outputs information with higher added value. Business systems continue to evolve to make more complex organizational management more efficient.

A business system is often modeled as a collection of jobs. A job is a basic execution unit in the system, such as a database update process and a calculation process for data obtained from each node terminal. Depending on the business system, the number of jobs can range from thousands to tens of thousands. Furthermore, the number of program files constituting a job is several hundred thousand, sometimes several million. Since the business system continues to operate for many years, various maintenance operations such as addition, correction, and abolition of jobs, program files, and data items are required even after operation.
JP 2002-358224 A JP 2006-268507 A JP 2007-265029 A

  For long-term operation of business systems, the overall picture of the business system must always be clear. Usually, the meanings of jobs, program files, data items, etc. are documented as design documents. However, the description of the design document is not always clear, and the programmer does not always write the design document correctly and without error. In addition, the design document itself may be lost. In this way, the reliability of design documents greatly depends on the programmer's “mind”. Once the business system and the design document deviate, the business system can become a black box.

  The present invention has been completed based on the above-mentioned problems, and its main object is to provide a technique for efficiently analyzing the current state of a business system.

One embodiment of the present invention relates to a job analysis support apparatus.
This apparatus refers to job relationship information indicating dependency relationships of a plurality of jobs, generates a plurality of provisional lists corresponding to each of the plurality of head jobs, and registers the head job in the corresponding provisional list. Next, all of the preceding jobs are registered in one of the temporary lists, and themselves detect a job that is not registered in the temporary list as a candidate job, and the candidate job is added to the temporary list in which the preceding job is registered. The additional registration processing for additional registration is repeated until all of a plurality of jobs are registered in any provisional list. When the job registered in the first provisional list corresponds to the preceding job of the job registered in the second provisional list, the job registered in the second provisional list is transferred to the first provisional list. Thus, the second provisional list is combined with the first provisional list. A job list in which a plurality of provisional lists are combined is displayed on a screen as a list in which a plurality of jobs are arranged in a line based on the dependency.

  It should be noted that any combination of the above-described components, and the present invention expressed by a method, system, recording medium, and computer program are also effective as an aspect of the present invention.

  According to the present invention, it becomes easy to efficiently analyze the current state of a business system.

FIG. 1 is a hardware configuration diagram of the business system 220.
The business system 220 is introduced to manage the business of an organization such as a company or a public facility. The business system 220 may be configured as a system that integrates a plurality of geographically dispersed organizations.

The business system 220 in this embodiment includes a job management device 230, a job execution device group 200, and an external storage device 210. The job management device 230, the job execution device group 200, and the external storage device 210 are connected to each other via a communication network.
The job management device 230 causes the job execution device group 200 to execute a plurality of jobs based on the execution conditions of each job. The job execution device group 200 includes a plurality of job execution devices 202. Each job execution device 202 executes the job assigned from the job management device 230. The job management device 230 may assign a job to any one of the job execution devices 202 in accordance with a predetermined assignment rule. Alternatively, jobs may be preferentially assigned to the job execution devices 202 that have a lighter processing load than the other job execution devices 202 so that the processing load of each job execution device 202 is distributed.
The program constituting the job may be held in advance by the job execution apparatus 202. Alternatively, a program may be downloaded from the job management apparatus 230 to the job execution apparatus 202 when a job execution instruction is given. The job execution device 202 notifies the job management device 230 of the job execution state.

  The external storage device 210 stores various data for business. The job execution device 202 sends and receives data to and from the external storage device 210 when executing a job. Further, the job execution device 202 executes a job based on data acquired from the external storage device 210 or data acquired from another database (not shown), a node terminal, or the like.

  In summary, the job execution device 202 executes various jobs using the data in the external storage device 210 as a variable. The job management device 230 controls job execution timing based on the execution conditions of each job. As described above, based on the data obtained from the external storage device 210, a plurality of jobs are executed according to the schedule, so that the entire business system 220 is operated.

The job executes “write” and “read” with respect to various files during execution. Hereinafter, a file to be accessed from a job is referred to as a “data file”. Many of the data files are normally held in the external storage device 210. The business system 220 is designed for long-term and sometimes operation for several decades. In addition, jobs, programs, data files, and the like constituting the business system 220 are appropriately modified in response to changes in organizational work.
The job analysis support apparatus 100 is an apparatus for analyzing a job, a program constituting each job, a data file accessed from each program, and the like, and presenting the current state of the business system 220 in a user-friendly format.

FIG. 2 is a configuration diagram of the business system 220.
The configuration of the business system 220 is
A. Job relationship: relationship between jobs. Job structure: relationship between job and program, program and data file Data structure: Hierarchy can be divided into three levels: the relationship between data files and data elements.

A. Job Relationship: Job-Job Relationship The business system 220 includes one or more frames, and the frame includes one or more nets (NET). The net includes one or more jobs. Thus, the processing unit of the business system 220 is subdivided in the order of frame, net, and job. A net is a concept in which jobs related to a predetermined process are grouped, and a frame is a concept in which nets related to a predetermined process are grouped. Jobs are identified by their frame and net.

  There is a dependency relationship between a plurality of jobs, that is, execution of a job in the subsequent stage is started after execution of the job in the previous stage is completed. For example, assume that job 2 and job 3 are executed based on the execution result of job 1. In this case, since job 2 and job 3 cannot be executed unless execution of job 1 is completed, job 2 and job 3 depend on job 1. On the other hand, no dependency relationship is established between job 2 and job 3. The affiliation and dependency of each job are registered as “job relation information 240”. The job management apparatus 230 refers to the job relation information 240 and controls the execution schedule of each job. The job-related information 240 is information for the job management device 230 and is not information that considers readability for humans.

  Therefore, the programmer updates the job-related document 242 as appropriate when a job is added or deleted, a dependency is changed, or the like. The job relation document 242 is a design document for explaining the job relation in an easy-to-understand manner for humans.

B: Job structure: relationship between job and program, program and data file A job is an aggregate of one or more programs. The program accesses various data files. For example, when one program p1 writes data A to the data file d1, another program p2 executes its own processing based on the data A of the data file d1. Thus, each program cooperates via a data file. As a result, each job is linked via a data file.

  The relationship between jobs and programs, and programs and data files is registered as “first job structure information 244”. The first job structure information 244 of this embodiment is described in a job control language (JCL). The first job structure information 244 indicates a relationship between one job, one or more programs constituting the job, and a data file to be accessed by each program. It can be seen that the job shown in FIG. Of these, it can be seen that the program 3 has access to four data files (D files) b, c, e, and f. The first job structure information 244 will be described later with reference to FIG.

  Since the first job structure information 244 in this embodiment is described in JCL, it is possible for a human to read down the first job structure information 244. However, JCL is merely a programming language, and is not an optimal format for allowing humans to understand the relationship between jobs, programs, and data files.

  Therefore, the programmer updates the job structure design document 248 as appropriate when a job, a program, or a data file is added or deleted, or the correspondence is changed. The job structure design document 248 is a design document for explaining the job structure in an easy-to-understand manner for humans.

  Further, the relationship between the program and the data file, and the data file and the layout file are registered as “second job structure information 246”. A layout file is a file that declares a data type and a data name for one or more data elements included in a data file. The second job structure information 246 of this embodiment is described in COBOL (COmmon Business Oriented Language). It can be seen that the program 3 shown in FIG. 4 has access to four data files, data files b, c, e, and f. Among these, it can be seen that the data type and data name of each data element included in the data file b are declared in the layout file b.

  Since the second job structure information 246 in this embodiment is described in COBOL, it is possible for a human to read down the second job structure information 246. However, COBOL is also a programming language and is not an optimal format for allowing humans to understand the relationship between programs, data files, and layout files.

  Therefore, the programmer updates the job structure design document 248 as appropriate when a program, data file, layout file is added or deleted, or the correspondence is changed.

C: Data structure: relationship between data file and data element The data declaration information 250 is a layout file for declaring the data type and data name of one or more data elements included in the data file. The data declaration information 250 shown in the figure declares data types and data names of four data elements 1 to 4. The data declaration information 250 in this embodiment is also described by COBOL. The data declaration information 250 will be described later with reference to FIG.

  Since it is described in COBOL, it is possible for a human to read down the data declaration information 250. Normally, the programmer updates the data definition document file 252 as appropriate when changing the data type or data name of the data element included in the data file. The data definition document file 252 is a design document for explaining various data elements used in the business system 220.

  As described above, the business system 220 has the A.D. Job-related, B. Job structure, C.I. It is hierarchized in three stages of the data structure. The current state of the business system 220 is indicated by job-related information 240, first job structure information 244, second job structure information 246, and data declaration information 250 (hereinafter referred to as “current state information”). However, it is difficult to grasp the entire contents of the huge business system 220 from these current status information that does not necessarily take human readability into consideration. Therefore, design documents (hereinafter referred to as “document information”) such as a job-related document 242, a job structure design document 248, and a data definition document file 252 are prepared corresponding to each layer.

However, as a result of the long-term operation of the business system 220, the current status information and the document information are gradually separated. Once the document information deviates from the current status information, the current status of the business system 220 cannot be accurately grasped unless the current status information is accessed. That is,
Document information: easy to understand for humans, but easy to deviate from the current situation.
Current status information: It is difficult for humans to understand, but it shows the current status correctly.
It can be said.
The job analysis support apparatus 100 analyzes the correct current status of the business system 220 based on the current status information, and the A. Job-related, B. Job structure, C.I. This is a device for showing the data structure to the user in an easily understandable manner. In the following, the process until the job analysis support apparatus 100 analyzes the current status information and presents the current status information in a user-friendly format is referred to as “current status analysis processing”.

FIG. 3 is a diagram showing an outline of the process of the current state analysis process.
In the current state analysis process, four processes S10, S12, S14, and S16 are sequentially executed.
1. Job serialization (S10)
With reference to the job relation information 240, a plurality of jobs are arranged in a line in the arrangement order reflecting the job dependency. The jobs arranged in a line are displayed on the screen as a “job list”. Job serialization is related to Fig. 5, Fig. 6, Fig. 7 (a), Fig. 7 (b), Fig. 8 (a), Fig. 8 (b), Fig. 9 (a), and Fig. 9 (b). And will be described in detail.
2. Correction of job list (S12)
By referring to the job relation information 240 and the like, a “job set” is created in which job attribute information indicating the attribute of each job is associated with the job. Modify the job list so that the job set becomes a list element. The job list correction will be described in detail with reference to FIGS.
3. Create data set list (S14)
By referring to the first job structure information 244 and job set described in JCL, a “data set” in which the data file, program, job, and job attribute information are associated is created. A “data set list” in which the data set is a list element is displayed on the screen. The creation of the data set will be described in detail with reference to FIGS.
4). Creation of element set list (S16)
With reference to the data declaration information 250 described in COBOL, the data definition document file 252 and the like, an “element set” in which the meaning of the data, the data name, and the data type are associated with each data element is created. An “element set list” having the element set as a list element is displayed on the screen. The creation of the element set will be described in detail with reference to FIGS.

FIG. 4 is a functional block diagram of the job analysis support apparatus 100.
Each block shown here can be realized in hardware by an element such as a CPU of a computer or a mechanical device, and in software it is realized by a computer program or the like. Draw functional blocks. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software.
Here, functions to be exhibited by each functional block will be mainly described, and specific actions will be described with reference to FIG.

The job analysis support apparatus 100 includes a user interface processing unit 110, a data processing unit 140, and a data holding unit 160.
The user interface processing unit 110 is in charge of processing related to the entire user interface such as input processing from the user and information display for the user.
The data processing unit 140 executes various data processing based on the data acquired from the user interface processing unit 110. The data processing unit 140 also serves as an interface between the user interface processing unit 110 and the data holding unit 160.
The data holding unit 160 stores various setting data prepared in advance and data received from the data processing unit 140.

User interface processing unit 110:
The user interface processing unit 110 includes an input unit 112 and a display unit 114.
The input unit 112 receives an input operation from the user. The input unit 112 includes a job relation information acquisition unit 116, a job content information acquisition unit 118, a job structure information acquisition unit 120, a data declaration information acquisition unit 122, and a data definition document acquisition unit 124. The job relationship information acquisition unit 116 acquires job relationship information 240. The job content information acquisition unit 118 acquires “job content information 258” as part of the document information. The job content information 258 is information in which a job is associated with job attribute information indicating job attributes. The job content information 258 will be described later with reference to FIG. The job structure information acquisition unit 120 acquires first job structure information 244 and second job structure information 246. The data declaration information acquisition unit 122 acquires data declaration information 250. The data definition document acquisition unit 124 acquires the data definition document file 252. In addition to this, the input unit 112 also acquires various types of information such as the job-related document 242 and the job structure design document 248.

The display unit 114 displays various information to the user.
The display unit 114 includes a job list display unit 126, a data set list display unit 128, and an element set list display unit 130. The job list display unit 126 displays the job list on the job list screen 280 shown in FIG. The data set list display unit 128 displays the data set list on the data set list screen 330 shown in FIG. The element set list display unit 130 displays the element set list on the element set list screen 350 shown in FIG.

Data processing unit 140:
The data processing unit 140 includes a job list generation unit 142, a data set generation unit 144, and an element set generation unit 146. The job list generation unit 142 executes “job serialization (S10)” and “job list correction (S12)” in the current state analysis process shown in FIG. The data set generation unit 144 executes “data set list creation (S14)”, and the element set generation unit 146 executes “element set list creation (S16)”.

  The job list generation unit 142 includes a provisional list generation unit 148, a provisional list addition unit 150, a provisional list combination unit 152, and a job list update unit 154. The temporary list generating unit 148, the temporary list adding unit 150, and the temporary list combining unit 152 execute “job serialization (S10)”. The provisional list generation unit 148 generates a “provisional list” that is the basis of the job list from the dependency relationship of each job, and the provisional list addition unit 150 adds each job to any provisional list. . Then, the provisional list combining unit 152 combines a plurality of provisional lists to create a job list. The job list updating unit 154 executes “job list correction (S12)”.

Data holding unit 160:
The data holding unit 160 includes a job related information holding unit 162 that holds job related information 240, a job content information holding unit 164 that holds job content information, a job that holds first job structure information 244 and second job structure information 246. A structure information holding unit 168, a data declaration information holding unit 170 that holds data declaration information 250, and a data definition document holding unit 172 that holds a data definition document file 252 are included. The data holding unit 160 also holds various current status information and document information.

In the following, the four processing contents S10, S12, S14, and S16 of the current state analysis processing shown in FIG. 3 and the user interface related to each processing will be sequentially described.
[1. Job serialization]

FIG. 5 is a schematic diagram showing job dependency.
As described above, the job dependency is set in the job relationship information 240. FIG. 5 visually shows dependency relationships of seven jobs A to G. Hereinafter, job 2 having “execution completion of job 1” as an execution start condition is referred to as “following job” of job 1. Job 1 is also referred to as “preceding job” of job 2. In the case shown in the figure, job B and job D are subsequent jobs of job A. Job A is a preceding job for job B and job D. Job C is a job that follows job B directly, and a job that follows job A indirectly. Hereinafter, a direct preceding job for a certain job, such as job B for job C, is referred to as “narrowly preceding job”. When an indirect preceding job for a certain job is included like job A for job C, it is referred to as a “preceding job in a broad sense”. In the present specification, unless otherwise specified, the term “preceding job” simply means “preceding job in a narrow sense”.

  The job management apparatus 230 causes the job execution apparatus 202 to execute executable jobs one after another while determining whether each job can be executed according to the job dependency and the job execution status. According to the figure, job A and job G have no preceding job. Therefore, execution of job A and job G can be started at any time. Hereinafter, such a job having no preceding job is referred to as a “first job”.

FIG. 6 is a data structure diagram of the job relation information 240 for setting the job dependency shown in FIG.
The job relationship information 240 includes not only job dependency relationships but also information related to job affiliation and the like. Here, only job dependency relationships will be described. The target job column 254 shows seven jobs A to G shown in FIG. The preceding job column 256 indicates the preceding job of each job shown in the target job column 254. According to the figure, there is no preceding job of job A, but the preceding job of job B is job A. Further, there are three preceding jobs of job F: jobs C, E, and G. In the job relationship information 240, dependency relationships between jobs are defined in this format.

For humans, the schematic diagram of FIG. 5 is easier to grasp the job dependency than the data structure format of FIG. For this reason, the job relationship document 242 often illustrates the dependency relationship of each job in the format shown in FIG. However, when the job dependency is illustrated in a format as shown in FIG. 5, if the job dependency is frequently changed, the diagram itself is likely to be messy.
Therefore, the “1. job serialization” processing in the present embodiment aims to arrange the jobs A to F in a line in the arrangement order reflecting the job dependency.

FIG. 7A is a schematic diagram showing a provisional list generation process in job serialization.
The hatched portion in the figure indicates an area where no preceding job is set. First, the provisional list generation unit 148 detects the head job with reference to the job relation information 240. The first job is a job for which no preceding job is set, and job A and job G correspond to the first job. The temporary list generation unit 148 generates a temporary list A and a temporary list B. More specifically, the provisional list generation unit 148 secures two areas on the heap memory and associates them with the provisional list A and provisional list B, respectively. The provisional list generation unit 148 registers job A in the provisional list A and job B in the provisional list B (S1, S2). More specifically, the provisional list generation unit 148 records the ID of job A in the area corresponding to the provisional list A on the heap memory, and records the ID of job B in the area corresponding to the provisional list B.

FIG. 7B is a schematic diagram illustrating a first process in the additional registration process in the serialization of jobs.
The hatched portion in the figure indicates an area where no preceding job is set and an area corresponding to a preceding job already registered in the provisional list. The provisional list adding unit 150 refers to the job-related information 240 and the registered contents of each provisional list, and all the preceding jobs are registered in any provisional list and are registered in any provisional list. Detect missing jobs as candidate jobs. In the figure, job B and job D correspond. The provisional list adding unit 150 registers such candidate jobs in the same provisional list as the preceding job. In the case of FIG. 5, the provisional list adding unit 150 registers the candidate job D in the same provisional list A as the preceding job A (S3). At this time, job D is registered immediately after job A. In the temporary list A, jobs A and D are arranged. Next, the provisional list adding unit 150 registers the candidate job B in the same provisional list A as the preceding job A (S4). At this time, job B is registered immediately after job A. As a result, jobs A, B, and D are arranged in the temporary list A.
When there are a plurality of preceding jobs, an arbitrary preceding job may be selected and a candidate job may be registered immediately after the selected preceding job. Here, job D is registered in provisional list A and then job B is registered in provisional list A, but the registration order may be reversed.
The process of registering a candidate job after specifying a candidate job is called “additional registration process”. The additional registration process is repeated until there are no candidate jobs.

FIG. 8A is a schematic diagram showing a second process in the additional registration process in the serialization of jobs.
The provisional list adding unit 150 detects the next candidate job. In the figure, job C and job E are detected. The provisional list adding unit 150 registers the candidate job E in the same provisional list A as the preceding job D (S5). At this time, the candidate job E is registered immediately after the preceding job D. Next, the temporary list adding unit 150 registers the candidate job C in the same temporary list A as that of the preceding job B (S6). At this time, candidate job C is registered immediately after preceding job B.
As a result, jobs A, B, C, D, and E are registered in the provisional list A in this order.

FIG. 8B is a schematic diagram showing a third process in the additional registration process in the serialization of jobs.
The provisional list adding unit 150 detects the next candidate job. In the figure, job F is detected as the last candidate job. The temporary list adding unit 150 registers the candidate job F in the same temporary list B as that of the preceding job G (S7). At this time, the candidate job F is registered immediately after the preceding job G. Since job C and job E as well as job G are the preceding jobs of job F, job F may be registered in provisional list A.
Since there are no candidate jobs, the additional registration process ends.

FIG. 9A is a schematic diagram illustrating a provisional list combining process in job serialization.
The provisional list combining unit 152 combines the provisional list q after the provisional list p when the job 1 of the provisional list p is a preceding job of the job 2 in another provisional list q. In the case of the figure, the job C and job E in the provisional list A are the preceding jobs of the job F in another provisional list B. The provisional list combining unit 152 refers to the job relation information 240 and each provisional list, and detects a job having a preceding job in another provisional list such as the job F. In the case of the figure, the provisional list combining unit 152 combines the provisional list B after the provisional list A.

FIG. 9B is a schematic diagram illustrating a job list when job serialization is completed.
The temporary list combining unit 152 combines a plurality of temporary lists into one to generate a “job list”. In the figure, jobs are arranged in a line in the order of A, B, C, D, E, G, and F. Referring to FIG. 5 again, it can be seen that there are three flows: a job A, B, and C, a flow D and E, and a flow G and F. Therefore, according to the algorithm described with reference to FIGS. 7A to 9B, a plurality of jobs can be arranged in a line in the arrangement order reflecting the dependency.

As another example, assume that candidate job D is registered in provisional list A after candidate job B is registered in provisional list A in FIG. In this case, the registration contents of the provisional lists A and B are as follows:
Provisional list A: A, D, B
Provisional list B: G
It becomes.

Next, in FIG. 8A, it is assumed that the candidate job E and the candidate job C are registered in the temporary list A in this order. In this case, the registration contents of the provisional lists A and B are as follows:
Provisional list A: A, D, E, B, C
Provisional list B: G
It becomes.

Next, in FIG. 8B, it is assumed that the preceding job of candidate job F is job E and candidate job F is registered in provisional list A. In this case, the registration contents of the provisional lists A and B are as follows:
Provisional list A: A, D, E, F, B, C
Provisional list B: G
It becomes.

Here, since job G is a preceding job of job F, when provisional list A is combined with provisional list B, jobs are arranged in the order of G, A, D, E, F, B, and C as the job list. become. Referring to FIG. 5, it can be seen that there are three flows: a job G, a flow A, D, E, and F, and a flow B and C. Therefore, even in the above-described another example according to the algorithm described with reference to FIGS. 7A to 9B, a plurality of jobs can be arranged in a line in the arrangement order reflecting the dependency.
Here, in order to simplify the explanation, seven jobs A to G have been described as an example. However, even when the number of jobs is larger, even if the dependency relationship is more complicated, the number of temporary jobs is provisional. The above algorithm that sets a large flow by creating a list and connects each candidate job immediately after a narrowly preceding job works effectively.
[2. Job list modification]

FIG. 10 is a schematic diagram illustrating a job set generation process.
Next, the job list update unit 154 generates a job set in which the job and the job attribute information are associated with each job. A part of job attribute information is defined by job relation information 240. A frame column 260 indicates a frame. The net ID column 262 shows the net ID. The net name column 264 shows the name of the net. A job ID column 266 shows a job ID. In addition to this, the job relation information 240 also defines a preceding job for each job as shown in FIG. Here, job attribute information other than job dependency will be described.

The job content information 258 is a part of the document information and is a design document that defines the processing content of each job. The job content information 258 may be provided as part of the job related document 242 or the job structure design document 248. The job ID column 268 shows the job ID. The job name column 270 indicates the name of the job. The job content column 272 shows job processing content. The job list update unit 154 generates a job set 274 for each job, using the job IDs registered in the job ID field 266 of the job relation information 240 and the job ID field 268 of the job content information 258 as keys. The job set 274 shown in the figure includes various job attribute information such as a frame, a net ID, a net name, a job ID, a job name, and job processing contents for a job with job ID = B. In addition to these, various types of information such as preceding jobs may be included.
With such a processing method, a job set in which a job is associated with various job attribute information is generated for each job.

FIG. 11 is a screen diagram of the job list screen 280.
The job list update unit 154 adds job attribute information to each job, and from the “job list with jobs as list elements” generated by the “1. job serialization” process, “jobs with job sets as list elements” List ". In other words, a job list in which job sets are arranged in the arrangement order determined by “1. Job serialization” is generated. The job list display unit 126 displays a job list having a job set as a list element on the job list screen 280.

  The job list screen 280 allows the user to browse the job attribute information of a huge number of jobs included in the business system 220 collectively. Since each job set is arranged in a form reflecting the job dependency, the user can easily understand the job dependency even in the list format.

  The name of the job in this embodiment is set according to a predetermined naming rule. The jobs are “1. Input detection”, “2. Reception of data from external storage device 210”, “3. Processing of received data”, “4. Recording of data to external storage device 210”. As described above, it is classified into several types according to the processing contents. Then, “ST” is set as the suffix (suffix) for the job name classified as “1. Input detection”. In the figure, job A and job G correspond.

The job list display unit 126 displays a job set relating to a job for which the suffix “ST” is set in a manner that can be visually distinguished from job sets relating to other jobs. For example, in the job list screen 280, the suffix “ST” is set, that is, a job set of a job related to “1. Input detection” is set to a character color, background color, font, It may be displayed in character size. Similarly, “S” is set as a suffix (suffix) for job names classified as “2. Receiving data from external storage device 210”. In the figure, job B and job D correspond. The job list display unit 126 displays a job set related to a job for which the suffix “S” is set in a form that can be visually distinguished from job sets related to other jobs. For example, in the job list screen 280, only the job set of the job for which the suffix “S” is set, that is, “2. Receiving data from the external storage device 210” may be displayed in blue.
According to such an aspect, the type and relationship of each job can be easily shown to the user.

  The processing content of the job shown in the job list is derived from the job content information 258 that is document information. By referring to the job list screen 280, the user can efficiently determine the portion of the job content information 258 that is not described. As a result, the job list makes the user recognize the necessity of updating the document information.

When the user selects any job set with an input device such as a mouse, a list of data sets related to the selected job is displayed on the screen. The screen display of the data set list will be described with reference to FIG.
[3. Create dataset list]

FIG. 12 is a schematic diagram showing a data set creation process.
Next, the data set generation unit 144 generates a data set in which jobs, programs, and data files are associated with each other. The data set generation unit 144 generates a data set 282 for each data file from the job list 284 generated earlier, the first job structure information 244 described in JCL, and the assignment information 298. In the job list 284, the frame column 286 is a frame, the net ID column 288 is a net ID, the net name column 290 is a net name, the job ID column 292 is a job ID, the job name column 294 is a job name, and a job content column. Reference numeral 296 denotes job processing contents.

  The assignment information 298 is a part of the current status information and associates a data file alias (hereinafter referred to as “assign”) with a layout file. The assignment column 300 shows the assignment. The declaration file column 302 indicates the name of the layout file that declares the data elements of the data file specified by the assignment, that is, the data declaration information 250. The assignment information 298 is extracted from the second job structure information 246 described in COBOL, but may be provided as part of the document information.

  The first job structure information 244 is already described by JCL, and defines the relationship between jobs, programs, and data files. The first job structure information 244 shown in FIG. In the program name area 304, names of programs constituting the job B are defined. An I / O area 306 indicates whether the program accesses a data file as an input source (I) or whether it accesses as an output destination (O). An assignment area 308 indicates the assignment of a data file to be accessed. A path area 310 indicates a path of a data file to be accessed.

  The data set generation unit 144 refers to the first job structure information 244 of job B and the job set of job B in the job list 284, and generates a data set for each data file appearing in the first job structure information 244. The data set 282 in FIG. 6 relates to the data file of the assignment “SYSHDD” to be accessed by the job B and the program “SEMP350”. In the data set 282, the assignment of the assignment area 308 is registered in the assignment field 314 as it is. In the data set name column 312, the data file name with a path shown in the path area 310 is registered. In the program column 318, the name “SEMP350” of the program indicated in the program name area 304 is registered. In the I / O column 316, “I (read)” that is the access type of the program “SEMP350” to the data file “SYSHDD” is registered. The job ID column 322 and the job name column 320 indicate the ID and name of the job to which the program “SEMP350” belongs. For these pieces of information, the job ID and name are acquired from the job list 284. The data set generation unit 144 extracts the corresponding information from the job list 284 and the first job structure information 244 using the job ID and name as a key, and generates a data set 282.

  Further, the data set generation unit 144 registers the layout file name indicated in the declaration file field 302 in the declaration file field 324 of the appropriate data set 282 using the assignment in the assignment field 314 as a key. In addition, information may be extracted from the document information as a part of the data set to explain the registered contents of the data file.

FIG. 13 is a screen diagram of the data set list screen 330.
When the user selects a job set for job B on the job list screen 280 in FIG. 11, a list of data sets related to job B is displayed as shown in FIG. The data set list display unit 128 detects a data set in which the job B is registered in the job ID column 322 and displays a data set list in which the corresponding data sets are arranged on the data set list screen 330.

  According to the figure, it can be seen that job B includes a program named “SEMP360”, and this program reads data from the data file designated by the assignment “SYS021”. However, “& dummy” is specified as the data set name of the data file “SYS021”. This indicates that the data file “SYS021” is already invalid. If “& dummy” is specified in all the data files to be accessed by the program “SEMP360”, the program “SEMP360” is an invalid program (hereinafter referred to as “dummy program”). In this case, the program “SEMP360” can be deleted from the disk such as the job management apparatus 230. If “& dummy” is specified for all the data files to be accessed by job B, job B is an invalid job (hereinafter referred to as “dummy job”). In this case, the job B itself can be deleted from the disk.

  With the data set list screen 330, dummy programs and dummy jobs can be efficiently detected based on the relationship with the data file. The data set generation unit 144 may automatically detect invalid data files, dummy programs, and dummy jobs using the above algorithm, and may automatically delete them if necessary.

When the user selects any data set with an input device such as a mouse, a list of element sets is displayed on the screen for the data elements related to the selected data set. The screen display of the element set list will be described with reference to FIG.
[4. Create Element Set List]

FIG. 14 is a schematic diagram illustrating a process of creating an element set.
Next, the element set generation unit 146 refers to the data declaration information 250 and the data definition document file 252 and generates an element set in which the name, meaning, and data type are associated with each data element.

  The data declaration information 250 is a layout file associated with the data file “SYSHDD” and is described in COBOL. The file name of the layout file including the data declaration information 250 is “CBL1”. The correspondence between the data file “SYSHDD” and the layout file “CBL1” is indicated by the second job structure information 246, particularly, assignment information 298 derived from the second job structure information 246. The data declaration information 250 is a file for declaring various data elements (variables and the like) included in the data file “SYSHDD”. The data name declaration area 332 indicates the name “HOJIN-CD” of the data element, and the data type declaration area 334 indicates the data type (X (2)) of the data element.

  The data definition document file 252 is a design document for explaining the meaning and data type of each data element declared in the layout file “CBL1”. The data meaning definition area 336 indicates the meaning of the data element, and the data type definition area 338 indicates the data type.

  The element set generation unit 146 receives data declaration information 250 (current information) for declaring each data element of the data file “SYSHDD” and data declaration information 250 (document information) for explaining each data element of the data file “SYSHDD”. Select and generate an element set 340 for each data element.

  The element set generation unit 146 temporarily generates an element set according to the declaration order of each data element in the data declaration information 250 and the definition order of each data element in the data definition document file 252. For example, assuming that the data element “HOJIN-CD” first declared in the data declaration information 250 and the data element “corporation” first defined in the data definition document file 252 are the same data element, the element set 340 is generated. However, the element set generation unit 146 confirms that the data type defined in the data type declaration area 334 and the data type defined in the data type definition area 338 match. Not 340.

  In general, the declaration order of data elements in the data declaration information 250 and the definition order of data elements in the data definition document file 252 often coincide. This is because, as a general tendency, data elements are often defined in the data definition document file 252 in the same order as the declaration order of the data elements of the data declaration information 250. Even after the element set generation unit 146 generates element sets, it is desirable that the user can check the contents of each element set and manually correct the contents of these element sets.

FIG. 15 is a screen diagram of the element set list screen 350.
When the user selects a data set of the data file “SYSHDD” on the data set list screen 330 in FIG. 13, an element set related to the data file “SYSHDD” is displayed in a list as shown in FIG. 15. The element set list display unit 130 detects an element set for the data file “SYSHDD” and displays an element set list in which the corresponding element sets are arranged on the element set list screen 350.

The job analysis support apparatus 100 has been described based on the embodiments.
In general, if the current status information and the document information are different from each other, the business system 220 is likely to become a black box. Conventionally, efforts have been made to prevent the business system 220 from becoming a black box in terms of both current information and document information due to stricter coding rules and design document formats. However, such measures largely depend on personal skills.

  While the job analysis support apparatus 100 is based on the current status information indicating the business system 220 as it is, the job analysis support apparatus 100 refers to the existing document information as necessary. Job-related, B. Job structure, C.I. Three aspects of the data structure are shown in list form in the form of a job list screen 280, a data set list screen 330, and an element set list screen 350. Because it is a list format, it is easy to become familiar with processing by existing spreadsheet software. Therefore, it becomes easier to show the entire contents of the business system 220 from these various lists in a visually comprehensible form.

  The job analysis support apparatus 100 arranges jobs having complicated dependency relationships in a line. [1. According to the algorithm described in relation to [Serialize Job], it is possible to arrange the jobs in the arrangement order reflecting the job dependency. Even in the list format, the user can easily read the job dependency to some extent.

  After that, a job set is generated from the job relation information 240 and the job content information 258. According to the job set list, various job attribute information such as job, affiliation, name, and processing content can be collectively displayed on the job list screen 280. By changing the display mode of the job set according to the type of job, the user can easily understand the type of each job intuitively.

When a job is selected on the job list screen 280, data file information related to the selected job is displayed in a list. According to the data file list, the user can collectively confirm the relationship between the job, the program, and the data file.
As of 2007, COBOL-based jobs that are more than 20 years old are still running in many business systems. On the other hand, there are many jobs that have already finished their roles as a result of maintenance work, so-called “dummy jobs”. Originally, dummy jobs should be removed from the disk. However, if the possibility that a job that looks like a dummy job is not actually a dummy job cannot be excluded, it may be left without being removed. An excessive increase in dummy jobs is not preferable because it leads to deterioration of so-called TCO (Total Cost of Ownership). According to the job analysis support apparatus 100, it becomes easy to efficiently detect a dummy program or a dummy job based on the data file list.

  Further, when a data file is selected on the data set list screen 330, information on data elements related to the selected data file is displayed in a list. According to the element set list, the user can collectively confirm the relationship between the data file and the data element.

  Thus, according to the job analysis support apparatus 100, the current status information of the business system 220 can be easily shown to the user. Further, since document information is also taken in and displayed as appropriate, it becomes easy to find a missing part or an old part in the document information from the relationship with the current information.

  The present invention has been described based on the embodiments. The embodiments are exemplifications, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are within the scope of the present invention. .

It is a hardware block diagram of a business system. It is a block diagram of a business system. It is a figure which shows the outline of the process of a present condition analysis process. It is a functional block diagram of a job analysis support device. It is a schematic diagram which shows the dependency relationship of a job. FIG. 6 is a data structure diagram of job relationship information for setting the job dependency shown in FIG. 5. (A) It is a schematic diagram which shows the provisional list production | generation process in the serialization of a job. (B) It is a schematic diagram which shows a 1st process among the additional registration processes in the serialization of a job. (A) It is a schematic diagram which shows a 2nd process among the additional registration processes in the serialization of a job. (B) It is a schematic diagram which shows the 3rd process among the additional registration processes in the serialization of a job. (A) It is a schematic diagram which shows the provisional list coupling | bonding process in the serialization of a job. FIG. 6B is a schematic diagram illustrating a job list when job serialization is completed. It is a schematic diagram which shows the production | generation process of a job set. It is a screen figure of a job list screen. It is a schematic diagram which shows the creation process of a data set. It is a screen figure of a data set list screen. It is a schematic diagram which shows the creation process of an element set. It is a screen figure of an element set list screen.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 Job analysis support apparatus, 110 User interface processing part, 112 Input part, 114 Display part, 116 Job relation information acquisition part, 118 Job content information acquisition part, 120 Job structure information acquisition part, 122 Data declaration information acquisition part, 124 Data Definition document acquisition unit, 126 Job list display unit, 128 Data set list display unit, 130 Element set list display unit, 140 Data processing unit, 142 Job list generation unit, 144 Data set generation unit, 146 Element set generation unit, 148 Provisional List generation unit, 150 provisional list addition unit, 152 provisional list combination unit, 154 job list update unit, 160 data holding unit, 162 job relation information holding unit, 164 job content information holding unit, 168 job structure information Holding unit, 170 Data declaration information holding unit, 172 Data definition document holding unit, 202 Job execution device, 200 Job execution device group, 210 External storage device, 220 Business system, 230 Job management device, 240 Job relationship information, 242 Job relationship Document, 244 First job structure information, 246 Second job structure information, 248 Job structure design document, 250 Data declaration information, 252 Data definition document file, 258 Job content information, 274 Job set, 280 Job list screen, 298 Assignment information , 330 Data set list screen, 340 element set, 350 element set list screen.

Claims (8)

Job relation information indicating the preceding job corresponding to the preceding stage of each job for a plurality of jobs whose dependency is determined so that one or more jobs corresponding to the succeeding stage are executed on condition that one or more jobs corresponding to the preceding stage are executed. A job relation information acquisition unit to be acquired;
Referring to the job-related information, a job for which no preceding job is set is detected as the first job, and a plurality of temporary lists are generated on the memory corresponding to each of the plurality of first jobs, and the corresponding temporary list is created. A provisional list generator for registering the first job;
Referring to the job-related information and the registration contents of each provisional list, all of the preceding jobs are already registered in any provisional list, and themselves detect unregistered jobs in the provisional list as candidate jobs. A provisional list addition unit that repeats additional registration processing for additionally registering a job in a provisional list in which the preceding job is registered until all of the plurality of jobs are registered in any provisional list;
With reference to the job-related information and the registered contents of each provisional list, when the job registered in the first provisional list corresponds to the preceding job of the job registered in the second provisional list, the second provisional list A temporary list combining unit that combines the second temporary list with the first temporary list by transferring the job registered in the first temporary list;
A job list display unit that displays a job list in which a plurality of provisional lists are combined as a list in which the plurality of jobs are arranged in a line based on the dependency relationship;
A job analysis support apparatus comprising:   The provisional list adding unit additionally registers the candidate job immediately after the preceding job in the provisional list in which the preceding job of the candidate job is registered in the additional registration processing. The job analysis support device described. A job content information acquisition unit for acquiring job content information in which each job is associated with job attribute information indicating a job attribute;
By referring to the job content information and adding job attribute information to each job arranged in a line in the job list, the job list is modified so that a set of jobs and job attribute information becomes a list element. A job list update unit,
The job analysis support apparatus according to claim 1, wherein the job list display unit displays a list of jobs and sets of job attribute information on a screen display of the corrected job list. The job content information acquisition unit acquires a job name of each job set to indicate a job type according to a predetermined naming rule as a part of job attribute information,
The job list display unit identifies a job type from a job name, and displays each list element of the job list on a screen in a display mode predetermined according to the job type. 4. The job analysis support device according to 3. A job structure information acquisition unit for acquiring job structure information indicating one or more programs constituting the job and one or more data files to be accessed by each program;
Referring to the job content information and the job structure information, a data set that associates a data file, a program that accesses the data file, a job that uses the program as a component, and job attribute information that corresponds to the job A data set generation unit for generating
A data set list display unit for displaying one or more data sets including the selected job on the screen as a data set list when any job is selected by the user in the job list;
The job analysis support apparatus according to claim 3, further comprising:   The job analysis support apparatus according to claim 5, wherein the job structure information acquisition unit acquires the job structure information from a code described in a job control language (JCL). A data declaration information acquisition unit for acquiring data declaration information indicating a data name declaration and a data type declaration of one or more data elements included in the data file;
A data definition document acquisition unit that acquires a data definition document file that is a design document indicating the meaning and data type of one or more data elements included in the data file;
An element set generation unit that generates an element set that associates the meaning, data name, and data type of the data element with reference to the data declaration information and the data definition document file;
An element set list that displays one or more element sets as an element set list on one or more data elements related to the selected data set when one of the data sets is selected by the user in the data set list A display unit;
The job analysis support apparatus according to claim 5, further comprising: Job relation information indicating the preceding job corresponding to the preceding stage of each job for a plurality of jobs whose dependency is determined so that one or more jobs corresponding to the succeeding stage are executed on condition that one or more jobs corresponding to the preceding stage are executed. The ability to get and
Referring to the job-related information, a job for which no preceding job is set is detected as the first job, and a plurality of temporary lists are generated on the memory corresponding to each of the plurality of first jobs, and the corresponding temporary list is created. A function to register the first job,
Referring to the job-related information and the registration contents of each provisional list, all of the preceding jobs are already registered in any provisional list, and themselves detect unregistered jobs in the provisional list as candidate jobs. A function of repeating additional registration processing for additionally registering a job in a provisional list in which the preceding job is registered until all of the plurality of jobs are registered in any one of the provisional lists;
With reference to the job-related information and the registered contents of each provisional list, when the job registered in the first provisional list corresponds to the preceding job of the job registered in the second provisional list, the second provisional list A function of combining the second provisional list with the first provisional list by transferring the job registered in the first provisional list;
A function of displaying a job list in which a plurality of provisional lists are combined as a list in which the plurality of jobs are arranged in a line based on the dependency relationship;
A job analysis support program characterized by causing a computer to perform the job.

Images