JPH0580993A - Job executing sequence control system - Google Patents

Abstract

PURPOSE:To ensure the flexible job executing sequence in a job executing sequence control system of a computer system by changing optionally the job executing sequence which is previously registered through a job under execution. CONSTITUTION:A job which is executed in a user job executing area 11 calls a subroutine to request a job execution control program 12 to change an executing sequence register area 13. Thus the registered job can be changed. Meanwhile a subroutine is called for reference to a job executing result message recording area 14. Thus the job executing results are transferred among jobs.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a job execution order control method for a computer system, and more particularly to changing the execution order of a job being executed and a succeeding job, and communicating execution results of preceding jobs between jobs. The present invention relates to a job execution order control method that changes the execution order of subsequent jobs according to the result.

[0002]

2. Description of the Related Art A conventional job execution sequence control method for automatically operating a system is, for example, Japanese Patent Laid-Open No.
The techniques described in JP-A-3-293619 and JP-A-63-317815 are mentioned.

Japanese Patent Laid-Open No. 63-293619 discloses a technique in which a plurality of jobs are registered in a file in advance and a simulation routine is assigned to each job and executed.

Further, in Japanese Patent Laid-Open No. 63-317815, a response to a message output to a console, a startup job, etc. are defined in a file in advance, and when the message is delivered, the response to the message and the activation are started. The technology for executing a job or the like is described.

[0005]

The above-mentioned prior art is intended for automatic execution of fixed jobs, and the execution order of jobs is only considered in the order registered in a file in advance. However, there is a problem in that the execution order of jobs registered in a file cannot be changed or deleted from a job being executed (user program), and the execution order of jobs cannot be dynamically changed.

Further, since consideration is not given to the execution result message of another job from the job being executed (user program), it is necessary to change the execution order of the succeeding job depending on the execution result of a certain job. There was a problem that the execution order could not be changed in the job (user program) being executed.

An object of the present invention is to make it possible to arbitrarily change the execution order of jobs registered in a file or memory in advance from a job being executed (user program), and to give flexibility to the execution order of jobs. To provide a control method.

[0008]

In order to achieve the above object, the present invention is provided with an execution order registration means in which the execution order of a plurality of jobs is registered in advance, and the execution order registered in the execution order registration means is provided. In the job execution order control method for executing jobs according to the above, a changing means for changing the execution order registered in the execution order registration means from the job being executed is provided, and the execution job is changed to the execution order registration means. When a request is made, the execution order registered in the execution order registration means is arbitrarily changed.

Further, in the present invention, the execution result message storage means for sequentially storing the execution result message of each job, and the execution result message reference for referring to the execution result message stored in the execution result message storage means from the job being executed. When the job being executed makes a reference request to the execution result message storage means, the execution result message stored in the execution result message storage means is arbitrarily referred to, and the changing means is provided according to the content of the referred execution result message. Is used to arbitrarily change the execution sequence registered in the execution sequence registration means.

[0010]

When the user calls a subroutine requesting change or deletion of a job registered in advance in the job execution order registration means from a job being executed (user program) at any time, the job execution management program reads the job in advance. It is possible to update the file or memory in which the execution order of the jobs is registered with the requested contents (change or deletion) by the subroutine, and execute the updated contents.

If the user calls a subroutine that references the execution result message of another job from an executing job (user program) at any time,
The job execution management program can notify the execution result message of the job requested by the subroutine from the job execution result message recording means that sequentially records the execution result message of each job. Job execution order can be changed.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS As an embodiment of the present invention, a method of deleting a registered succeeding job due to abnormal termination of a preceding job and newly registering another job as a succeeding job will be described in detail with reference to the drawings. ..

FIG. 1 is a diagram showing the internal configuration of a computer system for implementing the present invention.

The computer system 1 has a user job execution area 11 divided and divided into a plurality of areas.
Execute user jobs in each area.

Assuming that processing is executed when a change request or a deletion request is made by a subroutine from a job (user program) being executed in each user job execution area 11.
There is a job execution management program 12. The job execution management program 12 changes the execution order registration area 13 for registering the job execution order, and also refers to the job execution result message recording area 14 for sequentially recording the execution result messages of each user job. .. And
The job execution management program 12 notifies each user job execution area 11 by returning the result as a subroutine.

FIG. 2 is a diagram showing the format of the execution order registration area 13 for registering the execution order of jobs.

