JP2015064848A - Job management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a job management system capable of reducing workload of work, entailed by a change in a job net execution schedule, for changing the job net execution schedule on a side detecting and executing an event, and preventing work omission.SOLUTION: A job management system includes: a table for pre-defining a time difference between transmitting-side job start time and receiving-side job start time if a dependency relation for event transmission/reception is held among job nets; and a job management manager changing execution time of each job while referring to execution time in each job net so that the receiving-side job can start while securing the time difference defined in the table if an execution schedule of the job nets for which the time difference is already pre-defined is to be changed.

Description

  The present invention relates to a job management system, and more particularly to a job management system for easily and safely performing a schedule change operation for each job net that operates in conjunction with event transmission / reception with respect to an operation related to changing a job net execution schedule. Is.

An example of a conventional job management apparatus is shown in FIG.
In this example, the host machine 101A in which the job management manager 102 that manages actual jobs as jobs is installed, and job execution agents (103AC to 103C) that actually execute jobs distributed from the job management manager 102. The terminal 105 that can input data and output the results to the host machine (101B to 101D) installed with the job management manager 102 and the host machine (101B to 101D) for performing simulation. They are connected to each other via a network.
Here, the host machine is a machine that operates an actual job, and the host machine is a machine that performs simulation for a job to be newly added and a job that has already been operated. Here, the machine operating the actual business is defined as the production environment, and the machine for performing the simulation is defined as the verification environment.
The environment includes one job management manager 102 and three job execution agents (103AC to 103C).
The job management manager 102 distributes the managed job to each job execution agent and executes the job. The job distribution destination differs depending on the job contents of each job, and can be arbitrarily designated. When the job execution is completed, the job execution manager notifies the job management manager 102 of the job execution result. Upon receiving the result notification, the job management manager 102 operates daily operations by terminating the execution of the corresponding job.

An example of a conventional job net is shown in FIG.
Job 1 is executed first, and when completed, job 2 and job 3 are executed. When job 3 is finished, job 4 is executed.
Here, each job only knows about jobs that are related to its own jobs and jobs that are executed before, and it has no information about which jobs it is linked to. Not. There are multiple jobs in a job net, but each execution location can be a separate agent.
In the job management system, processing is automatically executed in response to a specific event, so-called event.
That is, it is defined that a job in a certain job net transmits a specific event.
A job in another job net can receive the event and execute a predefined job. At this time, the job net on the receiving side needs to be set to start before the job net on the event transmitting side “so as not to miss the reception”.

As described above, the job itself does not have definition information as to which job is related to its own job, and therefore it is necessary to define when to execute the job according to the schedule incorporated in the job net.
When changing the schedule of the event sending side, the schedule on the receiving side must be changed before the schedule on the receiving side.
The related art here is disclosed in the following patent document.

JP 2009-230322 A

In job management, jobs such as counting in business are defined. Then, define the date and time for actual execution.
There are several types of jobs, and each job can be broadly classified according to the type assigned to it.
For example, a job that transmits an event, a job that operates by receiving an event to be transmitted, and a job that transfers a received job are also known.
Some jobs that receive events exist as files that receive events and leave a history of them, but there are also jobs that disappear as they are when they are received. There are jobs that no longer exist, and the job itself no longer exists.

In the case of a job that disappears simply due to reception mediation, the role of the job after reception may be lost, so it is necessary to start the reception job first in order to receive events from another job is there.
This is because it is necessary to decide the start of the reception job in advance in the schedule, and if there is a change in the schedule, there is a dependency between the reception job and the transmission job, so the change may affect other job nets. There is a case.

  An object of the present invention is to reduce the amount of work for changing the execution schedule of a job net that is detected and executed when an execution schedule of a job net is changed, and to prevent omission of work. It is to provide a job management system that can do this.

  In order to achieve the above object, the job management system according to the present invention defines in advance a time difference between the start time of the sending job and the start time of the receiving job when there is an event transmission / reception dependency between job nets. When changing the execution schedule of a table and a job net for which the time difference is defined, refer to the execution time of each job net so that the receiving job is started with the time difference defined in the table secured. And a job management manager for changing a job execution time.

