JP2018116518A - Job monitoring program, job monitoring device, and job monitoring method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a job monitoring program, a job monitoring device, and a job monitoring method capable of preventing occurrence of delay in output of a screen on which a job status is reflected.SOLUTION: Schedule information of a job to be executed is acquired from each of a plurality of job schedulers that perform schedule management of the job, a target job to be executed during a specific period is specified based on the acquired schedule information, the scheduler that performs the management of the specified target job is requested for information related to a status of the specified target job, and a screen indicating the status of the target job to be executed during the specific time is generated from the information related to the status of the target job acquired in accordance with the request.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a job monitoring program, a job monitoring apparatus, and a job monitoring method.

  For example, a business provider (hereinafter simply referred to as a business operator) that provides a service to a user constructs and operates a business system (hereinafter also referred to as an information processing system) for providing the service.

  In this case, a business system operator (hereinafter also simply referred to as an operator), for example, a monitoring device that monitors the operating status of jobs or job nets (hereinafter collectively referred to as jobs) that constitute the business system. Confirm the screen output by. Thereby, the operator of the business system can check the operation status of each job. Therefore, when an abnormality occurs in the business system, the operator can quickly detect the abnormality (see, for example, Patent Documents 1 to 3).

JP 2011-150442 A JP 2002-157134 A JP 2001-350636 A

  In the business system as described above, each business system constructed in each of a plurality of data centers is aggregated according to the usage status of the service by the user. In this case, for example, the operator also aggregates monitoring devices that monitor the business system to be aggregated. As a result, the operator can reduce the number of monitoring devices to be operated, and can reduce the work load required for monitoring each business system.

  However, when business systems are aggregated as described above, the number of jobs that each monitoring apparatus needs to monitor increases. Therefore, in this case, in the monitoring apparatus, it takes a long time to acquire information indicating the operation status of each job (hereinafter also referred to as status information), and there is a possibility that the output of the screen monitored by the operator may be delayed. .

  In view of this, an object of one aspect is to provide a job monitoring program, a job monitoring apparatus, and a job monitoring method that can prevent a delay in output of a screen reflecting a job state.

  According to one aspect of the embodiment, job schedule information is acquired from each of a plurality of job schedulers that perform schedule management of jobs to be executed, and executed within a specific period based on the acquired schedule information Information regarding the status of the specified target job is requested to the job scheduler that manages the specified target job, and the information regarding the status of the target job acquired in response to the request is requested. , Causing the computer to execute a process of generating a screen showing the state of the target job executed within the specific time.

  According to one aspect, it is possible to prevent a delay in the output of the screen reflecting the job status.

FIG. 1 is a diagram illustrating an overall configuration of the information processing system 10. FIG. 2 is a diagram illustrating the hardware configuration of the monitoring device 1. FIG. 3 is a diagram for explaining the hardware configuration of the management apparatus 2. FIG. 4 is a functional block diagram of the monitoring device 1. FIG. 5 is a functional block diagram of the management apparatus 2. FIG. 6 is a flowchart for explaining the outline of job monitoring processing in the first embodiment. FIG. 7 is a diagram for explaining the outline of the job monitoring process in the first embodiment. FIG. 8 is a diagram for explaining the outline of the job monitoring process in the first embodiment. FIG. 9 is a diagram for explaining the outline of job monitoring processing in the first embodiment. FIG. 10 is a flowchart for explaining the details of the job monitoring process in the first embodiment. FIG. 11 is a flowchart for explaining the details of the job monitoring process in the first embodiment. FIG. 12 is a flowchart for explaining the details of the job monitoring process in the first embodiment. FIG. 13 is a flowchart illustrating the details of the job monitoring process according to the first embodiment. FIG. 14 is a flowchart illustrating details of the job monitoring process according to the first embodiment. FIG. 15 is a diagram for explaining a specific example of the schedule information 131. FIG. 16 is a diagram for explaining the details of the job monitoring process in the first embodiment. FIG. 17 is a diagram illustrating a specific example of the time zone information 133. FIG. 18 is a diagram for explaining the details of the job monitoring process in the first embodiment. FIG. 19 is a diagram for explaining a specific example of the state information 132. FIG. 20 is a diagram illustrating a specific example of the monitoring screen. FIG. 21 is a diagram illustrating a specific example in which the job monitoring process is performed again after the monitoring screen illustrated in FIG. 20 is output. FIG. 22 is a diagram illustrating a specific example in which the job monitoring process is performed again after the monitoring screen illustrated in FIG. 20 is output. FIG. 23 is a diagram illustrating a specific example in which job monitoring processing is performed again after the monitoring screen illustrated in FIG. 20 is output. FIG. 24 is a diagram illustrating a specific example in which job monitoring processing is performed again after the monitoring screen illustrated in FIG. 20 is output. FIG. 25 is a flowchart illustrating job monitoring processing according to the second embodiment.

