Apparatus and method for managing job flows in an information processing system

The present invention relates to a management support program, a management support device, and a management support method.

When daily business processing in corporate activities is executed by an information processing system, a job management system that manages the operations and execution schedules of a plurality of jobs is often used.

Such a job management system is introduced not only at the head office of a company but also at each branch and each base. Then, the operation manager monitors and manages that the operation management work is operating correctly within the range closed to each branch / base.

In recent years, servers that have been held and managed at each branch or base have been virtualized and aggregated, and are often collected and managed in one place. Along with the flow of server virtualization aggregation, a small number of operation managers monitor the virtualized aggregated servers and manage and confirm that the entire operation management business is operating correctly. As a result, the number of operations management tasks monitored and managed by each operation manager is increasing.

There are the following technologies as technologies related to job management. As the first technology, there is a technology that analyzes and displays the management information collected by the management server or the management data of the Web service for management on the user's application screen and appropriately informs the user of the system status (for example, patent documents). 1.). In the first technique, the task division unit analyzes the definition information in which the task flow of the compound task including a plurality of tasks is defined, and divides the compound task into each task. The task group analysis unit classifies two or more tasks that are the same in the task flow defined in the definition information into the same task group. The task group analysis unit classifies tasks that are not equal in the task flow defined in the definition information into individual task groups, and classifies a plurality of tasks included in the compound task into two or more task groups.

As a second technology, there is an image processing device that displays a plurality of elements divided into groups included in job information related to image data processing in a display area allocated to each job on the screen for a plurality of jobs. (For example, Patent Document 2.). In the second technique, the control unit determines whether or not all the plurality of elements can be displayed in the display area of the first screen displayed on the display unit. For jobs that cannot be displayed, the control unit displays all elements that belong to the same group as the elements that cannot be displayed in the display area of the first screen on the second screen that accepts the transition operation and transitions from the first screen. Take control.

As a third technique, there is a technique for easily grasping the job execution order (for example, Patent Document 3). In the third technique, the computer classifies a plurality of jobs included in the log data according to which time interval the job end time belongs to among the plurality of time intervals. For a plurality of jobs included in the first time interval, the computer generates first data indicating the job execution order relationship based on the job end time. In addition, the computer generates second data indicating the job execution order relationship for a plurality of jobs included in the second time interval following the first time interval, based on the job end time. Based on the end time of the job included in the first time interval and the end time of the job included in the second time interval, the computer will use the job included in the first time interval and the second time interval. Analyze the execution order relationship with the jobs included in. Then, the computer generates data showing the execution order relationship of the jobs from the first time interval to the second time interval.

<p><patcit num="1"><text>Japanese Unexamined Patent Publication No. 2008-3709</text></patcit><patcit num="2"><text>Japanese Unexamined Patent Publication No. 2010-166336</text></patcit><patcit num="3"><text>Japanese Unexamined Patent Publication No. 2011-128828</text></patcit><patcit num="4"><text>Japanese Unexamined Patent Publication No. 6-83598</text></patcit><patcit num="5"><text>JP-A-63-241605</text></patcit></p>

<p> Due to the virtual consolidation of servers using data centers, the situation where job flows including multiple jobs are executed is increasing. Therefore, the operation manager may group job flows in order to facilitate monitoring of a plurality of job flows.</p><p> However, in the first technology, the job flow in batch business is often a flow of processing in a smaller unit than that of a Web service. In an environment where a large number of jobs exist, even if jobs that are in a parallel relationship are simply grouped, the job flow will have a large number of small groups, and monitoring and management will remain difficult. Therefore, no effect can be expected by grouping in a large-volume job environment.</p><p> Further, in the second technique, since the grouping is performed only by simple setting information, the order / dependency between the groups cannot be considered. Therefore, it cannot be used for monitoring and managing job flows in batch operations, which makes monitoring and management difficult unless the order and dependencies between groups are taken into consideration when grouping.</p><p> In this way, when grasping the status of a plurality of job flows, even if the jobs are grouped by the first or second technique and displayed on the screen, the contents of the job schedule screen become complicated. As a result, even if such a screen is referred to, the operation manager may not be able to properly judge the status of a plurality of job flows.</p><p> In addition, in the environment before virtualization consolidation, if there is no notification from a certain branch / base that a problem has occurred by a specific time, the next process will proceed. Processing may be synchronized. As a result, when a job is executed at a plurality of bases, the operation manager can synchronize the processing of the multiple bases with the job divided at a specific time as a guide.</p><p> However, when servers are consolidated in a data center or the like, it becomes difficult to grasp the correspondence between jobs for each branch / base and which job is followed by which job.</p><p> As one aspect of the present invention, there is provided a management support technique that facilitates grasping the job execution status and the transition relationship between jobs in job flow monitoring.</p>

<p> The management support program according to one aspect of the present invention causes a computer to perform the following processing. That is, the computer generates classification information in which jobs are classified for each attribute based on the attribute information of a plurality of jobs included in the managed job flow in response to a request from the monitoring terminal. The computer groups a plurality of jobs into a plurality of groups according to the attribute information by using the classification information and the transition relationship information regarding the transition relationship between jobs in the job flow. Computer<u style="single">The job execution section for each of a plurality of groups is obtained based on the number of jobs from the start job to each job in the job flow.</u>The computer generates job execution schedule display information. The job execution schedule display information displays the transition relationship between jobs when one of the plurality of jobs and the job following the job belong to different groups. At the same time, the job execution schedule display information is displayed for each group.<u style="single">Asked about</u>Execution interval to other groups<u style="single">Asked about</u>Display in correspondence with the execution section.</p>

<p> According to one aspect of the present invention, in monitoring the job flow, it becomes easy to grasp the execution status of jobs and the transition relationship between jobs.</p>

<figref num="1">An example of the management support device in this embodiment is shown.</figref><figref num="2">The processing at the time of aggregation of batch operations in this embodiment and the processing flow of management / monitoring of batch operations after aggregation are shown.</figref><figref num="3">An example of the job / branch correspondence table in this embodiment is shown.</figref><figref num="4">An example of the job classification table in this embodiment is shown.</figref><figref num="5">An example of the relationship information between jobs in this embodiment is shown.</figref><figref num="6">The relationship between each job and the job classification information in this embodiment is shown.</figref><figref num="7">An example of the group job related table in this embodiment is shown.</figref><figref num="8">A job flow diagram in which jobs in the present embodiment are grouped by consecutive sections with the same classification information is shown.</figref><figref num="9">An example of the successor group management table in this embodiment is shown.</figref><figref num="10">It is a figure which shows the relationship between groups in this embodiment.</figref><figref num="11">An example of the distance management table in this embodiment is shown.</figref><figref num="12">An example of the relationship between the job flow and the distance of each job in this embodiment is shown.</figref><figref num="13">An example of the execution section management table in this embodiment is shown.</figref><figref num="14">An example of the relationship between the group and the section in this embodiment is shown.</figref><figref num="15">An example of the group for each job classification and the relationship between the groups in the present embodiment is shown.</figref><figref num="16">The group monitoring diagram in this embodiment is shown.</figref><figref num="17">The group monitoring diagram which displays a plurality of sections together in this embodiment is shown.</figref><figref num="18">An example of the reduced display management table in this embodiment is shown.</figref><figref num="19">The system configuration diagram for the batch migration process in this embodiment (Example) is shown.</figref><figref num="20">The job / branch correspondence information temporary table in this embodiment (Example) is shown.</figref><figref num="21">The job / branch correspondence table in this embodiment (Example) is shown.</figref><figref num="22">The overall flow of batch migration processing in this embodiment (Example) is shown.</figref><figref num="23">The flow of the branch / base information extraction process (S13) in which the job was executed in the present embodiment (Example) is shown.</figref><figref num="24">The system configuration diagram about the grouping display processing of the job flow in this Embodiment (Example) is shown.</figref><figref num="25">The job-related information table 71 in this embodiment (Example) is shown.</figref><figref num="26">The job classification table 72 in this embodiment (Example) is shown.</figref><figref num="27">The job classification information temporary table 73 in this embodiment is shown.</figref><figref num="28">The execution section management table 74 in this embodiment (Example) is shown.</figref><figref num="29">The distance management table 75 in this embodiment (Example) is shown.</figref><figref num="30">The group job-related table 76 in this embodiment (Example) is shown.</figref><figref num="31">The subsequent group management table 77 in this embodiment (Example) is shown.</figref><figref num="32">The group display table 78 in this embodiment (Example) is shown.</figref><figref num="33">The reduced display management table 79 (when reducing 3 sections to 1 section) in this embodiment (Example) is shown.</figref><figref num="34">The reduced group display table (when 3 sections are reduced to 1 section) in the present embodiment (Example) is shown.</figref><figref num="35">The overall flow of the grouping display processing of the job flow in this embodiment (Example) is shown.</figref><figref num="36">The flow of the job classification information extraction process (S22) in this embodiment (Example) is shown.</figref><figref num="37">The flow (No. 1) of the derivation process (S23) of the relationship between the group and the job in this embodiment (Example) is shown.</figref><figref num="38">The flow (No. 2) of the derivation process (S23) of the relationship between the group and the job in this embodiment (Example) is shown.</figref><figref num="39">The flow of the derivation process (S24) of the connection relationship between groups in this embodiment (Example) is shown.</figref><figref num="40">The flow of the derivation process (S25) of the distance from the head job of each job in this embodiment (Example) is shown.</figref><figref num="41">The flow of the derivation process (S26) of the group execution section and the connection section in the present embodiment (Example) is shown.</figref><figref num="42">The flow of the group display table creation process (S27) in this embodiment (Example) is shown.</figref><figref num="43">The flow of the update processing (S28) of the execution status of the group on the group display table in the present embodiment (Example) is shown.</figref><figref num="44">The flow (No. 1) of the group reduction display data creation process (S29) in the present embodiment (Example) is shown.</figref><figref num="45">The flow (No. 2) of the group reduction display data creation process (S29) in the present embodiment (Example) is shown.</figref><figref num="46">A group list of job classification information of the selected section in the present embodiment (Example) is shown.</figref><figref num="47">The screen displayed when GrpB-4 is selected in the group list in this embodiment (Example) is shown.</figref><figref num="48">The flow of the display processing of the client in this Embodiment (Example) is shown.</figref><figref num="49">It is an example of the block diagram of the hardware environment of the computer which executes the program in this Embodiment (Example).</figref>