In the execution order registration area 13, the name of the user job execution area 11 to be executed and the name of the job to be activated are registered as a pair, and the number of registered pairs of entries is continuously created. , "*" Is registered in the last entry.

FIG. 2 shows that jobs A1 and A2 are executed in order in the user job execution area A, and then jobs B1 and B2 are executed in order in the user job execution area B.

FIG. 3 is a diagram showing the format of the job execution result message recording area 14 for sequentially recording the execution result messages of each user job.

Job execution result message recording area 14
, The message ID of the job execution result message and the job execution result message are registered as a pair, and the entries are paired as many as the registered number, and "*" is registered as the last entry. Has been done. The name of the job that was started is added to the job execution result message.

FIG. 3 shows that the job A1 to which the message ID "123" is added has ended normally, and the job A2 to which the message ID "456" has been added has ended abnormally.

2 and 3, that is, the job A1 ends normally, the succeeding job A2 ends abnormally, and the user job execution area 11 of the current user job execution area 11 is terminated. It is assumed that job B1 is being executed by B.

FIG. 7 shows a flowchart for explaining the operation of job B1.

While the job B1 is being executed in the user job execution area B, when the subroutine for referring to the execution result message of the preceding job of the job B1, that is, the job A2 is called (71), the job execution management program 1
2 uses the message ID of the requested job execution result and the started job name in the execution result message (in this case, the job name is A2) as a key to search the job execution result message recording area 14 and execute job A2 It is determined whether the process has been completed normally (72).

When it is determined in step 72 that the job A2 has ended normally, the job B1 thereafter executes normal processing and ends. On the other hand, when it is determined in step 72 that the job A2 has not ended normally, that is, it has ended abnormally, the job execution management program 12 notifies the user job execution area 11 of an execution result message indicating that the job A2 has ended abnormally (subroutine). Return).

In the case of the present embodiment, by referring to the entry 31 in which the message regarding the job A2 in the job execution result message recording area 14 is registered, the job A
The job execution management program 12 informs the user job execution area 11 of the execution result message of the abnormal end of the job A2 (subroutine return). In this way, it is possible to recognize that the job A2 has ended abnormally while the job B1 is being executed.

Next, with this as a trigger, a subroutine call is made to the job execution management program 12 with a deletion request so that the job B1 deletes the succeeding job B2 (73).
Performs change processing on the execution order registration area 13.

FIG. 6 shows a process of changing the execution order registration area 13 by the job execution management program 12.

First, it is determined whether or not the change processing for the execution order registration area 13 is a deletion request (61). If it is a deletion request, the corresponding entry in the execution order registration area 13 and the additional job stream are invalidated. That is, in this embodiment, the entry in which the job B2 is registered is deleted (62).

When the corresponding entry and the additional job stream in the execution order registration area 13 are deleted in step 62, the execution order registration area 13 is searched, the corresponding entry is invalidated, and a meaningless display is performed ( Forward display)
I do. Further, since the startup job registered in the corresponding entry may have already been added to the user job execution area as a subsequent job stream, the job stream added to the user job execution area is also deleted. After the deletion process is completed, the process returns to the process of job B1 by returning to the subroutine.

Next, in the job B1, a subroutine call is made to the job execution management program 12 to register the job C1 as a succeeding job in the execution order registration area 13 (74). Perform change processing.

This changing process will be described with reference to FIG.

First, it is determined whether or not the change processing for the execution order registration area 13 is a deletion request (61). In the case of the present embodiment, since it is a registration request, the process proceeds to "N", and it is determined whether or not to additionally register the last entry in the execution order registration area 13 (63). In this embodiment, the job B2 has already been deleted, and all the jobs shown in FIG. 2 have been started up. Therefore, the job B2 will be additionally registered in the last entry in the execution order registration area 13 "Y". Then, the user job execution area name and the startup job name are set in the last entry 21 of the execution order registration area 13 (64),
In order to display that the next entry is the last entry, the job execution area name and the startup job name are displayed as "*" (65). Then, if the activation process is in the waiting state, the waiting is released (66) and the subroutine returns to the job B1.

On the other hand, if it is requested in step 63 not to additionally register to the last entry in the execution order registration area 13 but to additionally register to an entry in the middle, the user area name and job name are added to the requested entry. Is registered (67). Then, the contents of the entries after the added entry are shifted one by one (68), and the subroutine returns.