[Configuration of information processing system]
FIG. 1 is a diagram illustrating an overall configuration of the information processing system 10. An information processing system 10 illustrated in FIG. 1 is a business system for providing a service to a user, for example.

  An information processing system 10 illustrated in FIG. 1 includes job execution devices 3a, 3b, and 3c (hereinafter collectively referred to as job execution device 3) that execute jobs for providing services to users. Each job execution apparatus 3 is distributed and arranged in a plurality of data centers (not shown), for example.

  Further, the information processing system 10 shown in FIG. 1 includes job schedulers JS2a, JS2b, and JS2c (hereinafter collectively referred to as job scheduler JS2) that perform schedule management of each job executed in the job execution apparatuses 3a, 3b, and 3c. Management devices 2a, 2b, and 2c (hereinafter collectively referred to as management device 2). The schedule management performed by each job scheduler JS2 includes, for example, execution of each job at a predetermined time.

  Further, the information processing system 10 shown in FIG. 1 acquires status information of each job executed in the job execution device 3 from the management device 2, and generates a screen (hereinafter also referred to as a monitoring screen) indicating the status of each job. The monitoring apparatus 1 (hereinafter also referred to as the job monitoring apparatus 1) on which the job scheduler JS1 that operates is operated. Specifically, the job scheduler JS1 polls each job scheduler JS2, for example, and acquires status information of each job. Then, a monitoring screen is generated by collecting the acquired state information.

  The monitoring device 1, the management device 2, and the job execution device 3 are each configured by one or more physical machines, for example. Each physical machine has a CPU (Central Computing Unit), a memory (DRAM: Dynamic Random Access Memory), and a large-capacity memory such as a hard disk (HDD: Hard Disk Drive). In addition, the monitoring device 1, the management device 2, and the job execution device 3 may be configured by virtual machines (not shown) generated on physical machines, for example.

  In the information processing system 10 as described above, job execution devices deployed in a plurality of data centers may be aggregated depending on the usage status of services by users. In this case, for example, the operator also performs aggregation of monitoring apparatuses that monitor the job execution apparatuses to be aggregated. Specifically, for example, when other jobs executed by other job execution apparatuses (not shown) other than the job execution apparatus 3 are collected in the job execution apparatus 3a, the operator monitors other jobs. The monitoring device to be performed is changed from a monitoring device (not shown) other than the monitoring device 1 to the monitoring device 1. As a result, the operator can reduce the number of monitoring devices to be operated, and can reduce the work load required for monitoring the operating state of each job.

  However, when job execution devices are aggregated as described above, the number of jobs that the monitoring device 1 needs to monitor increases. Therefore, in this case, in the monitoring device 1, the time required for acquiring the status information of each job becomes long, and there is a possibility that the output of the monitoring screen monitored by the operator is delayed.

  Therefore, the monitoring apparatus 1 according to the present embodiment acquires job schedule information from each of a plurality of job schedulers JS2 that perform schedule management of jobs to be executed. And the monitoring apparatus 1 specifies the job (henceforth a target job) performed within a specific period based on the acquired schedule information.

  Thereafter, the monitoring device 1 requests the job scheduler JS2 that manages the specified job for the status information of the specified target job, and from the status information of the target job acquired in response to the request within a specific time. Generate a monitoring screen that shows the status of the target job to be executed.

  That is, the monitoring apparatus 1 in the present embodiment refers to the schedule information acquired from the job scheduler JS2, thereby limiting the jobs for acquiring the status information to only jobs that are executed within a specific period.

  Thereby, the monitoring device 1 can reduce the processing load required for generating the monitoring screen. Therefore, the monitoring apparatus 1 can output a screen reflecting the actual job state at the requested time.

[Hardware configuration of monitoring device and management device]
Next, the hardware configuration of the monitoring device 1 and the management device 2 will be described. FIG. 2 is a diagram illustrating the hardware configuration of the monitoring device 1. FIG. 3 is a diagram illustrating the hardware configuration of the management apparatus 2.

  The monitoring apparatus 1 includes a CPU 101 that is a processor, a memory 102, an external interface (I / O unit) 103, and a storage medium (storage) 104. Each unit is connected to each other via a bus 105.

  The storage medium 104 stores, in a program storage area (not shown) in the storage medium 104, a program 110 for performing processing for monitoring a job executed by the job execution apparatus 3 (hereinafter also referred to as job monitoring processing). To do.

  As illustrated in FIG. 2, the CPU 101 loads the program 110 from the storage medium 104 to the memory 102 when executing the program 110, and performs job monitoring processing in cooperation with the program 110.

  The storage medium 104 includes, for example, an information storage area 130 (hereinafter also referred to as a storage unit 130) that stores information used when performing job monitoring processing. The external interface 103 communicates with the management device 2.

  The management device 2 also includes a CPU 201 that is a processor, a memory 202, an external interface (I / O unit) 203, and a storage medium (storage) 204. Each unit is connected to each other via a bus 205.

  The storage medium 204 stores a program 210 for performing job monitoring processing in a program storage area (not shown) in the storage medium 204.

  As shown in FIG. 3, when executing the program 210, the CPU 201 loads the program 210 from the storage medium 204 to the memory 202 and performs job monitoring processing in cooperation with the program 210.

  The storage medium 204 includes, for example, an information storage area 230 (hereinafter also referred to as a storage unit 230) that stores information used when performing job monitoring processing. The external interface 203 communicates with the monitoring device 1.

[Software configuration of information processing system]
Next, the software configuration of the information processing system 10 will be described. FIG. 4 is a functional block diagram of the monitoring device 1. FIG. 5 is a functional block diagram of the management apparatus 2.

  As shown in FIG. 4, the CPU 101 cooperates with the program 110 to obtain a schedule acquisition unit 111, a target job identification unit 112, a timing determination unit 113, a request transmission unit 114, and a state information reception unit 115. Operate. Further, as illustrated in FIG. 4, the CPU 101 operates as a screen generation unit 116 and a screen output unit 117 by cooperating with the program 110. Further, as shown in FIG. 3, schedule information 131, status information 132, and time zone information 133 are stored in the information storage area 130.

  The schedule acquisition unit 111, the target job identification unit 112, the timing determination unit 113, the request transmission unit 114, the status information reception unit 115, the screen generation unit 116, and the screen output unit 117 may each be a function of the job scheduler JS1. .

  The schedule acquisition unit 111 acquires schedule information 131 from each of a plurality of job schedulers JS2 that perform schedule management of jobs to be executed. The schedule information 131 is information including an execution schedule of a job for which each job scheduler JS2 performs schedule management. Specifically, the schedule acquisition unit 111 accesses the information storage area 230 of the management device 2 and acquires the schedule information 131. A specific example of the schedule information 131 will be described later.

  The target job specifying unit 112 specifies a target job to be executed within a specific period based on the schedule information 131 acquired by the schedule acquisition unit 111.

  The timing determination unit 113 determines the timing for requesting the status information 132 of the target job. The status information 132 is information indicating the operating status of each job executed in the job execution apparatus 3. A specific example of the status information 132 will be described later.

  Specifically, the timing determination unit 113 refers to the time zone information 133 stored in the information storage area 130 and determines the timing for requesting the status information 132 of the target job. The time zone information 133 is information for each time zone indicating the time required to acquire the job status information 132. A specific example of the time zone information 133 will be described later.

  The request transmission unit 114 requests the status information 132 of the target job from each of the job schedulers JS2 that manages the target job specified by the target job specifying unit 112. Specifically, the request transmission unit 114 transmits a transmission request for the status information 132 of the target job at the timing determined by the timing determination unit 113.

  The status information receiving unit 115 receives the status information 132 transmitted from each job scheduler JS2.

  The screen generation unit 116 generates a monitoring screen including the operation status of the target job executed within a specific time from the target job status information 132 acquired by the status information reception unit 115, and the screen output unit 117 For example, the monitoring screen generated by the screen generation unit 116 is output to a monitoring terminal (not shown) that can be confirmed by the operator.

  Further, as shown in FIG. 5, the CPU 201 operates as a schedule generation unit 211, a request reception unit 212, a state information generation unit 213, and a state information transmission unit 214 by cooperating with the program 210. Further, as shown in FIG. 5, schedule information 131 and status information 132 are stored in the information storage area 130.

  The schedule generation unit 211 generates schedule information 131 in response to, for example, an operator inputting an execution schedule for each job to the management apparatus 2. Then, the schedule generation unit 211 stores the generated schedule information 131 in the information storage area 230.

  The request receiving unit 212 receives a transmission request for the state information 132 transmitted by the monitoring device 1. Then, the state information generation unit 213 generates the state information 132 in response to the request reception unit 212 receiving a transmission request for the state information 132. Then, the state information generation unit 213 stores the generated state information 132 in the information storage area 230.

  For example, the management device 2 accesses each job execution device 3 and acquires information indicating an operation state of each job for which schedule management is performed at a regular timing. Then, the status information generation unit 213 generates status information 132 from the information indicating the operation status of each acquired job.

  The state information transmission unit 214 transmits the state information 132 generated by the state information generation unit 213 to the monitoring device 1.