FIG. 1 shows an example of the management support device according to the present embodiment. The management support device 1 includes a classification information generation unit 2, a grouping unit 3, and a display information generation unit 4.

The classification information generation unit 2 is classified information (job classification information) in which jobs are classified for each attribute based on the attribute information of a plurality of jobs included in the managed job flow in response to a request from the information processing terminal. To generate. As an example of the classification information generation unit 2, there is a CPU 112 that executes the extraction process 65 described later.

The grouping unit 3 groups a plurality of jobs into a plurality of groups according to the attribute information by using the classification information and the transition relationship information regarding the transition relationship between jobs in the job flow. As an example of the grouping unit 3, there is a CPU 112 that executes the display information creation process 66 described later. An example of the transition-related information is the job-related information table 71, which will be described later.

The display information generation unit 4 generates job execution schedule display information. The job execution schedule display information displays the transition relationship between jobs when one of the plurality of jobs and the job following the job belong to different groups. At the same time, the job execution schedule display information is displayed by associating the execution section of the job of each group with the execution section of the job of another group based on the number of jobs from the start job to each job in the job flow. As an example of the display information generation unit 4, there is a CPU 112 that executes the display information creation process 66 described later. An example of the execution schedule display information is a group monitoring diagram (Fig. 16), which will be described later.

With this configuration, in job flow monitoring, it becomes easy to grasp the job execution status and the transition relationship between jobs.

The attribute information may include information about the execution conditions of the job. In addition, the attribute information may include information about the name or group given to the job.

With this configuration, it is possible to extract job classification information during operation by using the job execution conditions and features.

FIG. 2 shows the processing at the time of aggregation of batch operations in the present embodiment and the processing flow of management / monitoring of batch operations after aggregation. The processing flow of batch business aggregation is as follows. First, existing batch information from each branch / base (18) is collected in the data center 11 (S1).

The computer 12 in the data center 11 modifies the batch information (uncorrected batch information 13) so that the collected batch information can be executed by the information processing system 17 (S2). For example, the computer 12 mechanically replaces the job name in the batch information, the IP (Internet Protocol) address of the server that executes the job, the notification destination in the event of an abnormality, and the like.

The computer 12 inputs the corrected batch information (corrected batch information 14) to the information processing system 17 (S3).

A test is made to see if the modified batch work works correctly in the information processing system 17 (S4).

The operation manager operates and monitors the information processing system using the computer 12 (S5).

Next, the processing flow for managing and monitoring batch operations after aggregation will be described. This embodiment is a technology for facilitating the management and monitoring of large-scale batch operations, and makes it possible to automatically construct and display an ideal job flow in terms of operation management (monitoring).

The computer 12 extracts the relationship information between jobs from the job flows that form a plurality of batch jobs (S6), and creates one job flow. Therefore, in order to construct an ideal job flow in terms of operation management (monitoring), the computer 12 performs the following processing.

The computer 12 extracts the job classification information from the uncorrected batch information 13 at the time of virtualization aggregation. (S7 (S7-1)) In addition, the computer 12 extracts the job classification information from the modified batch information 14 during operation (S7 (S7-1)).

Computer 12 displays the job flow by grouping jobs based on the extracted job classification information (S8).

&lt;S7: Process to extract job classification information&gt; . S7-1 (At the time of virtualization aggregation) Computer 12 extracts information about the branch / base that executes each job from the batch information 13 before aggregation, and extracts it. Classify jobs based on information about the branches / bases that have been created.

Batch operations for each branch / base before consolidation are units that are meaningful in terms of operations. Therefore, by grouping each job in the batch business by branch / base based on the extracted information about the branch / base, it is possible to group the jobs in units that are meaningful in business.

Here, as shown in FIG. 3, the computer 12 generates a job / branch correspondence table that tabulates the correspondence between each job and the branch / base information. Then, the computer 12 uses the job / branch correspondence table when grouping the jobs in S8.

In the computer 12, at the timing (S2) in which the batch information is replaced according to the environment after aggregation in the flow at the time of aggregation of batch operations in FIG. 2, the jobs in the batch information 13 before aggregation are located at which branch / base. Extract information on what was being done in.

Branch / base information that was executed before each job was aggregated can be extracted based on the characteristics of the job name, the IP address information of the job execution server, and the error notification destination of the job or job flow in the batch information before aggregation. .. As shown in FIG. 3, the computer 12 stores the correspondence between the extracted job and the branch / base information in the job / branch correspondence table which is a table.

The method of extracting the branch / base information where the job was executed is as follows. -How to use the IP address information of the job execution server The IP address of the execution server is specified for each job or job flow. In addition, the subnet information of the IP address differs for each branch / base. The computer 12 uses this feature to determine the branch / base where the job was executed from the subnet information of the IP address of the execution server set in the job.

-How to use the error notification destination of a job An error notification destination is set for each job or job flow. Before aggregation, a different operation manager or operator is specified for each branch / base as this abnormality notification destination. Therefore, the computer 12 determines the branch / base where the job was executed from the set error notification destination.

Since the actual branch / base name cannot be obtained, an identifier is set as the branch / base information in the job / branch correspondence table (for example, the first branch / base information is "ID = 0001"). , The second one is "ID = 0002", etc.).

-S7-2 (during operation) The computer 12 can classify each job by using the feature of the modified batch information 14 even in the case other than the time of virtualization aggregation (during operation). When the number of jobs becomes large and monitoring becomes difficult due to virtualization aggregation, jobs can be classified by the above S7-1 process.

However, if you do not implement virtualization aggregation but have a large number of job environments and want to facilitate monitoring and management, or if you want to group by other methods even in the environment after virtualization aggregation, S7-2 Jobs can be classified by processing and the classified information can be tabulated. When grouping jobs in S8, computer 12 uses the table obtained here.

The method for extracting job classification information during operation is as follows. The computer 12 selects an appropriate extraction method from these extraction methods and classifies the jobs.

-Method of using the correspondence between jobs and branch / branch information The computer 12 can classify jobs from the job / branch correspondence table (Fig. 3) acquired at the time of virtualization aggregation. As shown in FIG. 4, the branch / base information in the job / branch correspondence table becomes the job classification information 16 (job classification table 16-1) as it is.

-How to use the characteristics of job names Job names may have specific prefixes or suffixes attached to the system or business unit. For example, the job name may have a system name or a business name attached to a prefix or a suffix, such as " system_start processing" or " business_master update processing". Computer 12 classifies each job based on the regularity of this job name.

