JPH08286778A - Job execution management method and device therefor - Google Patents

Abstract

PURPOSE: To execute JOB correctly by automatically judging the execution propriety of respective jobs based on JOB attributes including registered prerequisite JOB and the schedule of processing execution. CONSTITUTION: The pre-execution check program of a step S2-1 is executed at first and a JOB schedule record is read with a processing scheduled data concerned as a KEY in the pre-execution check program. The execution schedule of the JOB of the processing schedule is checked by table searching. When it is to be executed, a JOB check record is read with the JOB concerned as the KEY. Then, whether all the JOBs being presupposition are normal or not is judged by sequentially referring to the prerequisite JOB table shown by diagonal lines. When all the JOBs are normal, JOB-B is executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a batch-type multiple job (hereinafter referred to as "J") which is executed based on transaction data generated as a result of various entry operations artificially executed.
OB) execution management work, especially for individual JOBs
The present invention relates to a JOB execution management method for automatically performing execution availability determination / execution result management in the same batch process, and an apparatus for implementing the method.

[0002]

2. Description of the Related Art Conventionally, when batch-type multiple jobs for transaction processing are performed in an unattended state at night, etc.,
By incorporating the job stream coded to perform the continuous batch processing on the system, only the activation of each JOB is automatically performed. Therefore, in this system, it is possible to determine whether or not the job can be executed, including the execution schedule management of each job.
It was impossible to manage the execution result of B and use it as the execution feasibility determination standard of the subsequent open job.

[0003]

As described above, each J
Since continuous batch-type transaction processing is automatically executed using a job stream that stores only OB startup information, execution permission judgment including execution schedule management for each JOB and execution result management for each JOB are not possible. This is possible, and the next JOB is often executed without satisfying the prerequisites for execution. Moreover, confirmation of the execution result was also impossible except by performing it artificially after the completion of the batch processing. Therefore, the entry processing of the next day is started without recognizing the processing abnormality, or even if it is recognized, it is necessary to return from the save (SAVE) medium to the file environment before executing the relevant batch JOB and rerun (RERUN). Recovery (RECOV
There was a problem that scandals occurred because it took a lot of man-hours for ERY) and it became impossible to provide functions to the business itself.

Therefore, the technical problem of the present invention is not only to improve the accuracy of the work and to reduce the work but also to reduce the recovery man-hours in the case of a system abnormality, and eventually to realize the system support with less trouble in the work itself. It is to provide a batch type job execution management method of an automatic operation type.

[0005]

The batch type JO of the present invention
In the automatic execution management system of B, in order to solve the above-mentioned problems, a prerequisite JOB (processing) is created for each new JOB, and its execution schedule is set during operation. By registering, the function of creating (updating) the JOB execution management file, and whether or not all the prerequisite jobs have been completed normally when batch processing is executed based on the job stream, And confirm the execution schedule of the JOB based on the above-mentioned JOB execution management file, and check whether it can be executed or not before execution.
In addition, a post-job check is performed to store each JOB execution result in the JOB execution management file.

[0006]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1A is an explanatory diagram showing the configuration and flow in the embodiment of the present invention, and FIG. 1B is a diagram showing the execution schedule and precondition JOB of each JOB in the example of FIG. FIG. 1C is a diagram showing a specific processing flow of JOB-B in FIG.

2A shows a JOB schedule record, FIG. 2B shows a JOB check record, FIG. 2C shows a JOB result update record, and FIG. 2D. FIG. 8 is a diagram showing a JOB execution management file that is referenced during each check.

In FIG. 1A, JOB-A and JOB-
A job stream of batch processing including three jobs B and JOB-C is shown. In FIG. 1A, the process is started in step S0, JOB-A is executed in step S1, JOB-B is executed in step S2, JOB-C is executed in step S3, and the process is ended in step SE. The job stream is shown.

Referring to FIG. 1B, the execution schedules set for the JOB-A, JOB-B, and JOB-C in FIG. 1A and the preconditions for executing each JOB. JOB is shown.
As is clear from FIG. 1 (b), there is no precondition when JOB-A is executed, and JOB-B is executed after JOB-A is executed as a precondition to be executed. Shows. In addition, JOB-C is JOB-A
And JOB-B are assumed to be executed, but in this case they are not executed.

FIG. 1 (c) shows FIG. 1 (a) and FIG.
JOB-A, JOB-B, and JOB shown in (b)
As an example of -C, a detailed processing flow of JOB-B indicated by diagonal lines is shown. First, JOB-B starts in step S2-0, checks before execution in step S2-1, and then in step S2-2, JOB-B starts.
BB is actually executed. After execution of JOB, post-execution check is performed in step S2-3, and step S2-
At E, JOB-B ends. Other JOB-A and JOB-C are also executed by the same processing flow.

JOB-A and JOB shown in FIG.
-B and JOB-C JOB schedule records include the scheduled execution date, JOB-A, JOB-B, and JOB-C.
It is recorded whether or not is executed.

In the JOB check record shown in FIG. 2B, the result of the check is recorded, and the black star mark indicates any one of "normal", "abnormal", and "non-execution". Is showing. The JOB schedule record and the JOB check record are referred to for the check before the execution in FIG.

The JOB result update record shown in FIG. 2C is composed of a JOB identification (JOB-ID) and a check record reverse lookup table.

In the JOB execution management file shown in FIG. 2 (d), steps S2-1 and S2- of FIG. 1 (c) are included.
The above 3 that is referenced and updated at each check in 3
A type of execution management file, that is, a JOB schedule record, a JOB check record, and a JOB result update record are stored.