[Outline of First Embodiment]
Next, an outline of the first embodiment will be described. FIG. 6 is a flowchart for explaining the outline of job monitoring processing in the first embodiment. 7 to 9 are diagrams for explaining the outline of the job monitoring process according to the first embodiment. The job monitoring process shown in FIG. 6 will be described with reference to FIGS.

  As shown in FIG. 6, the monitoring device 1 waits until the information acquisition timing (NO in S1). The information acquisition timing is, for example, the timing immediately after the monitoring screen is output (generated). That is, for example, the monitoring device 1 starts preparation for outputting the next monitoring screen in response to the completion of the output of the monitoring screen.

  When the information acquisition timing is reached (YES in S1), the monitoring apparatus 1 obtains the schedule information 131 for each job from each of a plurality of job schedulers JS2 that perform schedule management for each job, as shown in FIG. Obtain (S2).

  Subsequently, the monitoring apparatus 1 specifies a target job to be executed within a specific period based on the schedule information 131 acquired in the process of S2 (S3). The specific period is, for example, a period from the time when the next monitoring screen is output to the time when the next monitoring screen is output. Therefore, in the process of S3, for example, the monitoring device 1 specifies a job to be executed as a target job from the next time when the monitoring screen is output until the next time when the next monitoring screen is output.

  Further, as shown in FIG. 8, the monitoring apparatus 1 requests the status information 132 of the specified target job from the job scheduler JS2 that manages the target job specified in the process of S3 (S4). And it waits until it receives the requested state information 132 (NO in S5).

  Thereafter, when the requested status information 132 is received (YES in S5), the monitoring apparatus 1 is executed within a specific time from the status information 132 of the target job acquired in the processing of S5 as shown in FIG. A screen showing the status of the target job is generated (S6).

  That is, the monitoring apparatus 1 according to the present embodiment refers to the schedule information 131 acquired from the job scheduler JS2, thereby limiting the jobs for acquiring the status information 132 to only jobs that are executed within a specific period.

  As a result, the monitoring apparatus 1 can reduce the processing load required for screen generation. Therefore, the monitoring device 1 can output a monitoring screen reflecting the actual job status at the requested time.

[Details of First Embodiment]
Next, details of the first embodiment will be described. 10 to 14 are flowcharts illustrating details of the job monitoring process according to the first embodiment. FIGS. 15 to 24 are diagrams for explaining the details of the job monitoring process in the first embodiment. The job monitoring process shown in FIGS. 10 to 14 will be described with reference to FIGS.

[Schedule generation process]
First, a process in which the management apparatus 2 generates the schedule information 131 (hereinafter also referred to as a schedule generation process) will be described.

  As shown in FIG. 10, the schedule generation unit 211 of the management device 2 waits until the schedule generation timing (NO in S101). The schedule generation timing may be, for example, a timing at which the operator inputs an execution schedule for each job to the management apparatus 2.

  When the schedule generation timing comes (YES in S101), the schedule generation unit 211 generates schedule information 131 including the schedule of each job executed in the managed job execution apparatus 3 (S102). Hereinafter, a specific example of the schedule information 131 will be described.

[Specific examples of schedule information]
FIG. 15 is a diagram for explaining a specific example of the schedule information 131. FIG. 15A illustrates a specific example of the schedule information 131a acquired from the job scheduler JS2a, and FIG. 15B illustrates a specific example of the schedule information 131b acquired from the job scheduler JS2b. FIG. 15C is a diagram for describing a specific example of the schedule information 131c acquired from the job scheduler JS2c.

  The schedule information 131 illustrated in FIG. 15 includes an “item number” that identifies each piece of information included in the schedule information 131, an “identification ID” that identifies each job scheduler JS2, and a “job” that identifies each job (job net). "ID" as an item. The schedule information 131 shown in FIG. 15 includes “scheduled start time” indicating the scheduled start time of execution of each job, “scheduled end time” indicating the scheduled end time of execution of each job, and execution start conditions of each job. The “start condition” shown is an item.

  Specifically, in the schedule information 131a shown in FIG. 15A, “JS2a” is set as the “identification ID” and “NET #” is set as the “job ID” in the information whose “item number” is “1”. 2 ”is set, and“ 08:05 ”is set as“ scheduled start time ”. In the schedule information 131a shown in FIG. 15A, “08:15” is set as “scheduled end time” and “NET” is set as “start condition” in the information whose “item number” is “1”. “End of # 1” is set. That is, the schedule information 131a shown in FIG. 15A indicates that NET # 2 starts execution at 8: 5 on the condition that the execution of NET # 1 ends.

  Further, in the schedule information 131a shown in FIG. 15A, “JS2a” is set as the “identification ID” and “NET # 3” is set as the “job ID” in the information whose “item number” is “2”. Is set, and “08:00” is set as the “scheduled start time”. In the schedule information 131a shown in FIG. 15A, “08:30” is set as “scheduled end time” and “none” is set as “start condition” in the information whose “item number” is “2”. "Is set. That is, the schedule information 131a shown in FIG. 15A indicates that NET # 3 starts execution at 8:00 regardless of the execution status of other jobs. Description of other information included in FIG. 15 is omitted.

  Returning to FIG. 10, the schedule generation unit 211 stores the schedule information 131 generated in the process of S <b> 102 in the information storage area 130 (S <b> 103). Thereafter, the schedule generation unit 211 waits until the next schedule generation timing (NO in S101).