For example, ask the operator to specify the "delimiter" of the job name and the "position of the token to be classified". In this case, computer 12 separates the job names with a delimiter and classifies them by the token at the specified position. For example, when the delimiter is "_" and the token position is "head", " system_start processing" and " business_master update processing" are " system" and " business". It can be divided into classifications such as.

When modifying the batch information at the time of virtualization aggregation, "branch " is added to the job name of the job executed at each branch / base, and "branch A_business start processing on the day" and "branch B_" are added. In some cases, information on which branch / base was used, such as "Same-day business start processing", may be given. Therefore, it may be possible to classify each branch / base by job name.

How to use scheduled job start date information (schedule information) Scheduled start date information is specified for each job. Jobs with the same scheduled start date information can be considered to be started on the same day because they are jobs of a part of the same job or related jobs. For example, jobs related to job A may be started every Monday, jobs related to job B may be started on weekdays, and so on. Therefore, the computer 12 can be classified by jobs having the same scheduled start date information.

&lt;S8: Job flow display processing by grouping jobs based on job classification information&gt; Computer 12 groups and displays jobs based on the correspondence between jobs extracted in S7 and job classification information. By grouping and displaying jobs, it becomes easier for jobs to fit on the screen in a job flow in which a large number of jobs exist. In addition, since it is grouped by the business unit that was performed at the branch / base before the consolidation and the scheduled start date information of the business unit, it becomes easy to grasp the specific business process and the relationship between the business.

As a premise of S8, before performing grouping, for example, as shown in FIG. 5, one job flow (relationship information between jobs 15) is created from a plurality of jobs by using the above-mentioned third technique or the like. ..

FIG. 5 shows an example of the relationship information 15 between jobs in the present embodiment. Here, the computer 12 can clarify and group the job classifications included in the job flow of FIG. 5 by using the job classification table 16-1 created in S7.

FIG. 6 shows the relationship between each job and the job classification information in this embodiment. FIG. 6 shows a job flow that clarifies the classification of jobs included in the job flow of FIG.

In the following, an example of grouping based on branch / base information at the time of virtual aggregation is shown. The original job names are jobs 1 to 13, but they are represented by branch information in Fig. 6 and below for easy understanding.

Up to the above, the relevance information 15 between jobs and the job classification information 16 have been obtained. Therefore, the computer 12 performs grouping by the following method based on the relevance information 15 between jobs and the job classification information 16 and displays the grouping information to facilitate monitoring.

(1) First, the computer 12 groups consecutive jobs having the same classification information into one group based on the job classification table 16-1 created in S7 and the relevance information 15 between jobs, and Fig. 7 Create the group / job related table shown in.

At this time, in the case of a branched job, if even one of the branch destinations has the same classification information, the branched job is set to the same group. If all subsequent jobs have different classification information, each subsequent job is a single group of jobs. Figure 8 shows a job flow diagram in which jobs are grouped by consecutive sections with the same classification information.

(2) Next, the computer 12 tabulates the connection relationship between the groups as shown in FIG. 9 based on the group-job relationship table created in (1) above and the job connection relationship. Generate a group management table. FIG. 10 shows a diagram showing the relationships between the groups in the present embodiment.

As shown in Fig. 10, jobs can be grouped and displayed based on the relationships between groups. However, it is difficult to understand the order of processing only from the relationship diagram of FIG. Therefore, the following procedure is performed so that it is possible to visualize where the currently executing job is located in the whole.

(3) The computer 12 obtains the distance (number of arrows) from the first job (the first job executed in the job flow) for each job. If there are multiple leading jobs, or if there is branching / convergence, there are multiple distances from the leading job. In such cases, the longest distance is the distance to the job. Figure 11 shows a distance management table that manages the distance from the first job to each job.

Furthermore, Fig. 12 shows an example of the relationship between the job flow and the distance between each job. FIG. 12 shows the job flow diagram of FIG. 8 divided by the distance from the first job using the distance management table of FIG.

(4) Next, the computer 12 determines the execution section of each group from the subsequent group management table (Fig. 9) and the distance management table (Fig. 11), and creates a table. Specifically, the computer 12 finds the shortest distance and the longest distance among the jobs included in the group. Here, the range from the shortest distance to the longest distance is the execution section of the group.

Further, the computer 12 calculates the section to be connected to the succeeding group of each group from the connection relationship of jobs (FIG. 9) and the distance management table from the first job to each job (FIG. 11). As shown in FIG. 13, the computer 12 generates an execution section management table in which the calculated section is added to the subsequent group management table. FIG. 14 shows an example of the relationship between a group and an interval.

(5) Groups of the same job classification are displayed on one horizontal axis. That is, if there are multiple groups of the same job classification in the same section, they are displayed together. For example, in section 1, GrpB-1 and GrpB-2 of the group for branch B exist, so GrpB-1 and GrpB-2 are collectively displayed in GrpB.

FIG. 15 shows an example of a group for each job classification and a relationship between the groups. After grouping groups of the same job classification that exist in the same section, the relationships between the groups are displayed by arrows as shown in Fig. 15 using the execution section management table (Fig. 13).

That is, when the preceding job and the succeeding job of the job belong to different groups among the consecutive jobs, the transition information is displayed by an arrow.

(6) FIG. 16 shows a group monitoring diagram in the present embodiment. At the time of monitoring, as shown in FIG. 16, a group monitoring diagram is displayed on the monitor screen. In the group monitoring diagram, the vertical axis shows the grouped attribute information, the horizontal axis shows the time, and the bar showing the job execution period is displayed in a Gantt chart format separated by a predetermined time interval. In the group monitoring diagram, the current execution position of each group is indicated by a thick arrow or the like from the section positions of the currently executing job and the job in each group.

By moving the thick arrow from section 0 to the right as the job is executed, it becomes easier to understand the current execution location for the entire job flow. In addition, by changing the color of the thick arrow according to the execution status of the jobs in each group, the status of the jobs in the group can be displayed in an easy-to-understand manner.

When the number of groups is large, the arrows indicating the relationships between the groups are often displayed, making it difficult to understand the relationships. Therefore, when a specific group is specified, the relationship is displayed in an easy-to-understand manner by displaying only the arrows of the preceding / succeeding relationship related to that group.

In addition, if a deadline time exists for jobs in each group in a certain section, that time is displayed. If the execution is completed or delayed, the status will be indicated along with the deadline.

(7) In the case of a job flow with a large number of jobs, the number of sections may be too large to fit the group monitoring diagram in (6) above on the screen. In this case, the computer 12 automatically displays the group monitoring diagram so that it fits in the screen, or reduces the width by an arbitrary size.

However, simply reducing the width reduces the width of one section, making it difficult to see. Therefore, as shown in FIG. 17, the computer 12 reduces and displays the group monitoring diagram by grouping a plurality of sections.

Also, when multiple sections are grouped together, even if there are multiple arrows indicating the relationship between groups in each section, if all are displayed in the same way, the number of arrows per section will increase. , It becomes difficult to see.

Therefore, the arrows in the section / section are summarized based on the following concept. The lowermost figure of FIG. 17 is obtained by performing the following (A) to (D) with respect to the uppermost figure of FIG.

(A) When the size of the group monitoring diagram is automatically changed, the computer 12 does not reduce all of the monitoring diagram, and the computer 12 reduces the size based on the relationship between the screen size required for display and the current screen size. Ask for. For any size, the operator specifies the degree of reduction.

(B) The computer 12 calculates the number of sections I to be combined into one section from the reciprocal of the degree of reduction. In the example of FIG. 17, since the reduction degree was 20%, 5 sections are newly summarized as 1 section at 1 / 0.2. At this time, the number of sections to be summarized I = 5 sections.

(C) The computer 12 sets the correspondence between the new section N and the arrow indicating the relationship between the groups in each section of the section "N × I ~ (N + 1) × I-1" before reduction. Ask. In the example of FIG. 17, since the number of sections I to be combined is 5, the new section 1 corresponds to the sections 5 to 9 before reduction. From this, it is possible to obtain the correspondence between which section the arrow before reduction becomes the arrow from which section to which section in the new section. The relationship between the groups and the connection section information before and after the reduction are stored in the reduction display management table as shown in FIG.

(D) The computer 12 combines the information of the arrows in the new section with the same relationship between the groups in the new section from the information of the relationship between the groups in the new section saved in the reduced display management table (Fig. 18). Summarize. With reference to the "Arrow ID after reduction" column in the reduced display management table (Fig. 18), for example, if there are multiple arrows from section 0 of GrpA to section 0 of GrpB in the new section, the computer 12 will use that. Display multiple arrows as one arrow.