Here, the JOB schedule record of FIG. 2A is registered in advance by a person in charge for each scheduled date of automatic operation of processing. In addition, the JOB check record shown in FIG. 2B and the JOB check record shown in FIG.
The result update record is created with each JOB-ID as KEY when a JOB is newly created and incorporated into the process.

Returning to FIG. 1C, the pre-execution check indicated by the slanted lines is indicated by the record contents 11 of the JOB schedule record indicated by the slanted lines in FIG. 2A and the slanted line in FIG. 2B. The JOB check records (record contents thereof) 12 and 13 are respectively referred to and updated. Further, the JOB result update record (record content) 14 indicated by the diagonal lines in FIG. 2C is also referred to and updated.

FIG. 3 is a diagram showing the detailed processing flow of the JOB pre-execution check of FIG. 1 (c), and FIG. 4 is shown in FIG. 1 (c).
FIG. 8 is a diagram showing a detailed processing flow of post-job check of FIG.

Next, the operation will be described. When the process shown in the process flow of FIG. 1C is started by the job stream of FIG. 1A, first, step S2-1
The pre-execution check program of is executed. In the pre-execution check program, first, the JOB indicated by the diagonal line in FIG.
The schedule record is read (step S2-
11). Next, in step S2-12, the execution schedule of the job to be processed (here, "B" shown by the diagonal lines) is checked by table search. here,
If not executed (N), the process proceeds to step S2-31 in the flowchart of FIG. On the other hand, in the case of execution (Y), the corresponding JOB (here, “B”) is set as KEY, and
The JOB check record shown in (b) is read (step S2-13). Next, by sequentially referring to the prerequisite JOB table as indicated by the diagonal lines,
It is determined whether or not all JOBs that are prerequisites are normal (step S2-14). As a result, if all are normal (Y), JOB-B is executed (step S2-15).

After JOB-B is completed, the post-execution check program shown in FIG. 4 is started. In the program, the corresponding JOB (here, “B”) is set as KEY, and the JOB result update record 14 indicated by the diagonal lines in FIG.
Is read (step S2-31), and the check record reverse lookup table is sequentially referenced (steps S2-32 and S2-36). JOB stored in the reverse lookup table
(JOB whose own JOB is a precondition: "C" in this case) is KEY, the JOB check record 13 is read (step S2-33), and the status (normal, abnormal, non-execution) of the execution result of JOB-B is read. It is set in the corresponding table (step S2-34), and the JOB check record 13 is rewritten (step S2-35).
When all the jobs stored in the check record reverse lookup table are KEY, the job check records of FIG. 2B are processed, and when the processing of steps S2-33 to S2-35 is completed, FIG. J0B-A shown in
The processes of J0B-B and J0B-C are completed (step S2-E).

[0021]

As described above, according to the present invention, in a general-purpose machine system that performs batch processing including a plurality of jobs including unmanned automatic operation, a person in charge does not artificially judge whether processing can be performed one by one. There is no mistake even in the system system in which there is a shortage of computing personnel by automatically judging the executability of each JOB based on the registered precondition JOB and other JOB attributes and the process execution schedule. Since the operation can be performed, not only the accuracy of the work can be improved and the work can be reduced, but also the recovery man-hours can be reduced in the case of a system abnormality, and eventually the system support with less hindrance to the work itself can be realized. is there.

[Brief description of drawings]

FIG. 1A is an explanatory diagram showing a configuration and a flow in an embodiment of the present invention. (B) is each JO in the example of (a)
It is a figure which shows the execution schedule and precondition JOB of B. (C) is a figure which shows the processing flow of JOB-B of (a).

FIG. 2A is a diagram showing a JOB schedule record. (B) is a diagram showing a JOB check record. (C) is a figure which shows a JOB result update record.
(D) is a figure which shows a JOB management file.

FIG. 3 is a diagram showing a detailed processing flow of a pre-job check in FIG. 1 (c).

FIG. 4 is a diagram showing a detailed processing flow of a post-job check in FIG. 1 (c).

[Explanation of symbols]

 10 JOB execution management file 11 JOB schedule record 12, 13 JOB check record 14 JOB result update record

Claims (5)

[Claims] 1. In a general-purpose system that performs batch processing consisting of a plurality of jobs, including unattended automatic operation at night, etc., in executing an execution schedule of each job, a job that is a prerequisite for each job is defined. A job execution management method characterized in that the registration is performed and the execution result of each job is recorded to automatically determine the executability of the plurality of continuous jobs and manage the execution results of the jobs. 2. The job execution management method according to claim 1, wherein the executability determination is made by an execution schedule check performed before execution of each selected job, and the execution result management is performed by the selected individual job. The job execution management method, which is performed by checking the execution result performed after the execution of the job. 3. The job execution management method according to claim 2, wherein the execution schedule check includes a job schedule record having a time record and an executability record of each job created in advance, and the job registration as the precondition. , Each job is performed by referring to a job check record indicating one of normal, abnormal, and non-execution, and the execution result is checked by a job including a job identification and a check record reverse lookup table. A job execution management method, which is performed by referring to a result update record and the job check record. 4. A general-purpose machine system that performs batch processing consisting of a plurality of jobs, including unattended automatic operation at night, etc., registers a job that is a prerequisite for execution schedule and execution of each job, and File creation means for recording the execution results of each job, means for checking the executability of consecutive jobs based on the created files, a means for checking before execution, and an execution result check that automatically manages job execution results And a job execution management apparatus. 5. The job execution management apparatus according to claim 4, wherein a job schedule record in which execution time data created in advance and whether or not each job is executed are recorded, and a job schedule record newly created when the job is executed. The job check record that records whether each job is in the normal, abnormal, or non-execution state under the above prerequisites, and the job result update record composed of the job identification and check record reverse lookup table A job execution management device comprising a job execution management file provided.