[Details of job monitoring processing]
Next, details of the job management apparatus performed by the monitoring apparatus 1 will be described. The schedule acquisition unit 111 of the monitoring device 1 waits until the information acquisition timing (NO in S11). Hereinafter, it is assumed that the information acquisition timing is the timing immediately after the output of the monitoring screen is performed at 7:50.

  When it is time to acquire information (YES in S11), the schedule acquisition unit 111 of the monitoring apparatus 1 acquires job schedule information 131 from each of a plurality of job schedulers JS2 that perform schedule management of jobs to be executed. (S12).

  Specifically, the monitoring device 1 (job scheduler JS1) obtains the schedule information 131 shown in FIG. 15, for example, and as shown by the arrows in FIG. 16, the NET regardless of the execution status of other jobs. Information indicating that execution of # 1 and NET # 3 is started can be acquired. In this case, as shown by the arrow in FIG. 16, the monitoring apparatus 1 starts execution of NET # 2 on the condition that execution of NET # 1 ends, and NET # 2 on the condition that execution of NET # 2 ends. It is possible to acquire information indicating that the execution of 4 is started. Furthermore, in this case, as indicated by the arrows in FIG. 16, the monitoring apparatus 1 can acquire information indicating that the execution of NET # 5 is started on the condition that the execution of NET # 2 and NET # 3 is ended. become.

  Further, in the process of S12, the schedule acquisition unit 111 acquires information indicating a job for which a manual operation has been performed from each of the plurality of job schedulers JS2.

  Specifically, for example, the schedule acquisition unit 111 refers to a log (not shown) related to each job stored in a plurality of job schedulers JS2, and outputs a monitoring screen immediately before a predetermined time (for example, immediately before). It is determined whether or not there is a job in which a log (hereinafter also referred to as an operation log) that is output when a manual operation is performed from the time point to the present. If the schedule acquisition unit 111 determines that there is a job for which an operation log has been generated, the schedule acquisition unit 111 acquires information indicating the job determined to exist as information indicating a job for which a manual operation has been performed.

  As a result, the target job specifying unit 112 can determine whether there is a job that has been manually operated, as will be described later.

  Thereafter, the target job specifying unit 112 of the monitoring device 1 refers to the schedule information 131 acquired in the process of S12, and specifies a job scheduled to be executed within a specific period as a target job (S13).

  Specifically, in the schedule information 131 shown in FIG. 15, information in which the time set for “scheduled start time” is between “08: 00” and “08: 10” is “item number” is “1”. ”,“ 2 ”, and“ 3 ”. Therefore, for example, when the specific period in the process of S13 is from 8 o'clock to 8:10, the target job specifying unit 112 has information “1” to “3” set in “item number”. “NET # 1”, “NET # 2”, and “NET # 3”, which are information set in the “job ID”.

  That is, the target job specifying unit 112 specifies only jobs to be executed in the near future in the process of S13. Specifically, the target job specifying unit 112 executes a job scheduled to be executed from the next time when the monitoring screen is output until the next time when the monitoring screen is output (the information is displayed on the monitoring screen where the next output is performed). Only jobs that need to be included. Therefore, in this case, the target job specifying unit 112 does not specify a job that is not scheduled to be executed between the next time when the monitoring screen is output and the next time when the monitoring screen is output.

  As a result, the monitoring device 1 can suppress the processing load required for generating the monitoring screen, as will be described later.

  Then, the target job specifying unit 112 determines whether or not there is a job that has not ended normally among jobs that have started execution in the past (S14).

  As a result, when it is determined that there is a job that has not ended normally (YES in S14), the target job specifying unit 112 determines that the job exists in S14 in addition to the target job specified in S13. Are identified as target jobs (S15). On the other hand, if it is determined that there is no job that has not ended normally (NO in S14), the target job identification unit 112 does not perform the process in S15.

  As a result, the monitoring device 1 can identify jobs that need to be continuously monitored by the operator from among jobs that have started execution in the past.

  Further, the target job specifying unit 112 determines whether there is a job for which a manual operation has been performed (S16). Specifically, the target job specifying unit 112 determines whether information indicating a job for which a manual operation has been performed has been acquired in the process of S12, for example.

  As a result, when it is determined that there is a job that has been manually operated (YES in S16), the target job specifying unit 112 exists in the process of S16 in addition to the target job specified in the processes of S13 and S15. Is determined as a target job (S17). Specifically, the target job specifying unit 112 specifies a job corresponding to the acquired information as a target job, for example, when information indicating a job for which a manual operation has been performed in the process of S12 is acquired. . On the other hand, when it is determined that there is no job that has been manually operated (NO in S16), the target job specifying unit 112 does not perform the process in S17.

  That is, even if the job is not scheduled to be executed within a specific period in the schedule information 131, there may be a job that is manually executed within the specific period. Therefore, the target job specifying unit 112 determines whether or not there is a job that has been manually operated in the process of S16. If it is determined that there is a job that has been manually operated, the job that existed in the process of S16 is identified as the target job in addition to the jobs specified in the processes of S13 and S15.

  As a result, the monitoring apparatus 1 can comprehensively specify jobs that need to include information in the monitoring screen to be output next.

  Thereafter, the timing determination unit 113 of the monitoring device 1 refers to the time zone information 133 stored in the information storage area 130 as shown in FIG. 12, and the status information of the target job specified in the processes of S13, S15, and S17 The timing for requesting 132 is determined (S21). Hereinafter, a specific example of the time zone information 133 will be described.

[Specific examples of time zone information]
FIG. 17 is a diagram illustrating a specific example of the time zone information 133. The time zone information 133 illustrated in FIG. 17 includes an “item number” that identifies each piece of information included in the time zone information 133, an “identification ID” that identifies each job scheduler JS2, and a “time zone” that indicates each time zone. And as an item. Also, the time zone information 133 shown in FIG. 17 includes “average time” indicating the average time required to acquire the status information 132 from each job scheduler JS2, and acquisition of the status information 132 from each job scheduler JS2. “Maximum time” indicating the maximum time required is included as an item.

  Specifically, in the time zone information 133 illustrated in FIG. 17, “JS2a” is set as the “identification ID” and “7: 00-” as the “time zone” in the information whose “item number” is “1”. 11:00 "is set. In the time zone information 133 shown in FIG. 17, “0.2 (seconds)” is set as “average time” and “0” is set as “maximum time” for information whose “item number” is “1”. .4 (seconds) "is set. Description of other information included in FIG. 17 is omitted.