In addition, if there is an arrow in the reduced display management table in the opposite direction, the computer 12 combines them into one as a bidirectional arrow (see the "two-way judgment flag" column in the reduced display management table). For example, in the new section, if there is an arrow from section 0 of GrpA to section 0 of GrpB and an arrow from section 0 of GrpB to section 0 of GrpA, the directions of these two arrows are opposite. In this case, the computer 12 displays as one double-headed arrow instead of two single-way arrows. As a result, the display of relationships between groups can be maintained even if the number of arrows is reduced.

The computer 12 executes the above (A) to (D), reduces and displays the groups, and then displays the execution status of each group and the deadline time as in the above (6). As a result, the status of each group can be similarly monitored even in the reduced display state.

According to this embodiment, the group display is performed based on the distance from the first job and the execution section of each group. The display size is automatically changed according to the screen size in a format that shows the relationship between groups. Moreover, even in a large-scale job environment, the execution status of the entire job flow can be easily understood, and it becomes easy to monitor and manage from a bird's-eye view.

In addition, by grouping jobs by branch / base information before aggregation and job classification information during operation, it is possible to display the business meaning in an easy-to-understand format, which makes it easier to monitor and manage. ..

By automatically performing the above grouping, the workload at the time of job aggregation in server virtualization aggregation can be suppressed.

The details of the examples of this embodiment will be described below. &lt;Batch migration process&gt; FIG. 19 shows a system configuration diagram for the batch migration process in the present embodiment (Example). When the batch information collected from each branch / base is transferred to the environment after virtualization aggregation, the processing shown in Fig. 19 is performed.

It is assumed that the batch information 32 before migration is aggregated by a predetermined tool or the like from each branch / base before virtualization aggregation.

The job setting replacement information 31 is information to be replaced and information after replacement, which is used when automatically replacing the job setting information with the environment after migration. For example, the job settings include "job execution server information". The job setting replacement information 31 stores information such as replacing the execution server information A before migration with the execution server information B after migration. The job setting replacement information 31 is created in advance.

The migration tool 33 is a tool for migrating the batch information and job information before virtualization aggregation to the system in the data center, and is executed on the computer by the operation of the operator. The migration tool 33 executes the batch conversion process 34 and the extraction process 35.

The batch conversion process 34 converts the batch information 32 before virtualization aggregation so that it can be used in the environment after virtualization aggregation. For example, when the batch management products are different before and after aggregation, or when the product versions are different, the batch conversion process 34 performs the following processing so that the batch management products can be used in the environment after aggregation. That is, the batch conversion process 34 generates the post-migration batch information 36 by converting the batch information (pre-migration batch information) 32.

Further, the batch conversion process 34 uses the job setting replacement information 31 to replace the information that needs to be changed before and after the migration among the job setting information, and sets the parameters according to the environment after the migration in the batch information. To do.

The extraction process 35 extracts information on which branch / base each job was executed from the pre-migration batch information 32. That is, the extraction process 35 extracts from the pre-migration batch information 32 the information required for the grouped display of the job flow, in which branch / base each job was executed. The extraction process 35 creates a job / branch correspondence table 41 from the correspondence between the extracted job and the branch, and stores it in the definition information database (DB) 40 in the server 39.

The registration tool registers the post-migration batch information 36 as the operation batch information 42 in the definition information DB 40 in the server 39.

FIG. 20 shows a temporary table of job / branch correspondence information in the present embodiment (example). The job / branch correspondence information temporary table 51 is a temporary table used in the extraction process 35 for extracting the branch / base information in which the job was executed. The job / branch correspondence information temporary table 51 includes data items of "job number", "subnet information", "abnormality notification destination", and "branch / base number".

FIG. 21 shows a job / branch correspondence table in the present embodiment (example). The job / branch correspondence table 41 includes data items of "branch / base number" and "job number".

FIG. 22 shows the overall flow of batch migration processing in the present embodiment (Example). In the batch migration process, the following process is performed.

The migration tool 33 converts the pre-migration batch information 32 and the information of each job into job information according to the product / version in the post-migration environment (S11).

The migration tool 33 uses the job setting replacement information 31 to convert the job information converted in S11 so that it can be used in the environment after migration (S12). Here, if the job setting replacement information 31 exists, the migration tool 33 performs the following processing. That is, when the migration tool 33 has the setting information to be replaced according to the job setting replacement information 31 in the job information converted in S11, the migration tool 33 sets the job setting information in the job information converted in S11. Replace and generate batch information 36 after migration. The migration tool 33 outputs the generated post-migration batch information 36.

The migration tool 33 performs an extraction process 35 that extracts information on which branch / base each job was executed from the pre-migration batch information 32, and registers it in the definition information DB 40 on the server 39 of the job management product ( S13). The processing of S13 will be described in detail in FIG.

The operator corrects the batch information 36 after migration if necessary (S14). Modifications can be made manually or by using another tool.

The operator uses the registration tool 37 to register the post-migration batch information 36 in the definition information DB 40 on the server 39 of the job management product.

FIG. 23 shows the flow of the branch / base information extraction process (S13) in which the job in the present embodiment (example) was executed.

The migration tool 33 acquires the IP address of the job execution server from the pre-migration batch information 32, and extracts the subnet information from the IP address. The migration tool 33 stores the relationship between the job name (job number) and the subnet information in the job / branch correspondence information temporary table 51 (S13-2).

The migration tool 33 acquires notification destination information when a job is abnormal from the pre-migration batch information 32. The migration tool 33 stores the relationship between the job name (job number) and the notification destination information in the job / branch correspondence information temporary table 51 (S13-3).

The migration tool 33 repeats the processes of S13-2 to S13-3 for all the jobs of the pre-migration batch information 32.

After processing S13-2 to S13-3 for all jobs in batch information 32 after migration, the migration tool 33 checks the subnet information of the jobs stored in the job / branch correspondence information temporary table 51. If the confirmed job subnet information is different from the previously confirmed job subnet information, the migration tool 33 allocates a new branch / base number to the job and registers it in the job / branch correspondence information temporary table 51.

Alternatively, if the confirmed job subnet information is the same as the previously confirmed job subnet information, the migration tool 33 performs the following processing. That is, the migration tool 33 assigns the same branch / base number as the branch / base number assigned to the confirmed job to the currently confirmed job and registers it in the job / branch correspondence information temporary table 51 ( S13-5).

In the case of a job for which subnet information is not set, the migration tool 33 assigns a branch / base number of the job having the same error notification destination and registers it in the job / branch correspondence information temporary table 51. However, if there are multiple jobs for which the same error notification destination is set and each has a different branch / base number, the migration tool 33 does not assign the branch / base number (S13-5).

If the job has neither subnet information nor error notification destination set, the migration tool 33 classifies the job as a job without branch / base information. Therefore, for example, a special branch / base number such as "0" is assigned and registered in the job / branch correspondence information temporary table 51.

The migration tool 33 repeats the processes of S13-5 to S13-7 for all the jobs in the created temporary table 51. After completing the processing of S13-5 to S13-7 for all the jobs in the created temporary table 51, the migration tool 33 performs the following processing. That is, the migration tool 33 stores the relationship between the job name stored in the job / branch correspondence information temporary table 51 and the branch / base number in the job / branch correspondence table 41 in the definition information DB 40 (S13-8). ..

&lt;Grouping Display Processing of Job Flows&gt; FIG. 24 shows a system configuration diagram for the grouping display processing of job flows in the present embodiment (Example). The processing shown in FIG. 24 is performed when the job flow is grouped and displayed when batch information is operated in the environment after virtualization aggregation or in the operating environment.

The system of FIG. 24 includes a server 39 and a client device (hereinafter referred to as "client") 81.

The server 39 includes a scheduler 61, a job execution unit 62, a definition information DB 40, a display information creation unit 63, and a memory 67. The scheduler 61, the job execution unit 62, and the display information creation unit 63 are executed by a processor such as a CPU (Central Processing Unit). The definition information DB40 is stored in the storage device.

The scheduler 61 manages the job execution schedule. The job execution unit 62 executes the job managed by the scheduler 61 based on the schedule information.

The definition information DB 40 stores the job / branch correspondence table 41 and the operation batch information 42 obtained in the batch migration process described above.

The display information creation unit 63 creates information corresponding to the request from the client 81 and returns it to the client 81. The display information creation unit 63 executes the determination process 64, the extraction process 65, and the display information creation process 66.