If the schedule linkage change between a plurality of job nets of the present invention is used, the amount of work when changing the execution schedule of the job net can be greatly reduced, and the change omission can be prevented.
As a result, it is possible to reduce the burden on the user when changing the schedule.

It is a figure which shows the structural example of the job management manager which is the principal part of the job management system which concerns on this invention. It is a figure which shows an example of the relationship between job nets. It is a figure which shows the example of a time difference definition table. 5 is a flowchart illustrating processing for confirming job connection in a job net. It is a flowchart which shows the process which confirms whether there are multiple jobs to which execution scheduled time was set. It is a figure which shows the example of a conventional job management system structure. It is a figure which shows the example of a job net.

Hereinafter, an embodiment of a schedule interlocking change function between a plurality of job nets to which the present invention is applied will be described.
FIG. 1 is a diagram showing a configuration example of a job management manager having a function for changing schedule linkage between a plurality of job nets.
The job management manager 100 includes a job connection destination determination unit 101, a job activation time confirmation unit 102, and a schedule time change unit 103, and is connected to the job net management DB 104 and the job schedule DB 105.

The job connection destination determination unit 101 is a unit that determines a connection relationship between jobs between job nets, and determines whether there is a connection relationship between jobs. As a determination target, the job net is stored in the job net management DB 104.
The job activation time confirmation unit 102 confirms whether the job activation time is set for the job with the job connection destination by the job connection destination determination unit 101 and confirms the specific contents of the activation time. It is means of.

  The schedule time changing unit 103 is a unit for changing the start time of the set job. The schedules before and after the change are renamed and stored in the job schedule DB 105.

FIG. 2 is a diagram showing a relationship diagram between job nets.
The basic operation here will be described.
First, job A of job net A is executed, and job B is executed after completion. jobB sends event A. Jobnet B executes jobC and executes jobD after completion.
jobD sends event B.
Multiple job nets execute each job in parallel or with a time difference

Job 1 of job net C receives event A and job 2 receives event B as the job net A and job net B are executed and the event is executed. If execution of both job1 and job2 is completed (AND condition), job3 is executed.
The job net C is activated before the job net A and job net B, and is waiting to receive the event A and event B. Job1 receives event A, and job2 receives event B.

In the job 1 and job 2 processing, if the processing in the job including event reception is completed, there is a determination in the AND job, and if both are completed, the subsequent job 3 is executed.
The execution schedule here is defined with the following settings.
(1) Job net A: Start every day at 11:00 am (2) Job net B: Start every day at 11:00 am (3) Job net C: Start every day at 10:00 am In this job management system, job net A and job net B Change the schedule to advance the start time.

  At this time, the job net C having a configuration for executing the reception event is started before the job net A or the job net B so as not to miss the premature event because there is a possibility of schedule change. It is also necessary to change the execution schedule of net C.

In the example shown in FIG. 2, the job net A and job net B are changed from the 11 o'clock start schedule to the 9 o'clock start schedule, and job B and Job D transmit events according to this change.
In job net C, job1 and job2 receive the event.
Here, when the start times of job net A and job net B are changed, job net C searches job net whose start time depends on event transmission / reception before transmission / reception of the event, and job management manager 100 searches for job nets. When the net C is found, the start time of the job net C is automatically changed based on the “start time difference”.

FIG. 3 is an example of the contents of a definition table defining “startup time difference”.
This table is used when the automatic schedule interlocking change function in the present invention is used.
The following information is stored in this table.
(1) Start time difference for each job net: A time difference set for each job net, and one record is defined for one job net. The time difference here means “when the event receiving side is activated at least earlier than the event transmitting side” when the automatic schedule interlocking change function is used. Therefore, when the job net execution schedule is initially set, it can be scheduled even when the time difference is shorter.
(2) Default start time difference: When using this function, this default value is applied to a job net for which the start time difference for each job net is not defined.