[Details of S21 processing]
Next, details of the processing of S21 will be described. As illustrated in FIG. 13, the timing determination unit 113 refers to the information storage area 130 that stores the time zone information 133, and the time required to acquire the status information 132 of the target job specified in S <b> 13 or the like (hereinafter referred to as a first time) (Also referred to as time) is specified for each job scheduler JS2a that performs schedule management of the target job specified in S13 or the like (S31).

  Then, the timing determination unit 113 sets, for each job scheduler JS2 corresponding to the target job specified in S13 or the like, the target job specified in S13 or the like at a timing that is at least a first time before the timing at which the monitoring screen is output. Is determined as the timing for requesting the state information 132 (S32).

  Specifically, in the time zone information 133 illustrated in FIG. 17, for example, the information whose “identification ID” is “JS2a” and “time zone” is “7: 00-11: 00: 00” is “item number”. Is information “1”. In the time zone information 133 illustrated in FIG. 17, for example, information whose “ID” is “JS2b” and “time zone” is “7: 00-11: 00: 00” is “item number” is “ 4 ”. Therefore, for example, when the time that the monitoring screen needs to be output next is 8:00, and the NET # 1, NET # 2, and NET # 3 are specified in the processing of S13 and the like, the timing determination unit 113 Reference is made to information whose “item numbers” in the time zone information 133 are “1” and “4”.

  That is, in this case, the timing determination unit 113 sets “JS2a” indicating the job scheduler JS2a managing NET # 2 and NET # 3 among the information included in the time zone information 133 to “identification ID”. Reference is made to information in which “item number” is “1”, which is information in which “7:00 to 11:00” including time is set to “time zone”. In this case, the timing determination unit 113 sets “JS2b” indicating the job scheduler JS2b that manages NET # 1 among the information included in the time zone information 133 to “identification ID”, and includes “8 o'clock”. Reference is made to information in which “item number” is “4”, which is information in which “7:00 to 11:00” is set to “time zone”.

  Then, in the process of S31, the timing determination unit 113, for example, “average time” of information whose “item number” is “1” as the time corresponding to NET # 2 and NET # 3 operating in the job scheduler JS2a “0.2 (seconds)”, which is the information set in the above, is specified. In addition, in the process of S31, for example, the timing determination unit 113 sets the “average time” of the information whose “item number” is “1” as the time corresponding to NET # 1 operating in the job scheduler JS2b. Information “0.3 (seconds)” is specified. Furthermore, for example, the timing determination unit 113 sets the number of jobs that acquire the state information 132 to “0.2 (seconds)” that is the time required to acquire the state information 132 of the NET # 2 and the NET # 3. “0.4 (second)” that is the result of multiplying a certain “2” is specified. In addition, the timing determination unit 113 sets, for example, “1” which is the number of jobs for acquiring the status information 132 to “0.3 (seconds)” which is the time required for acquiring the status information 132 of NET # 1. “0.3 (second)”, which is the result of multiplication, is specified.

  After that, in the process of S32, the timing determination unit 113 needs to output a monitoring screen as a timing for requesting the status information 132 of NET # 2 and NET # 3 from the job scheduler JS2a as shown in FIG. A time that is 0.4 seconds or more before a certain time (for example, 8 o'clock) is specified. Further, in the process of S32, the timing determination unit 113, as shown in FIG. 18, sets 0 for the time (for example, 8:00) when the monitoring screen needs to be output as the timing for requesting the status information 132 of NET # 1. .Specify time more than 3 seconds ago.

  Returning to FIG. 12, the request transmission unit 114 of the monitoring device 1 waits until the timing determined in the process of S21 arrives (NO in S22). Specifically, when the timing determined in the process of S21 is 0.4 seconds before 8 o'clock and 0.3 seconds before 8 o'clock, 0.4 of 8 o'clock, which is the earlier of these times, Wait until seconds ago.

  When the timing determined in the process of S21 has arrived (YES in S22), the request transmission unit 114 identifies the job scheduler JS2 corresponding to the timing reached in the process of S22 with the process specified in the process of S13, etc. The job status information 132 is requested (S23).

  Specifically, in this case, for example, the request transmission unit 114 transmits a transmission request for the status information 132 to the job scheduler JS2a corresponding to 0.4 seconds before 8 o'clock, which is the timing determined in S21. To do.

  Thereafter, the request transmission unit 114 determines whether a transmission request for the status information 132 has been transmitted to all the job schedulers JS2 corresponding to the timing determined in the process of S21 (S24). As a result, when it is determined that the transmission request for the status information 132 has not been transmitted to all the job schedulers JS2 (NO in S24), the request transmission unit 114 performs the processing subsequent to S22 again.

  Specifically, for example, the request transmission unit 114 transmits a transmission request for the status information 132 to the job scheduler JS2a and then 0.3 seconds before 8 o'clock (the transmission request for the status information 132 to the job scheduler JS2b). Until it is time to send.

  On the other hand, when it is determined that the transmission request for the status information 132 has been transmitted to all the job schedulers JS2 (YES in S24), the status information receiving unit 115 of the monitoring device 1 includes the status information 132 requested in the process of S23. Wait until all are received (NO in S25). Hereinafter, a specific example of the state information 132 will be described.

[Specific example of status information]
FIG. 19 is a diagram for explaining a specific example of the state information 132. FIG. 19A is a diagram illustrating a specific example of the status information 132 received from the job scheduler JS2a, and FIG. 19B is a diagram illustrating a specific example of the status information 132 received from the job scheduler JS2b. is there. Hereinafter, it is assumed that each job scheduler JS2 manages each job according to the schedule information 131 described with reference to FIG. Hereinafter, it is assumed that the state information 132 illustrated in FIG. 19 is information acquired to generate a monitoring screen output at 8:00.

  The status information 132 illustrated in FIG. 19 includes an “item number” that identifies each piece of information included in the status information 132, an “identification ID” that identifies the job scheduler JS2, and a “job ID” that identifies each job (job net). As an item. Further, the status information 132 illustrated in FIG. 19 includes “status” indicating the execution status of each job as an item. “Status” includes “normal end” indicating that the execution of each job ended normally, “abnormal end” indicating that the execution of each job did not end normally, and that each job is being executed Is set to “in execution” indicating that each job is waiting to be executed, or “waiting to execute” is set.

  Specifically, in the status information 132 shown in FIG. 19, “JS2a” is set as the “identification ID” and “NET # 2” is set as the “job ID” in the information whose “item number” is “1”. Is set, and “waiting for execution” is set as “status”. In the status information 132 shown in FIG. 19, “JS2a” is set as the “identification ID” and “NET # 3” is set as the “job ID” in the information whose “item number” is “2”. “Waiting for execution” is set as “Status”. Description of other information included in FIG. 19 is omitted.

  Returning to FIG. 12, when all of the requested status information 132 is received (YES in S25), the screen generator 116 of the monitoring device 1 uses the status information 132 of the target job received in the processing of S25 within a specific time period. A monitoring screen indicating the status of the target job to be executed is generated (S26). And the screen output part 117 of the monitoring apparatus 1 outputs the monitoring screen produced | generated by the process of S26 (S27).

  Thereafter, the schedule acquisition unit 111 waits until the next information acquisition timing (NO in S11).

  Here, the monitoring apparatus 1 may omit the process of S12 when the job monitoring process is performed for the second time or later. That is, in this case, the monitoring apparatus 1 may use the schedule information 131 acquired in the first job monitoring process also in the second and subsequent job monitoring processes.

  When the process of S12 is omitted, the request transmission unit 114 acquires information indicating a job for which a manual operation has been performed from each of the plurality of job schedulers JS2 in the process of S23. As a result, the target job specifying unit 112 can refer to information indicating a job for which a manual operation has been performed even when the process of S12 is not performed. Hereinafter, a specific example of the monitoring screen will be described.