The newly registered job C1 is activated by the activation process. The startup process will be described with reference to FIG.

In this embodiment, all the jobs shown in FIG. 2 have been started up before the additional registration of the new job C1. That is, before the additional registration of the new job C1, the execution of the job has proceeded to the last entry 21 in the execution order registration area 13. Therefore, it is judged whether the user area name to be executed is "*" (41)
Goes to “Y” and is in a waiting state (42) for activation.

After the new job C1 is additionally registered, whether the area to be executed is "*" after the waiting is canceled by the above-described step 66 (cancellation of the activation waiting in the job registration processing). A judgment (41) is made. In this step 41, the execution order registration area 13
Entry 21 in step 64 (additional registration in the execution order registration area 13), the job C1 has been added and changed in step 65, so the process proceeds to “N” to see if the job is running in the user area to be executed. Judgment of whether it is (43)
Move on to.

Here, since the job C1 is registered as the succeeding job of the job B2, the user area names are the same,
That is, the job B1 is B, and the job B1 is still being executed. Therefore, the result is "Y", and the job B1 is added to the job stream as a subsequent job (44).

Job C1 added to the job stream
Is executed after the end of job B1.

Then, the entry in the execution order registration area 13 is advanced to the next (45), and the process returns to step 41 again.
In the next determination at step 41, the next entry is "*", so that the process waits for activation (42).

If it is determined in step 43 that the job is not running in the user area to be executed, the job is activated (46), and then the entry in the execution order registration area 13 is advanced (45). The processing from step 41 is repeated.

On the other hand, the job B1 is ended by the subroutine return in step 74. When the job ends, the job execution management program 12
Job B1 in the job execution result message recording area 14
Record the execution result message of.

FIG. 5 shows the recording process of the job execution result message.

First, the message I of the job B1 is written in the last entry of the job execution result message recording area 14.
D and the execution result message are set (51). Then, "*" is set as the message ID of the next entry and the execution result message (52).

As described above, the registered succeeding job can be deleted due to the abnormal termination of the preceding job, and another job can be newly registered and executed as the succeeding job.

[0046]

According to the present invention, it is possible to change the execution order of jobs whose execution order is registered in advance from the job being executed,
In addition, because a new job can be added, the execution order of subsequent jobs can be changed by the user, such as when the execution order of subsequent jobs changes due to the execution results of preceding jobs. There is an effect that can be given flexibility.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration in a computer system for realizing the present invention.

FIG. 2 is a diagram showing a format of an execution order registration area 13 for registering an execution order of jobs.

FIG. 3 is a diagram showing a format of a job execution result message recording area 14 for sequentially recording execution result messages of each user job.

FIG. 4 is a diagram for explaining a job activation process in job execution management.

FIG. 5 is a diagram for explaining a recording process of a job execution result message in job execution management.

FIG. 6 is a diagram for explaining a process of changing an execution order registration area by a job execution management program.

FIG. 7 is a flowchart for explaining the operation of job B1.

[Explanation of symbols]

 1 ... Computer system, 11 ... User job execution area, 12 ... Job execution management program, 13 ... Execution order registration area, 14 ... Job execution result message recording area,

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Yasuyuki Mogi 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Inside the Software Development Division, Hitachi, Ltd. (72) Inventor Katsuo Nishihara 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Bachi Co., Ltd. Hitachi, Ltd. Software Development Division

Claims (2)

[Claims] 1. A job execution order control method for executing a job according to an execution order registered in the execution order registration means, the execution order registration means preliminarily registering the execution order of a plurality of jobs. Change means is provided for changing the execution order registered in the execution order registration means from the job, and when the execution order registration means makes a change request to the execution order registration means, the execution order registration means A job execution order control method characterized in that the registered execution order is arbitrarily changed. 2. The job execution sequence control method according to claim 1, wherein execution result message storage means for sequentially storing execution result messages of each job, and execution result message storage means for storing the execution result message storage means from the job being executed. Execution result message reference means for referring to the execution result message is provided, and when the job being executed requests a reference to the execution result message storage means, the execution result message stored in the execution result message storage means is arbitrarily referred to. Then, the job execution order control method is characterized in that the execution order registered in the execution order registration means is arbitrarily changed by using the changing means according to the content of the referred execution result message.