The determination process 64 determines the related information between jobs. That is, the determination process 64 extracts the related information between jobs from the operation batch information 42 and summarizes the related information between jobs so that it can be displayed in the form of a job flow. The display information creation unit 63 holds the related information between jobs as the job related information table 71 and uses it when displaying the grouped job flow.

The extraction process 65 extracts job classification information. That is, the extraction process 65 performs the following process when the job / branch correspondence table 41 is not created by the batch migration process or the like, or when the grouping method is specified. That is, the extraction process 65 classifies the jobs based on the operation batch information 42 and creates the job classification table 72.

The display information creation process 66 creates display information by grouping jobs based on job classification information. That is, the display information creation process 66 uses the job-related information table 71 and the job classification table 72 to create information for grouping and displaying the job flow.

The memory 67 holds the job-related information table 71 and the job classification table 72. Further, the memory 67 holds a job classification information temporary table 73, an execution section management table 74, a distance management table 75, a group / job-related table 76, a subsequent group management table 77, a group display table 78, and a reduced display management table 79. To do.

The client 81 receives the job flow information to be displayed in the modified batch information and the job grouping information from the server 39. Then, the client 81 executes the display process 82 that groups the job flows and displays them on the screen.

FIG. 25 shows the job-related information table 71 in the present embodiment (example). The job-related information table 71 is a table that manages related information between jobs. The job-related information table 71 includes data items of "job number", "job name", and "successor job number".

A number that identifies a job is stored in the "job number". The job name corresponding to the job number is stored in the "job name". In the "subsequent job number", the job number of the job to be executed after the job indicated by the job number stored in the data item "job number" is stored.

FIG. 26 shows the job classification table 72 in the present embodiment (example). The job classification table 72 is a correspondence table between jobs and job classification information. The job classification table 72 includes data items of "job classification information" and "job number".

In the "job classification information", information on the type of job classification (for example, branch / base number) is stored. In the "job number", the job number corresponding to the information stored in the data item "job classification information" is stored.

FIG. 27 shows the job classification information temporary table 73 in the present embodiment. The job classification information temporary table 73 is a temporary table of job classification information. The job classification information temporary table 73 includes data items of "job number", "character string token", "scheduled start date information", and "job classification information".

The job number is stored in the "job number". A word (character string token) is stored in the "character string token". The scheduled start date of the job indicated by the job number is stored in the "scheduled start date information". In the "job classification information", information on the type of job classification (for example, branch / base number) is stored.

FIG. 28 shows the execution section management table 74 in the present embodiment (Example). The execution section management table 74 is a table that manages a group, a job in the group, a succeeding group, and an execution section. The execution section management table 74 includes data items of "group number", "job number", "job classification", "execution section", "subsequent group number", and "connection section".

The "group number" stores a number that identifies the group in which the job is grouped. Grouped job numbers are stored in the "job number". Job classification information is stored in the "job classification information". The section executed by the grouped jobs is stored in the "execution section". In the "subsequent group number", the subsequent group number in the execution section is stored. The connection information to the "subsequent group number" (connection destination) is stored in the "connection section".

FIG. 29 shows the distance management table 75 in the present embodiment (example). The distance management table 75 is a table that manages the distance from the first job of each job. The distance management table 75 includes data items of "job number" and "distance".

The job number is stored in the "job number". The "distance" stores the distance from the first job of each job.

FIG. 30 shows a group job-related table 76 in the present embodiment (example). Group job related table 76 is a table related to groups and jobs. The group / job-related table 76 includes data items of "group number", "job number", and "job classification information".

A group number that identifies a group is stored in the "group number". The job number is stored in the "job number". Job classification information is stored in the "job classification information".

FIG. 31 shows a subsequent group management table 77 in the present embodiment (Example). The successor group management table 77 is a relationship table of groups, jobs, and successor groups. The successor group management table 77 includes data items of "group number", "job number", "job classification information", and "successor group number".

The group number is stored in the "group number". The job number is stored in the "job number". Job classification information is stored in the "job classification information". The group number of the succeeding group is stored in the "successor group number".

FIG. 32 shows a group display table 78 in the present embodiment (Example). The group display table 78 holds the contents to be displayed as a group monitoring diagram (FIG. 16). The group display table 78 includes "job classification information", "group number", "execution section", "subsequent job classification information", "connection section", "display status", "status display position", and "deadline time". Includes data items for.

Job classification information is stored in the "job classification information". The group number is stored in the "group number". The execution section in the group monitoring diagram is stored in the "execution section". The job classification information of the succeeding job is stored in the "subsequent job classification information". In the "connection section", connection information from the job classification information to the succeeding job classification information is stored in the execution section. The display status (execution, abnormal termination, etc.) of the job classification information is stored in the "display status". In the "state display position", section information for displaying the "display state" is stored. The deadline time related to the job classification information is stored in the "deadline time".

FIG. 33 shows the reduced display management table 79 (when the three sections are reduced to one section) in the present embodiment (example). The reduced display management table 79 is a correspondence table of the relationships between groups before and after reduction. The reduced display management table 79 includes data items of "group", "successor group", "connection section before reduction", "connection section after reduction", "arrow ID after reduction", and "bidirectional determination flag".

The group number is stored in the "group". In the "successor group", the group number to be executed after the processing of the group is stored. In the "connection section before reduction", connection information from the group before reduction to the subsequent group is stored. In the "reduced connection section", the connection information from the reduced group to the succeeding group is stored. Information for identifying the reduced arrow is stored in the "reduced arrow ID". A flag for discriminating a bidirectional arrow (Yes: bidirectional arrow, No: one-way arrow) is stored in the "bidirectional determination flag".

FIG. 34 shows a reduced group display table (when three sections are reduced to one section) in the present embodiment (example). As the contents of the reduced group display table 80, the reduced contents of the group monitoring diagram displayed in the group display table 78 are stored. The reduced group display table 80 includes "job classification information", "group number", "execution section", "continuation job classification information", "connection classification", "display status", "status display position", and "deadline time". Includes data items.

FIG. 35 shows the overall flow of the grouped display process of the job flow in the present embodiment (Example). When a job grouping display request is received from the client 81, the display information creation unit 63 executes the following processing.

The display information creation unit 63 acquires related information between jobs (S21). Here, the display information creation unit 63 refers to each job information of the batch after aggregation, examines the dependency between jobs, clarifies the relationship, and stores it in the job-related information table 71.

The display information creation unit 63 extracts job classification information (S22). The details of S22 will be described with reference to FIG.

FIG. 36 shows the flow of the job classification information extraction process (S22) in the present embodiment (Example). At the time of virtualization aggregation or when the job classification table 72 is not created manually ("NO" in S22-1), the display information creation unit 63 extracts the job classification information by the following method and jobs. Create classification table 72.

As the grouping method setting, one of "branch / base information before aggregation", "job name", and "scheduled start date information" is specified by the user. The display information creation unit 63 extracts classification information by a method described later based on the designated information.

If grouping is specified in the branch / branch information before aggregation ("YES" in S22-2), and if the job / branch correspondence table 41 is created at the time of virtualization aggregation, the display information creation unit 63 performs the following processing (S22-3). That is, the display information creation unit 63 classifies the jobs based on the correspondence between the jobs in the job / branch correspondence table 41 and the branch / base numbers. Specifically, the display information creation unit 63 stores the correspondence between the job name and the job classification information in the job classification table 72, using the branch / base number as the job classification information based on the job / branch correspondence table 41.

If the job / branch correspondence table 41 does not exist, the display information creation unit 63 prompts the user to specify another grouping method described later.

When grouping by job name is specified ("NO" in S22-2, "NO" in S22-4, "job name" in S22-5), the display information creation unit 63 performs the following processing. Do (S22-6). That is, the display information creation unit 63 further asks the user to specify the "delimiter" and the "character string token position to be classified", and classifies the job according to the type of the character string token. Here, the display information creation unit 63 divides the job name according to the designated "delimiter". The display information creation unit 63 confirms the tokens of the delimited character string corresponding to the specified "position of the character string token".

That is, the job names of related systems and businesses are usually set according to specific rules. The display information creation unit 63 classifies jobs using the rules (for example, the job of the accounting system is often "accounting system_ ~ processing", and the order receiving system is "ordering system_ ~ processing". ).

For example, suppose there are jobs such as " system_start processing", " system_backup processing", and " system_order processing". In this case, if an underscore (_) is selected as the "delimiter" and the first token is selected as the "character string token position to be classified", the first token in the character string separated by the underscore is ". Jobs are classified by " system" and " system".

The display information creation unit 63 assigns the same job classification information to a job having the same token character string in the job name, and adds the correspondence between the job and the job classification information to the job classification table 72.