[Specific example of monitoring screen]
FIG. 20 is a diagram illustrating a specific example of the monitoring screen. The monitoring screen shown in FIG. 20 is a monitoring screen generated when the status information 132 shown in FIG. 19 is acquired.

  Specifically, in the status information 132 shown in FIG. 19, “waiting for execution” is set for the “status” of the information whose “job ID” is “NET # 2”, and the “job ID” is “NET # 3”. “Waiting for execution” is set in the “status” of the information. Further, in the status information 132 illustrated in FIG. 19, “waiting for execution” is set as the “status” of the information whose “job ID” is “NET # 1”.

  Therefore, for example, as illustrated in FIG. 20, the screen generation unit 116 associates information indicating that “NET # 1” and “waiting for execution” correspond to “NET # 2” and “waiting for execution”. To the monitoring screen. Further, for example, as illustrated in FIG. 20, the screen generation unit 116 includes information indicating that “NET # 3” corresponds to “waiting for execution” in the monitoring screen.

  On the other hand, the status information 132 illustrated in FIG. 19 does not include information having “JOB ID” “NET # 4” and information having “JOB ID” “NET # 5”. Therefore, for example, as illustrated in FIG. 20, the screen generation unit 116 provides information indicating that the state information 132 corresponding to the information indicating “NET # 4” and “NET # 5” does not exist (for example, “no information”). ) In the monitoring screen. Specifically, as illustrated in FIG. 20, the screen generation unit 116 includes information indicating that information indicating “NET # 4” corresponds to information indicating “no information”, and information indicating “NET # 5”. And information indicating that “no information” corresponds to the monitoring screen.

  That is, for example, when the monitoring screen to be output next is generated, the monitoring device 1 omits acquisition of information on a job that is not executed before the next monitoring screen output time. As a result, the monitoring device 1 can reduce the processing load required for generating the monitoring screen, and at the time (scheduled time) when the output of the monitoring screen reflecting the actual job status is requested. It becomes possible to do.

  Note that when calculating the first time in the process of S31, the timing determination unit 113 replaces the “average time” of the time zone information 133 shown in FIG. 17 with “ "Maximum time" may be used. Specifically, the timing determination unit 113 multiplies the time set in the “maximum time” of the time zone information 133 illustrated in FIG. 17 by the number of jobs for which the status information 132 needs to be acquired. One time may be calculated. Further, in this case, the timing determination unit 113 is permitted when outputting the monitoring screen from a value obtained by multiplying the time set in the “maximum time” of the time zone information 133 illustrated in FIG. 17 by the number of jobs. The first time may be calculated by subtracting a certain time (hereinafter also referred to as allowable delay time).

  Furthermore, the value obtained by multiplying the time set for “Average time” and the number of jobs is equal to or greater than the value obtained by subtracting the allowable delay time from the value obtained by multiplying the time set for “Maximum time” and the number of jobs. In some cases, the timing determination unit 113 may set a value obtained by multiplying the time set in the “average time” by the number of jobs as the first time. Also, the value obtained by multiplying the time set for “Average Time” by the number of jobs is less than the value obtained by multiplying the time set for “Maximum Time” by the number of jobs minus the allowable delay time. In some cases, the timing determination unit 113 may use a value obtained by subtracting the allowable delay time from the value obtained by multiplying the time set as the “maximum time” by the number of jobs as the first time.

  Thereby, the monitoring apparatus 1 can determine the calculation method of the 1st time according to the execution state of each job in each time slot | zone, for example.

[Status information generation process]
Next, a process in which the management apparatus 2 generates the state information 132 (hereinafter also referred to as a state information generation process) will be described.

  As shown in FIG. 14, the request reception unit 212 of the management device 2 waits until a transmission request for the status information 132 is received (NO in S111). That is, the request reception unit 212 waits until the monitoring device 1 transmits a transmission request for the status information 132 to the management device 2.

  When the transmission request for the status information 132 is received (YES in S111), the status information generation unit 213 of the management device 2 accesses each job execution device 3 and acquires information indicating the operation status of each job ( S112). Further, the state information generation unit 213 generates state information 132 including information indicating the operation state of each job acquired in the process of S112 (S113). Thereafter, the state information generation unit 213 stores the state information 132 generated in S113 in the information storage area 230 (S114).

  Thereby, each management device 2 can transmit the status information 132 corresponding to the transmission request transmitted from the monitoring device 1 to the monitoring device 1.

[Specific examples of job monitoring processing]
Next, a specific example of job monitoring processing will be described. FIG. 21 to FIG. 24 are diagrams for explaining a specific example in which job monitoring processing is performed again after the monitoring screen shown in FIG. 20 is output. Hereinafter, the monitoring screen is output every 10 minutes. In addition, hereinafter, each time the monitoring screen is output, the specific period in the process of S13 is changed to a time after 10 minutes.