In the case of the example in FIG. 3, the start time difference from the sending job net when job net A receives the event is 15 minutes, and the start time difference from the sending job net when job net B receives the event is 10 minutes. When the job net C receives an event, the start time difference from the transmission side job net is one hour.
Since events from a plurality of job nets may be received, this difference in starting time is kept at a minimum.
The validity period of the information in the table is the default "startup time difference", while the job management system is operating, the "startup time difference" for each job net defines the job net and then deletes the job net Until.

FIG. 4 is a flowchart for explaining the details of the update process of the job schedule.
In this process, if there are multiple jobs in the job net that have scheduled job processing times, whether the start time of each scheduled time of the job receiving the event is within a certain threshold This is a process for confirming whether or not it is necessary to change the scheduled job execution time on the receiving side.

When the scheduled execution times of a plurality of defined jobs are changed, first, a search is performed as to whether there is a job connection in the job net (step 401).
In this search, it is determined whether or not there is connection to the own job (step 402).
In the case of step 402, only the top job has no connection (no single job is possible), and if it is the top job, the search is terminated (step 408).

If there is a connection to the job, it is checked whether the scheduled job execution time is set for the connection destination job (step 403).
If the scheduled execution time is not set for the job, the search ends (step 408).
If the scheduled execution time is set for the job, it is compared and confirmed whether there are a plurality of set jobs in the job net (step 404).

  The purpose of this step is to change the time difference of the receiving job if there are multiple jobs whose schedule time is scheduled to be changed and each scheduled execution time is within a certain range. If the scheduled times differ greatly, the job change time may be too long for the job on the event receiver side, and the job execution itself may be hindered. For this reason, check the time difference between multiple job execution times There is a need.

In step 404, confirm that there are scheduled execution times for multiple jobs,
The job execution scheduled time differences are compared (step 405).
In this case, if the difference is within the defined time difference, the schedule of the scheduled execution time of each job is changed as it is (step 407).

In the example of FIG. 2, since the start times of job net A and job net B are changed and the time difference is within an allowable range, the start time of job net C is also changed.
However, if there is a difference exceeding the range defined in the scheduled execution times of the plurality of jobs in step 405, the process proceeds to step 406.
The time difference range here can be defined by the user, but its width is changed according to the system.

For example, in the case of a job that is executed during the night when other jobs are stopped, the time difference within the time that falls within the night including the job execution time is defined.

FIG. 5 is a flowchart showing details of the job schedule update, and another process after step 404.
If the time difference between the scheduled execution times of the plurality of jobs is large at step 404 (step 501), first, the scheduled execution times of the plurality of jobs in the job net are compared, and the time difference is within the defined allowable time difference range. Is confirmed (step 502).
If the range is significantly different, the schedule of the event destination job is changed according to the scheduled time of the job to be executed first (step 503, in the case of FIG. 2, the job net A is changed to the job net C according to the change time). Change the schedule).
Next, in order to confirm the scheduled execution time of job B, the job net is searched again, and the schedule of the event destination job is changed in accordance with the scheduled change time of the job (step 504).

DESCRIPTION OF SYMBOLS 100 Job management manager 101 Job connection destination determination means 102 Job start time confirmation means 103 Schedule time change means 104 Job net management DB
105 Job schedule DB

Claims (1)

  When there is an event transmission / reception dependency between job nets, change the table that defines the time difference between the start time of the sending job and the start time of the receiving job, and the execution schedule of the job net for which the time difference is already defined A job management manager that refers to the execution time of each job net and changes the execution time of each job so that the receiving-side job is activated while ensuring the time difference defined in the table. Job management system.

Images