If there is no other job having the same token, the display information creation unit 63 allocates new job classification information. If there is another job having the same token, the display information creation unit 63 acquires the job classification information of that job.

The display information creation unit 63 stores the job name, the character string token, and the job classification information in the job classification information temporary table 73.

When grouping by the scheduled start date information is specified ("start date information" in S22-5), the display information creation unit 63 classifies the jobs according to the scheduled start date information set for the job (S22). -7). Here, the display information creation unit 63 confirms the job start date information. If there is no other job having the same start date information, the display information creation unit 63 allocates new job classification information. If there is another job having the same start date information, the display information creation unit 63 acquires the job classification information of that job. The display information creation unit 63 stores the job name, start date information, and job classification information in the job classification information temporary table.

Specifically, since the scheduled start date information is usually different for each job, the same scheduled start date information is set for the job corresponding to a certain job. The scheduled start date information of such a job is different from the scheduled start date information of the job corresponding to a different job.

For example, if job A is started on a weekday, job B is every Monday, and job C is every Monday, job B and job C have the same scheduled start date information, so the display information creation unit 63 has the same classification. Judge as a job of. In this case, the display information creation unit 63 assigns the same job classification information to the jobs having the same scheduled start date information, and adds the correspondence between the job and the job classification information to the job classification table 72.

The display information creation unit 63 stores the relationship between the job name and the job classification information in the job classification table 72 of the DB from the job classification information temporary table 73 (S22-8). Return to the description in Figure 35.

The display information creation unit 63 derives the relationship between the group and the job (S23). The display information creation unit 63 has a preceding / succeeding connection relationship based on the correspondence between the job flow connection relationship in the job-related information table 71 and the job classification information in the job classification table 72, and the range of jobs with the same classification information. Are grouped together. The processing of S23 will be described with reference to FIGS. 37 and 38.

37 and 38 show the flow of the derivation process (S23) of the relationship between the group and the job in the present embodiment (example). The display information creation unit 63 determines whether a certain job and the preceding job for that job have the same classification information. When a certain job and a preceding job for that job are jobs with the same classification information, the display information creation unit 63 assigns the same group number to those jobs (S23-3).

More specifically, the display information creation unit 63 determines whether a certain job (target job) and the preceding job for that job have the same classification information. When the target job and the preceding job for that job are jobs with the same classification information, the display information creation unit 63 confirms the group number assigned to the preceding job. If the preceding job has already been assigned a group number, the display information creation unit 63 sets the target job to the same group number as the preceding job. The display information creation unit 63 adds the correspondence between the target job and its predecessor job to the group job-related table 76.

If a plurality of preceding jobs have the same job classification information and have different group numbers, the display information creation unit 63 targets jobs belonging to a group other than the group number initially assigned to the target job. Replace with the group number assigned to the job.

Specifically, the display information creation unit 63 changes all the jobs belonging to the group corresponding to the preceding job in the group / job-related table 76 to the group number of the target job group, and the preceding job originally belongs to it. Delete the existing group from the group job related table 76.

Repeat the process of S23-3 until confirmation is completed for all preceding jobs ("NO" in S23-2).

Next, the display information creation unit 63 determines whether the target job and the succeeding job for the target job have the same classification information. When the target job and the succeeding job for the target job are jobs with the same classification information, the display information creation unit 63 assigns the same group number to the target job and the succeeding job.

Further, when there are a plurality of jobs having a preceding / succeeding relationship and different group numbers are assigned to each, the display information creation unit 63 combines the group numbers into one as the same group. The display information creation unit 63 stores the relationship between the job and the group number in the group / job-related table 76.

More specifically, in the case where the group number is assigned to the target job in the preceding job ("YES" in S23-5) and there is a succeeding job for the target job, the display information creation unit 63 Determine whether the job classification information of the target job and the succeeding job is the same.

When the target job and the succeeding job have the same job classification information, the display information creation unit 63 confirms the group number assigned to the succeeding job. The display information creation unit 63 assigns the group number of the target job to the succeeding jobs having the same job classification information to which the group number is not assigned.

Further, the display information creation unit 63 replaces the group number of the succeeding job to which the group number is assigned among the succeeding jobs having the same job classification information with the group number of the target job. Specifically, the display information creation unit 63 changes all the jobs belonging to the group corresponding to the succeeding job in the group job related table 76 to the group number of the group of the target job. Then, the display information creation unit 63 deletes the group to which the succeeding job originally belonged from the group job-related table 76 (S23-6).

In the preceding job, if the group number is not assigned to the target job ("NO" in S23-5) and there is a succeeding job for the target job, the display information creation unit 63 uses the target job and the succeeding job. Judge whether or not the job classification information of is the same.

When the target job and the succeeding job have the same job classification information, the display information creation unit 63 confirms the group number assigned to the succeeding job. If at least one of the succeeding jobs is assigned a group number, the display information creation unit 63 sets the target job to the same group number. The display information creation unit 63 adds the correspondence between the target job and the succeeding job to the group job-related table 76.

If multiple subsequent jobs have the same job classification information and each has a different group number, the display information creation unit 63 selects jobs belonging to groups other than the group number initially assigned to the target job as the target job. Replace with the group number assigned to. Specifically, the display information creation unit 63 changes all the jobs belonging to the group corresponding to the succeeding job in the group job related table 76 to the group number of the group of the target job. Then, the display information creation unit 63 deletes the group to which the succeeding job originally belonged from the group job-related table 76 (S23-7).

If all of the preceding job and the succeeding job have different job classification information, or when all of the preceding job and the succeeding job are unconfirmed and the group number is not assigned, the group number is not assigned to the own job. In that case, assign a new group number and add a correspondence to the group job related table 76.

Repeat the process of S23-6 or S27-7 until confirmation is completed for all subsequent jobs ("NO" in S23-4).

When the processing of S23-6 or S27-7 is completed for all the succeeding jobs, the display information creation unit 63 performs the following processing. If all of the preceding job and the succeeding job have different job classification information, or when all of the preceding job and the succeeding job are unconfirmed and the group number is not assigned, the group number is not assigned to the target job. In that case, the display information creation unit 63 newly assigns a group number and adds the correspondence between the target job and the preceding job / succeeding job to the group / job-related table 76. Return to the description in Figure 35.

The display information creation unit 63 derives the connection relationship between the groups (S24). The display information creation unit 63 obtains which group is the successor group of a certain group based on the connection relationship of the job flow in the job-related information table 71 and the group / job-related table 76. The display information creation unit 63 adds the connection relationship between the requested groups to the succeeding group management table 77. The processing of S24 will be described with reference to FIG. 39.

FIG. 39 shows the flow of the derivation process (S24) of the connection relationship between the groups in the present embodiment (Example). The display information creation unit 63 performs the following processing until the confirmation of all the groups in the group / job relation table 76 is completed (S24-1). That is, the display information creation unit 63 obtains the group information to which the succeeding job belongs for all the jobs in the group from the group / job relation table 76. The display information creation unit 63 adds the connection relationship from the target group to the group to which the succeeding job belongs to the succeeding group management table (S24-3).

If there is a connection relationship between the target groups or a connection relationship that already exists in the successor group management table, the display information creation unit 63 does not add to the successor group management table.

Repeat the process of S24-3 until confirmation is completed for all jobs ("NO" in S23-4). Return to the description in Figure 35.

The display information creation unit 63 derives the distance from the first job of each job (S25). The display information creation unit 63 obtains the distance from the first job to each job based on the connection relationship of the job flow in the job-related information table 71. The distance from the first job to each job is the number of arrows passed from the first job to each job.

If there are a plurality of leading jobs, or if the route in the middle is branched, there are a plurality of distances from the leading job to each job. In this case, the maximum distance is the distance to the job. The display information creation unit 63 stores the obtained distance information for each job in the distance management table 75. The processing of S25 will be described with reference to FIG. 40.

FIG. 40 shows the flow of the derivation process (S25) of the distance from the head job of each job in the present embodiment (example). The display information creation unit 63 searches for the first job (a job for which no preceding job exists) based on the connection relationship of the job flow in the job-related information table 71 (S25-1).

If the first job does not exist ("NO" in S25-2), this flow ends. If the first job exists ("YES" in S25-2), the display information creation unit 63 sets the distance of the first job to 0 and adds the distance of the first job to the distance management table 75 (S25-2).

The display information creation unit 63 recursively obtains the distance (= number of arrows) from the first job for all subsequent jobs and adds them to the distance management table 75.