[Specific example of job monitoring process performed for the second time]
First, a specific example of the second job monitoring process (job monitoring process performed immediately after the monitoring screen output described in FIG. 20 is performed) will be described.

  In the schedule information 131 shown in FIG. 15, information in which the information set in “scheduled start time” is between “08:10” and “08:20” is information in which “item number” is “4”. It is. Therefore, in this case, the target job specifying unit 112 specifies “NET # 4” that is information set in “job ID” of information in which “4” is set in “item number” in the process of S13. .

  In the status information 132 shown in FIG. 19, “waiting for execution” is set for all “status” of the information whose “job ID” is “NET # 2”, “NET # 3”, and “NET # 1”. Has been. For this reason, the target job specifying unit 112 determines that NET # 1, NET # 2, and NET are the jobs that have not ended normally (jobs that are being executed, jobs that are waiting to be executed, or jobs that have ended abnormally) in S15. Specify # 3.

  Therefore, in the process of S23, the request transmission unit 114 transmits a transmission request for the NET # 2 and NET # 3 status information 132 to the job scheduler JS2a, and the NET # 1 status information 132 to the job scheduler JS2b. Send a send request. Further, in the process of S23, the request transmission unit 114 transmits a transmission request for the status information 132 of NET # 4 to the job scheduler JS2c.

  And the status information receiving part 115 receives the status information 132 shown in FIG. 21 in the process of S25. Specifically, as shown in FIG. 21, the status information receiving unit 115 indicates that NET # 2 and NET # 3 are being executed, NET # 1 has been normally terminated, and NET # 4 is waiting to be executed. Get the information shown.

  Thereafter, in the process of S26, the screen generation unit 116, as shown in FIG. 22, information indicating that “NET # 1” and “normal end” correspond, “NET # 2”, and “being executed” Are included in the monitoring screen, and information indicating that “NET # 3” and “under execution” correspond. Further, in the process of S26, the screen generation unit 116, as shown in FIG. 22, information indicating that “NET # 4” corresponds to “waiting for execution”, “NET # 5”, and “no information”. And information indicating that is supported in the monitoring screen.

[Specific example of job monitoring processing performed for the third time]
Next, a specific example of the job monitoring process performed for the third time (job monitoring process performed immediately after the output of the monitoring screen described in FIG. 22 is performed) will be described.

  In the schedule information 131 shown in FIG. 15, information in which “scheduled start time” is between “08:20” and “08:30” is information in which “item number” is “5”. Therefore, in this case, the target job specifying unit 112 specifies “NET # 5” which is information set in “job ID” of information in which “5” is set in “item number” in the process of S13. .

  Further, in the status information 132 shown in FIG. 21, “running” is set in the “status” of the information whose “job ID” is “NET # 2” and “NET # 3”, and “job ID” “Normal end” is set in the “status” of the information whose is “NET # 1”. In the status information 132 shown in FIG. 23, “waiting for execution” is set in the “status” of the information whose “job ID” is “NET # 4”. Therefore, the target job specifying unit 112 specifies NET # 2, NET # 3, and NET # 4 as jobs that have not ended normally in the process of S15.

  Therefore, in the process of S23, the request transmission unit 114 transmits a transmission request for the status information 132 of NET # 2 and NET # 3 to the job scheduler JS2a, and NET # 4 and NET # 5 to the job scheduler JS2c. The transmission request of the status information 132 is transmitted.

  And the status information receiving part 115 receives the status information 132 shown in FIG. 23 in the process of S25. Specifically, in the state information receiving unit 115, NET # 4 is being executed, NET # 1 and NET # 3 are normally terminated, NET # 2 is abnormally terminated, and NET # 5 is waiting to be executed. Acquire information indicating that.

  Thereafter, in the process of S26, the screen generation unit 116, as shown in FIG. 24, information indicating that “NET # 2” corresponds to “normal end”, “NET # 3”, and “abnormal end”. Are included in the monitoring screen, and information indicating that “NET # 4” and “under execution” correspond. In addition, in the process of S26, the screen generation unit 116 includes information indicating that “NET # 5” and “waiting for execution” correspond to each other in the monitoring screen, as shown in FIG.

  In this case, the state information receiving unit 115 does not acquire the state information 132 of NET # 1. Therefore, the screen generation unit 116 may divert the information about NET # 1 among the information included in the monitoring screen shown in FIG.

[Second Embodiment]
Next, a second embodiment will be described. FIG. 25 is a flowchart illustrating job monitoring processing according to the second embodiment.

  In the process of S21, the timing determination unit 113 in the first embodiment determines the time for requesting the job scheduler JS2 for the status information 132 of each job. On the other hand, the timing determination unit 113 in the second embodiment determines the order in which the job scheduler JS2 requests the status information 132 of each job in the process of S21. Hereinafter, only the process (the process of S21) different from the first embodiment will be described.

  As shown in FIG. 25, the timing determination unit 113 refers to the information storage area 130 that stores the time zone information 133, and acquires the time (hereinafter referred to as the first time) required to acquire information related to the status of the target job specified in the processing of S13 and the like. (Also referred to as time 2) is specified for each job scheduler JS2 corresponding to the target job specified in S13 or the like (S41).

  Then, the timing determination unit 113 determines that the order of the target jobs corresponding to the job scheduler JS2 in which the second time specified in the process of S41 is longer than that of the other job scheduler JS2 is higher than that of the target job corresponding to the other job scheduler JS2. The order in which the status information 132 of the target job specified in S13 or the like is requested is determined (S42).

  Thereafter, the timing determination unit 113 determines the timing for requesting the status information 132 of the target job according to the order determined in the process of S42 (S43). Specifically, for example, the timing determination unit 113 requests the status information 132 for the next job scheduler JS2 after a predetermined time has elapsed after a request for the status information 132 for a certain job scheduler JS2. In addition, the timing may be determined. In addition, for example, the timing determination unit 113 receives the status information 132 from the job scheduler JS2 after a request for the status information 132 to a certain job scheduler JS2, and then receives the status information 132 from the job scheduler JS2. The timing may be determined so that the status information 132 is requested.

  As a result, the timing determination unit 113 can reduce the burden when determining the request timing of the status information 132 for each job scheduler JS2.

  The above embodiment is summarized as follows.

(Appendix 1)
Get job schedule information from each of multiple job schedulers that manage the schedule of jobs to be executed,
Based on the acquired schedule information, identify the target job to be executed within a specific period,
Request information related to the status of the identified target job to the job scheduler that manages the identified target job,
Generating a screen showing the status of the target job to be executed within the specific time from information on the status of the target job acquired in response to the request;
A job monitoring program for causing a computer to execute processing.

(Appendix 2)
In Appendix 1,
Before the requested processing, refer to a storage unit that stores the time required to acquire the job status according to the time zone, and determine the timing for requesting information on the status of the target job.
Let the computer execute the process,
In the requesting process, a request for information on the state of the target job is made at the determined timing.
A job monitoring program.