If the distance from the first job is already set in the distance management table 75 (when there are multiple routes to reach that job), the display information creation unit 63 sets the current distance and the distance in the distance management table 75. Compare with. When the current distance value is larger than the distance value in the distance management table 75, the display information creation unit 63 updates the distance value in the distance management table 75 (S25-4). Return to the description in Figure 35.

The display information creation unit 63 derives the execution section and the connection section of the group (S26). The display information creation unit 63 obtains the execution section of the group and the connection section between the groups based on the succeeding group management table 77 and the distance management table 75. The execution section of a group is the section from the start of jobs in the group to the end of all jobs.

The display information creation unit 63 obtains the maximum distance and the minimum distance among the job distances in each group. The display information creation unit 63 stores the maximum distance from the minimum distance as the execution section of the group in the execution section management table 74.

The connection interval between groups is which interval is the connection from one group to another based on the distance of those jobs when the jobs in one group are related to the jobs in another group. It shows whether it is done in. The display information creation unit 63 sets the distance of the job in another related group from the distance of the job in the target group as the connection section between the groups, and adds it to the execution section management table 74. The processing of S26 will be described with reference to FIG. 40.

FIG. 41 shows the flow of the derivation process (S26) of the execution section and the connection section of the group in the present embodiment (Example). The display information creation unit 63 repeats the processes of S26-2 to S26-4 until the confirmation is completed for all the groups in the subsequent group management table 77.

The display information creation unit 63 refers to the succeeding group management table 77 and the distance management table 75, and obtains the minimum distance and the maximum distance for the jobs in the group. The display information creation unit 63 sets the maximum distance from the obtained minimum distance as the execution section of the group and adds it to the execution section management table 74 (S26-2).

The display information creation unit 63 performs the process of S26-4 until the confirmation is completed for all the jobs in the group.

The display information creation unit 63 searches for a succeeding job of the job in the group, and acquires the distance of the job from the distance management table 75. In addition, the display information creation unit 63 acquires the group to which the succeeding job belongs from the succeeding group management table 77. The display information creation unit 63 adds the distance from the job distance in the group to the succeeding job to the execution section management table 74 as the connection section from the target group to the succeeding group.

If the connection section is different even if the connection is made with the same succeeding group, the display information creation unit 63 sets the distance from the job in the group to the succeeding job as another connection section information. Add to management table 74.

On the other hand, when the same successor group has the same connection section or the connection from the target group to the target group, the display information creation unit 63 manages the distance from the job in the group to the succeeding job in the execution section. Do not add to table 74. Return to the description in Figure 35.

The display information creation unit 63 creates a group display table (S27). The display information creation unit 63 refers to the execution section management table 74, organizes the groups having the same job classification information so as to be displayed as one group, and adds them to the group display table 78.

When summarizing, if the execution sections of the groups overlap, the display information creation unit 63 updates the execution section information, and if the execution sections of the groups do not overlap, newly adds the execution section information.

The display information creation unit 63 refers to the execution section management table 74, and sets the display position of the arrow indicating the connection relationship between the groups to be displayed on the screen based on the connection section information before the group is grouped with respect to the group grouped above. Obtain and add to the group display table 78.

If there are multiple related arrows in the same connection section from one group to another in the group summarized above, the display information creation unit 63 displays as one arrow. , Combine the number of arrows on the table into one. If the sections are different, they are displayed as different arrows, so the number of arrows on the table is not summarized. The processing of S27 will be described with reference to FIG. 42.

FIG. 42 shows the flow of the group display table creation process (S27) in the present embodiment (Example). In the display information creation unit 63, for the group information of the same job classification information, the same execution section, the execution section is included in another execution section, and the execution sections overlap are on the group display table 78. Check if it exists in. If it exists on the group display table 78 and the execution section increases, the display information creation unit 63 updates the information on the group display table 78.

If there is no information on the group display table 78 or the execution sections do not overlap, the display information creation unit 63 newly adds the execution section information (S27-2).

The display information creation unit 63 performs the process of S27-2 until the confirmation of all the groups in the execution section management table 74 is completed.

When the confirmation for all the groups in the execution section management table 74 is completed ("YES" in S27-1, the display information creation unit 63 confirms all the groups in the execution section management table 74, S27-4 to S27- Check if the processing of 5 has been performed (S27-3). If the processing of S27-4 to S27-5 has not been performed for all the groups in the execution section management table 74 ("NO" in S27-3) , The display information creation unit 63 performs the following processing. That is, when the confirmation of all the connection section information in the group is completed ("YES" in S27-4), the display information creation unit 63 intergroups. The display position of the arrow representing the connection information is calculated. The start point of the display is the target group, and the end point is the subsequent group. The positions of the start point and the end point are determined by the connection section of the execution section management table 74. Display information creation unit 63 adds the position information of the start point and the end point to the corresponding group in the group display table 78 (S27-5). Return to the explanation of FIG. 35.

The display information creation unit 63 updates the execution status of the group on the group display table 78 (S28). The display information creation unit 63 refers to the execution section management table 74 and confirms the status of the jobs in the group. The display information creation unit 63 updates the group display table 78 with the status and distance of the job in the high display priority state as the display status and the display position of the status of the group. When there are a plurality of jobs having the same priority, the display information creation unit 63 sets the state / distance of the job having the shortest distance as the display state of the group and the display position of the state.

The display information creation unit 63 refers to the execution section management table 74, confirms the deadline time for jobs in the group in each section, and updates the group display table 78. If there are a plurality of different deadlines for a job in an execution section of one group, the display information creation unit 63 provides information on a plurality of deadlines for the execution section of one group. Is set in the group display table 78.

Further, for those whose jobs have already been completed normally or those whose jobs have been delayed, the display information creation unit 63 adds an attribute indicating completion or delay to the group display table 78. At the time of display, the display information creation unit 63 displays so that it can be seen that the job corresponding to the deadline time has been completed or delayed.

In addition, at the time of the second display etc., the processing speed will be increased by starting from S27. The processing of S28 will be described with reference to FIG. 43.

FIG. 43 shows the flow of the group execution status update process (S28) on the group display table in the present embodiment (example). The display information creation unit 63 performs the processes of S28-2 to S27-8 until the confirmation of all the groups in the execution section management table 74 is completed (S28-1).

Until the confirmation is completed for all the jobs in the group (S28-2), the display information creation unit 63 performs the processes of S28-2 to S27-8.

The display information creation unit 63 acquires the state of the "display state" stored in the group display table 78 (S28-3).

The display information creation unit 63 determines whether or not the display priority of the status of the jobs in the group is equal to or higher than the display priority of the status on the group display table 78 (S28-4). When the display priority of the status of jobs in the group is equal to or higher than the display priority of the status on the group display table 78 ("YES" in S28-4), the display information creation unit 63 processes S28-5. Do.

When the display priority of the status of jobs in the group is the same as the display status on the group display table 78, the display information creation unit 63 sets the distance of the "display status" on the group display table 78. , Compare the distance of the current job. Here, the display information creation unit 63 acquires information about the current job from the job execution unit 62. If the current job is shorter than the distance of the "display state" on the group display table 78, the display information creation unit 63 sets the distance of the "display state" on the group display table 78 to the distance of the current job. Update with (S28-5).

When the display priority of the status of jobs in the group is lower than the display priority of the status on the group display table 78 ("NO" in S28-4), the display information creation unit 63 performs the process of S28-6. ..

The display information creation unit 63 updates the "display state" stored in the group display table 78 with the current job state and distance (S28-6). The display information creation unit 63 performs the process of S28-6 even when the "display state" of the group display table 78 is empty.

When the deadline time is set for the job to be confirmed, the display information creation unit 63 adds the deadline time to the group display table 78. In addition, the display information creation unit 63 adds a "completion flag" to the deadline time of the group display table 78 when the job is completed normally. If the job is delayed with respect to the deadline, the display information creation unit 63 adds a "delay flag" to the deadline time of the group display table 78 (S28-7). Return to the description in Figure 35.

The display information creation unit 63 creates data for reduced display of the group (S29). The processing of S29 will be described with reference to FIGS. 44 and 45.

FIGS. 44 and 45 show the flow of the group reduction display data creation process (S98) in the present embodiment (Example). When the reduction degree of the screen display is specified at the time of job grouping display request ("YES" in S29-1), the display information creation unit 63 combines the specified reduction degree into a new section. Find the number I (S29-2). After that, the process proceeds to S29-5.

When the reduction degree of the screen display is not specified at the time of job grouping display request ("NO" in S29-1), the display information creation unit 63 acquires the current screen size. In addition, the display information creation unit 63 calculates the screen size required when displaying without reduction (obtained from the maximum section of the group and the display size per section) (S29-3).

The display information creation unit 63 obtains the degree of reduction required to fit within one screen from the current screen size and the screen size required without reduction. Further, the display information creation unit 63 obtains the number of sections I to be newly combined as one section from this reduction degree (S29-4).

If the number of sections I to be combined is 1 or less, this flow ends ("NO" in S29-5). If the number of sections I to be combined is greater than 1 ("YES" in S29-5), proceed to the process of S29-6.

The display information creation unit 63 performs the process of S29-7 until the confirmation of the display arrows of all the groups in the group display table is completed (S29-6).

Based on the number of sections I to be summarized, the display information creation unit 63 finds the correspondence relationship of which section the arrow before reduction is displayed in after reduction, and adds it to the reduction display management table 79 (S29-7).

In S29-7, the correspondence between the sections before and after reduction is the current section divided by the section I to be combined and rounded down to the nearest whole number (for example, when the section I to be combined is 3, the value before reduction is 0 ~. After the reduction of the section that is 2, it becomes section 0, and after the reduction of the section that is 3 to 5 before reduction, it becomes section 1). Arrows in the same section that have relationships between the same groups are combined into one. Also, if there are arrows in the same section in the opposite direction, they are combined into one double-headed arrow on the display.

After confirming the display arrows of all the groups in the group display table ("YES" in S29-6), the display information creation unit 63 copies the group display table 78 and reduces the group display table 80. Create (S29-8).

The display information creation unit 63 updates the execution section of each group in the group display table 80 after reduction and the display position of the group status based on the number of sections I to be collected (S29-9).

The display information creation unit 63 also updates the display position of the group state of the group display table 80 after reduction with a new section summarized by the number of sections I (S29-10).

In addition, the display information creation unit 63 updates the display arrow of the reduced group display table 80 based on the reduced display management table 79 (S29-11).

The display information creation unit 63 updates the deadline time of the group display table 80 after reduction based on the reduced display management table 79 (S29-12). Return to the description in Figure 35.

The display information creation unit 63 transmits the display information for grouping the job flow to the client 81 (S30). The display information creation unit 63 transmits the information of the job flow to be displayed and the reduced group display table 80 to the client 81 among the batch information after aggregation.

The display process 82 of the client 81 groups and displays the job flows based on the information of the job flow to be displayed sent from the server 39 and the reduced group display table 80 (S31). As a result, on the client 81 side, the job flow information (group monitoring diagram) grouped on the screen of the client 81 based on the job flow information and the reduced group display table 80 is displayed in the Gantt chart format. Is displayed. That is, as described with reference to FIGS. 16 and 17, in the group monitoring chart, the vertical axis shows the grouped attribute information, the horizontal axis shows the time, and the bar showing the job execution period is divided at predetermined time intervals. It is displayed in Gantt chart format.

The job flow in a certain job classification group can be drilled down and displayed. In that case, the job flow in a certain group and the jobs before and after it are displayed. For example, when the group B of the section 3 is selected in FIG. 16, the group list 91 of the job classification information B in the section 3 is displayed as shown in FIG.

In the group list 91 of FIG. 46, the status of the group is displayed, and the group name and status can be sorted. When any group is selected in the group 91 list, that group and the jobs before and after it are displayed.

FIG. 47 shows a screen displayed when GrpB-4 is selected in the group list in the present embodiment (Example). On screen 101, the job flow of GrpB-4 and the jobs before and after it are displayed, and the job status is also displayed. The groups displayed in the group list 91 are displayed in tab 102. By switching tab 102, you can display the job flow in another group.

FIG. 48 shows the flow of the display processing of the client in the present embodiment (Example). The client 81 sends the job classification information and section information selected on the screen to the server 39 (S41).

The client 81 receives the group list 91 belonging to the selected section of the corresponding job classification information from the server 39 (S42). The client 81 displays the group list 91 on the screen showing the status corresponding to the group (S43).

The client 81 determines whether or not a group has been selected from the group list 91 on the screen (S44). If no group is selected in the group list 91 on the screen ("NO" in S44) and the screen is not closed ("NO" in S45), the client 81 processes S43. If no group is selected in the group list 91 on the screen ("NO" in S44) and the screen is closed ("YES" in S45), the client 81 ends this flow.

When a group is selected in the group list 91 on the screen ("YES" in S44), the client 81 sends the information of the group to be drilled down to the server 39 (S46).

The client 81 receives the jobs included in the corresponding group and the job information before and after the jobs from the server 39, and displays them on the screen 101 (S47).

If tab 102 of another group is selected ("YES" in S48), client 81 processes S46.

If tab 102 of another group is not selected ("NO" in S48) and screen 101 is not closed ("NO" in S49), client 81 processes S47. If tab 102 of another group is not selected ("NO" in S48) and screen 101 is closed ("YES" in S49), client 81 processes S43.

FIG. 49 is an example of a block diagram of a hardware environment of a computer that executes a program according to the present embodiment (Example). The computer 110 functions as a server 39, a client 81, and the like. The computer 110 is composed of a CPU 112, a ROM 113, a RAM 116, a communication I / F 114, a storage device 117, an output I / F 111, an input I / F 115, a reading device 118, a bus 119, an output device 121, and an input device 122.

Here, the CPU indicates a central processing unit. ROM indicates read-only memory. RAM indicates random access memory. I / F indicates an interface. A CPU 112, a ROM 113, a RAM 116, a communication I / F 114, a storage device 117, an output I / F 111, an input I / F 115, and a reading device 118 are connected to the bus 119. The reading device 118 is a device that reads a portable recording medium. The output device 121 is connected to the output I / F 111. The input device 122 is connected to the input I / F 115.

As the storage device 117, various types of storage devices such as a hard disk, a flash memory, and a magnetic disk can be used. The storage device 117 or ROM 113 stores a program according to the present embodiment in which the CPU 112 functions as the response unit 3. Information is temporarily stored in RAM116. When the computer 110 is the server 39, the RAM 116 functions as the memory 67 and temporarily holds various tables. When the computer 110 is the client 81, the RAM 116 stores the job flow grouping display information received from the server 39.

The CPU 112 reads the program according to the present embodiment from the storage device 117 or the ROM 113 as the control unit 22, and executes the program. Specifically, the CPU 112 executes the migration tool 33 and the registration tool 37. Further, the CPU 112 executes the scheduler 61, and further functions as a job execution unit 62 and a display information creation unit.

The program that realizes the processing described in the above embodiment may be stored in the storage device 117, for example, from the program provider side via the communication network 120 and the communication I / F 114. Further, the program that realizes the processing described in the above embodiment may be stored in a commercially available and distributed portable storage medium. In this case, the portable storage medium may be set in the reading device 118, and the program may be read and executed by the CPU 112. As the portable storage medium, various types of storage media such as CD-ROMs, flexible disks, optical disks, magneto-optical disks, IC cards, and USB memory devices can be used. The program stored in such a storage medium is read by the reading device 118.

Further, as the input device 122, a keyboard, a mouse, an electronic camera, a webcam, a microphone, a scanner, a sensor, a tablet and the like can be used. Further, a display, a printer, a speaker, or the like can be used as the output device 121. Further, the network 120 may be a communication network such as the Internet, LAN, WAN, leased line, wired, and wireless.

The present invention is not limited to the embodiments described above, and various configurations or embodiments can be taken without departing from the gist of the present invention.

1 Management support device 2 Classification information generation unit 3 Grouping unit 4 Display information generation unit 11 Data center 12 Computer 13 Pre-correction batch 14 Post-correction batch 15 Relationship information between jobs 16 Job classification information 17 Information processing system 18 Branch 31 Jobs Setting replacement information 32 Pre-migration batch information 33 Migration tool 34 Batch conversion processing 35 Extract processing 36 Post-migration batch information 37 Registration tool 38 Batch registration processing 39 Server 40 Definition information DB 41 Job / branch correspondence table 42 Operation batch information 61 Scheduler 62 Job Execution unit 63 Display information creation unit 64 Judgment processing 65 Extraction processing 66 Display information creation processing 67 Memory 71 Job-related information table 72 Job classification table 73 Job classification information Temporary table 74 Execution section management table 75 Distance management table 76 Group / job related table 77 Subsequent group management table 78 Group display table 79 Reduced display management table 80 Reduced group display table 81 Client 82 Display processing