(Appendix 3)
In Appendix 2,
In the process of determining,
Specifying a first time required to acquire information on the status of the target job for each job scheduler corresponding to the target job;
A timing that is at least the first time before the timing of performing the processing to be generated is determined for each job scheduler corresponding to the target job as a timing of requesting information on the state of the target job;
A job monitoring program.

(Appendix 4)
In Appendix 1,
When there are a plurality of the target jobs, an order of requesting information on the state of the target job by referring to a storage unit that stores a time required to acquire the state of the job according to a time zone before the requested process To decide,
Let the computer execute the process,
In the requested process, a request for information on the state of the target job is made at a timing according to the determined order.
A job monitoring program.

(Appendix 5)
In Appendix 4,
In the process of determining,
Specifying a second time required to acquire information on the status of the target job for each job scheduler corresponding to the target job;
The status of the target job is such that the order of the target jobs corresponding to the job scheduler that is longer than the other job scheduler is before the target job corresponding to the other job scheduler. Determine the order in which information is requested,
A job monitoring program.

(Appendix 6)
In Appendix 1,
In the specifying process, in addition to a job executed within the specific period, a job for which a manual operation is performed is specified as the target job.
A job monitoring program.

(Appendix 7)
In Appendix 6,
In the specifying process, a job in which the manual operation is performed after the screen generation performed immediately before is specified as the target job.
A job monitoring program.

(Appendix 8)
In Appendix 6,
In the specifying process, when an operation log output when the manual operation is performed is generated, a job corresponding to the generated operation log is specified as the target job.
A job monitoring program.

(Appendix 9)
In Appendix 1,
In the specifying process, in addition to jobs executed within the specified period, a job that has not been normally completed among jobs executed in the past is specified as the target job.
A job monitoring program.

(Appendix 10)
A schedule acquisition unit that acquires job schedule information from each of a plurality of job schedulers that perform schedule management of jobs to be executed;
A target job specifying unit for specifying a target job to be executed within a specific period based on the acquired schedule information;
A request transmission unit that requests information relating to the status of the identified target job to a job scheduler that manages the identified target job;
A screen generation unit that generates a screen indicating the state of the target job executed within the specific time from information on the state of the target job acquired in response to the request;
A job monitoring apparatus.

(Appendix 11)
In Appendix 10,
A timing determination unit that determines a timing for requesting information related to the state of the target job with reference to a storage unit that stores time required to acquire the job state according to a time zone;
The request transmission unit requests information on the state of the target job at the determined timing;
A job monitoring apparatus.

(Appendix 12)
Get job schedule information from each of multiple job schedulers that manage the schedule of jobs to be executed,
Based on the acquired schedule information, identify the target job to be executed within a specific period,
Request information related to the status of the identified target job to the job scheduler that manages the identified target job,
Generating a screen showing the status of the target job to be executed within the specific time from information on the status of the target job acquired in response to the request;
A job monitoring method characterized by the above.

(Appendix 13)
In Appendix 12,
Before the requesting step, refer to a storage unit that stores the time required to acquire the job status according to the time zone, and determine the timing for requesting information on the status of the target job.
Let the computer execute the process,
In the requesting step, a request for information on the state of the target job is made at the determined timing.
A job monitoring method characterized by the above.

1: Monitoring device 2: Management device 3: Job execution device JS1: Job scheduler JS2: Job scheduler

Claims (11)

Get job schedule information from each of multiple job schedulers that manage the schedule of jobs to be executed,
Based on the acquired schedule information, identify the target job to be executed within a specific period,
Request information related to the status of the identified target job to the job scheduler that manages the identified target job,
Generating a screen showing the status of the target job to be executed within the specific time from information on the status of the target job acquired in response to the request;
A job monitoring program for causing a computer to execute processing. The claim 1, further comprising:
Before the requested processing, refer to a storage unit that stores the time required to acquire the job status according to the time zone, and determine the timing for requesting information on the status of the target job.
Let the computer execute the process,
In the requesting process, a request for information on the state of the target job is made at the determined timing.
A job monitoring program. In claim 2,
In the process of determining,
Specifying a first time required to acquire information on the status of the target job for each job scheduler corresponding to the target job;
A timing that is at least the first time before the timing of performing the processing to be generated is determined for each job scheduler corresponding to the target job as a timing of requesting information on the state of the target job;
A job monitoring program. The claim 1, further comprising:
When there are a plurality of the target jobs, an order of requesting information on the state of the target job by referring to a storage unit that stores a time required to acquire the state of the job according to a time zone before the requested process To decide,
Let the computer execute the process,
In the requested process, a request for information on the state of the target job is made at a timing according to the determined order.
A job monitoring program. In claim 4,
In the process of determining,
Specifying a second time required to acquire information on the status of the target job for each job scheduler corresponding to the target job;
The status of the target job is such that the order of the target jobs corresponding to the job scheduler that is longer than the other job scheduler is before the target job corresponding to the other job scheduler. Determine the order in which information is requested,
A job monitoring program. In claim 1,
In the specifying process, in addition to a job executed within the specific period, a job for which a manual operation is performed is specified as the target job.
A job monitoring program. In claim 6,
In the specifying process, a job in which the manual operation is performed after the screen generation performed immediately before is specified as the target job.
A job monitoring program. In claim 6,
In the specifying process, when an operation log output when the manual operation is performed is generated, a job corresponding to the generated operation log is specified as the target job.
A job monitoring program. In claim 1,
In the specifying process, in addition to jobs executed within the specified period, a job that has not been normally completed among jobs executed in the past is specified as the target job.
A job monitoring program. A schedule acquisition unit that acquires job schedule information from each of a plurality of job schedulers that perform schedule management of jobs to be executed;
A target job specifying unit for specifying a target job to be executed within a specific period based on the acquired schedule information;
A request transmission unit that requests information relating to the status of the identified target job to a job scheduler that manages the identified target job;
A screen generation unit that generates a screen indicating the state of the target job executed within the specific time from information on the state of the target job acquired in response to the request;
A job monitoring apparatus. Get job schedule information from each of multiple job schedulers that manage the schedule of jobs to be executed,
Based on the acquired schedule information, identify the target job to be executed within a specific period,
Request information related to the status of the identified target job to the job scheduler that manages the identified target job,
Generating a screen showing the status of the target job to be executed within the specific time from information on the status of the target job acquired in response to the request;
A job monitoring method characterized by the above.

Images