JP2009282577A - Job management apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enhance job processing efficiency in a state that a complex instruction is intensively inputted in a short time. <P>SOLUTION: A job management apparatus registers a plurality of jobs concerning the complex instruction in a preparation area 260 when a user inputs the complex instruction, changes the registration of the performable jobs among the jobs of the preparation area 260 from the preparation area 260 to a standby area 270, and selects a job performed from the jobs of the standby area 270 so as to perform the job. The job which is newly brought into a state that the job becomes performable after the performance of the former job is changed in registration from the preparation area 260 to the standby area 270. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a business information system, and more particularly to a technique for improving job execution efficiency.

  Business information systems that support the operation of companies and public facilities, so-called enterprise systems, are now the foundation of organizations of various sizes. The business information system supports complicated organization management by outputting higher value-added information after totaling, accumulating, analyzing and processing data obtained from node terminals and databases.

  A business information system is often modeled as a collection of jobs. A job is a basic execution unit in the system, such as a database update process and a calculation process for data obtained from each node terminal. Depending on the business information system, the number of jobs can range from thousands to tens of thousands.

Various “commands” are input to the business information system. Some instructions can be completed simply by executing one job (hereinafter referred to as “single instruction”), while other instructions that can be executed continuously by multiple jobs (hereinafter referred to as “compound instructions”). There is also.
JP 2002-358224 A JP 2006-268507 A JP 2007-265029 A

  Furthermore, there are commands that are executed periodically (hereinafter referred to as “periodic commands”), and commands that are executed irregularly based on user instructions or the like (hereinafter referred to as “irregular commands”). There is also. In the case of a business information system that supports irregular commands, if a large number of irregular commands are input in a short period of time, it is necessary to temporarily execute a large number of jobs, so that the processing load tends to increase rapidly. In particular, when many compound instructions are input in a short period of time, such a problem is likely to be manifested.

  The present invention has been completed in view of the above-mentioned problems, and its main object is to improve the job processing efficiency in a situation where instructions, particularly compound instructions, are input in a concentrated manner in a short period of time. , To provide.

One embodiment of the present invention relates to a job management apparatus.
When a composite command is input from a user, this apparatus registers a plurality of jobs related to the composite command in the preparation area, and jobs that are in an executable state among jobs in the preparation area are transferred from the preparation area to a predetermined standby area. Change the registration, select the job to be executed from the jobs in the standby area, and execute it. Jobs that are newly executable after job execution are registered and changed from the preparation area to the standby area.

  It should be noted that any combination of the above-described components, and the present invention expressed by a method, system, recording medium, and computer program are also effective as an aspect of the present invention.

  According to the present invention, it becomes easy to improve job processing efficiency in a situation where compound instructions are concentrated and input in a short time.

FIG. 1 is a schematic diagram of asset management work.
Hereinafter, an embodiment of the present invention will be described based on a business information system for supporting asset management business. The asset management business in the present embodiment is a business that obtains commission income from a customer by depositing the customer's asset and managing the asset on behalf of the customer. The asset management staff is broadly divided into “front office” and “back office”.

  The front office analyzes financial market trends and determines asset management policies. The back office executes financial transactions in accordance with instructions from the front office. For example, when the front office staff instructs the back office to increase the stock B purchase by the account of the customer A, the back office staff issues a buy order for the stock B via the asset management system 200. The asset management system 200 is a business information system for supporting various back office operations such as ordering stocks, calculating operational results, and creating reports for sending to customers.

FIG. 2 is a hardware configuration diagram of the asset management system 200.
The asset management system 200 includes a job management device 100, a job execution device group 220, and an external storage device 210. The job management device 100, the job execution device group 220, and the external storage device 210 are connected to each other via a communication network.
The job management apparatus 100 causes the job execution apparatus group 220 to execute each job. The job execution device group 220 includes a plurality of job execution devices 202. Each job execution device 202 executes the job assigned from the job management device 100. The job management apparatus 100 may assign a job to one of the job execution apparatuses 202 according to a predetermined assignment rule. Alternatively, jobs may be preferentially assigned to job execution devices 202 that are lighter in processing load than other job execution devices 202 so that the processing load of each job execution device 202 is leveled.
The program constituting the job may be held in advance by the job execution apparatus 202. Alternatively, a program may be downloaded from the job management apparatus 100 to the job execution apparatus 202 when a job execution instruction is given. The job execution apparatus 202 appropriately notifies the job management apparatus 100 of the job execution state.

  The external storage device 210 stores various data for business. The job execution device 202 sends and receives data to and from the external storage device 210 when executing a job. Further, the job execution device 202 executes a job based on data acquired from the external storage device 210 or data acquired from another database (not shown), a node terminal, or the like.

  In summary, the job execution device 202 executes various jobs using the data in the external storage device 210 as a variable. The job management device 230 controls job execution timing based on the execution conditions of each job. As described above, the entire asset management system 200 is operated by executing a plurality of jobs according to the schedule based on the data obtained from the external storage device 210.

FIG. 3 is a diagram illustrating job dependency in an operation result calculation instruction.
The back office inputs various commands to the asset management system 200, more specifically, the job management apparatus 100. Among these, an instruction for instructing calculation of an operation result for a specific customer (hereinafter referred to as an “operation result calculation instruction”) is an instruction realized by cooperation of a plurality of jobs, that is, a “composite instruction”. It is.

The operation result calculation instruction is composed of the following five jobs.
Job 1 (J1): A stock transaction by a customer acquired from the external storage device 210 is converted into a transaction history format.
Job 2 (J2): Stock attribute information is acquired from the external storage device 210 (file or the like) and recorded in the external storage device 210 (database or the like). The attribute information is information indicating an attribute change of a stock brand based on a stock exchange or a stock split in a corporate merger.
Job 3 (J3): Refers to the transaction history acquired in job 1, and calculates the number of stocks held and the average acquisition unit price. Further, the attribute information acquired in job 2 is referred to, and the number of held brands and the average acquisition unit price are corrected based on the events that have occurred in the owned brands.
Job 4 (J4): The current price information of the stocks is acquired from the external storage device 210 (file or the like) and recorded in the external storage device 210 (database or the like).
Job 5 (J5): Based on the number of owned brands calculated in job 3 and the average acquisition unit price, and the market price information acquired in job 4, the customer asset is evaluated for market value, and an operation result file is generated.
The back office transmits the generated operation result file to the front office or the like. A process in which the above five jobs are continuously executed in accordance with an operation result calculation instruction is referred to as an “operation result calculation process”.
Hereinafter, a process in which a plurality of jobs are continuously executed according to a composite instruction, such as an operation result calculation process, is referred to as “composite process”.

  Job 5 is executed on condition that job 3 and job 4 are completed. Hereinafter, the job B having “execution completion of job A” as an execution start condition is referred to as “following job” of job A. Job A is also referred to as “preceding job” of job B. In the case of FIG. 3, job 3 and job 4 are preceding jobs for job 5. Job 1 and job 2 are preceding jobs for job 3.

  The job management apparatus 100 causes the job execution apparatus 202 to execute executable jobs one after another while determining whether or not each job can be executed according to job dependency and job execution status. According to the figure, job 1, job 2 and job 4 have no preceding job. Therefore, execution of job 1, job 2, and job 4 can be started at any time. Hereinafter, such a job having no preceding job is referred to as a “first job”.

FIG. 4 is a data structure diagram of the job relation information 240 for setting the job dependency shown in FIG.
In the job relation information 240, the target job column 254 shows five jobs 1 to 5 shown in FIG. The preceding job column 256 indicates the preceding job of each job shown in the target job column 254. According to the figure, job 1, job 2, and job 4 have no preceding job. For this reason, these jobs are the top jobs. The preceding jobs of job 3 are job 1 and job 2. The preceding jobs of job 4 are job 3 and job 4. In the job relationship information 240, dependency relationships between jobs are defined in this format.

  The job management apparatus 100 refers to the job relation information 240 to select the first job or a job for which all of the preceding jobs have been completed as a “job in an executable state” and execute it to the job execution apparatus 202. Instruct.

  The processing time for compound instructions tends to be much longer than that for a single instruction. For this reason, the job management apparatus 100 asynchronously executes “process related to user interface” and “process related to job execution”. For example, when an operation result calculation instruction is input, the job management apparatus 100 first executes an operation result calculation process as a background process. For example, jobs 1, 2, 3, 4, and 5 are sequentially executed from jobs that can be executed. Since the operation result calculation process is executed in the background, a new command can be accepted after the job 1 is started. During operation result calculation processing for customer A, operation result calculation instructions for customers B and C can be input.

  In the following, first, general processing steps and problems of composite processing will be pointed out with reference to FIGS. Then, with reference to FIG. 8 and subsequent figures, a processing method of the composite processing in this embodiment will be described.

FIG. 5 is a flowchart showing a first method, which is a general process of composite processing.
The composite processing method shown in FIG. 5 is called a “first method”. Here, a description will be given assuming that two compound instructions are continuously input. First, the job management apparatus 100 receives a composite command as a UI (user interface) process (S10), and registers a job to be executed by this composite command (S12). In the case of the operation result calculation process, the above-described jobs 1 to 5 are registered. The job management apparatus 100 executes job processing as a separate process from the UI processing. The UI process of the job management apparatus 100 instructs the job process to execute the composite process (S14). Since the job process is executed as a background process of the UI process, the UI process can accept the next instruction after the instruction in S14.

  When a new composite instruction is received (S16), a job for this composite instruction is registered (S18), and execution of composite processing is instructed (S20). Hereinafter, the compound instruction received in S10 is referred to as a “first instruction”, and the compound instruction received in S16 is referred to as a “second instruction”. In the job processing, first, composite processing based on the first command is executed (S30), and when the composite processing is completed, the completion notification is sent to the input person of the first command (S32). Next, the job processing executes composite processing based on the second command (S40), and notifies the person who entered the second command of completion after completion of the composite processing (S42).

FIG. 6 is a flowchart showing detailed processing steps of the composite processing in S30 and S40 of FIG.
Among the jobs to be executed registered in S12 and S18, jobs that are in an executable state are selected (S44), and the selected job is executed by the job execution apparatus 202 (S46). If the composite process is not completed (N in S48), the process returns to S44 and the job to be executed next is selected. If the combined process is completed (Y in S48), the completion of the combined process is notified as shown in S32 and S42 of FIG.

Such a processing method has the following problems.
D1. The time from inputting a compound instruction to receiving a completion notice tends to be excessively long.
The input person of the 2nd command must wait for the compound processing based on the 1st command. In FIG. 5, the composite processing based on the second command (S40) is not started unless the composite processing based on the first command (S30) is completed. When composite commands are continuously input after the second command, the time until the last input person receives a completion notification may be very long.
D2. The readability of the program is bad.
As shown in S44 of FIG. 6, “a process for specifying an executable job (hereinafter referred to as“ standby job ”)” and “a process for specifying a job to be executed (hereinafter referred to as“ execution job ”). Is integrated. For this reason, it becomes difficult to distinguish the corresponding part of the “process for specifying the standby job” and the corresponding part of the “process for specifying the execution job” in the program code. Initially, even if both parts are clear on the code, both parts may be mixed as a result of many years of maintenance work.

FIG. 7 is a flowchart showing a second method, which is a general process of composite processing.
The composite processing method shown in FIG. 7 is referred to as a “second method”. Here, the description will be made on the assumption that two compound instructions are continuously input. First, the job management apparatus 100 receives a composite command (first command) as UI processing (S10), and registers a job to be executed by this composite command (S12). The job management apparatus 100 starts the first job process as a process separate from the UI process. The UI processing of the job management apparatus 100 instructs the first job processing to execute the composite processing for the first command (S14). After the instruction, the UI process can accept the next instruction. The first job process starts composite processing based on the first command (S30).

  When a new compound instruction (second instruction) is received as UI processing (S16), a job for this compound instruction is registered (S18). The job management apparatus 100 activates the second job process as a separate process from the UI process and the first job process. The UI processing of the job management apparatus 100 instructs the second job processing to execute the composite processing for the second command (S20). The second job process starts a composite process based on the second command (S40). The processing content of the composite processing (S30, S40) is the same as the content described in relation to FIG.

  Unlike the first method, in the second method, the composite processing based on the first instruction and the composite processing based on the second instruction are executed simultaneously and in parallel as separate processes. The first job process and the second job process notify the UI process of completion after completion of the respective composite processes (S32, S42).

  According to the second method, the input person of the second command does not have to wait for completion of the composite processing based on the first command. For this reason, the problem D1 pointed out about the first method can be solved to some extent. However, if a large number of compound instructions are input in a short period of time, a large amount of job processing is started, and the overhead associated with starting the job processing increases. Also, the problem D2 remains.

FIG. 8 is a schematic diagram of composite processing in this embodiment.
First, in this embodiment, two recording areas, a preparation area 260 and a standby area 270, are prepared. Each area is a recording area in which a job, more specifically, a job ID for uniquely identifying the job is temporarily registered. The standby area 270 is formed as a recording area having a queue structure based on FIFO (First-In First Out) as a basic principle.

In the present embodiment, mainly three processes of a preparation registration process (P1), a standby registration process (P2), and an execution control process (P3) are executed in parallel.
Preparation registration process (P1): A composite command is received from the back office. A job to be executed by a composite instruction is registered in the preparation area 260. Such a “job to be executed” is called a “preparation job”. For example, it is assumed that an operation result calculation command A for the customer A, an operation result calculation command B for the customer B, and an operation result calculation command C for the customer C are input. In the preparation registration process, a preparation job group 280a related to the operation result calculation instruction A, a preparation job group 280b related to the operation result calculation instruction B, and a preparation job group 280c related to the operation result calculation instruction C are registered in the preparation area 260. . The preparation registration process is executed in the same process as the UI process.

  Standby registration process (P2): Among the preparation jobs registered in the preparation area 260, a job in an executable state is identified, and the registration is changed to the standby area 270 as a “standby job”. The “standby job” is specified by referring to the job relation information 240 for each preparation job group 280. In the standby registration process (P2), a standby job is selected regardless of the input order of operation result calculation instructions. In the case of the figure, job 2 related to the operation result calculation instruction B, job 2 and job 4 related to the operation result calculation instruction A are moved from the preparation area 260 to the standby area 270 as standby jobs.

  Execution control process (P3): The standby jobs registered in the standby area 270 are extracted in order, and are executed by one of the job execution apparatuses 202 as an “execution job”. When execution of the execution job is completed, completion notification is sent to the preparation registration process (P1) and the standby registration process (P2).

The standby registration process (P2) periodically checks the preparation area 260, and selects a preparation job in an executable state as a standby job regardless of the order in which the preparation jobs are registered in the preparation area 260. When there is no preparation job in the preparation area 260, or when no preparation job becomes a standby job, the standby registration process (P2) sleeps.
The execution control process (P3) also periodically checks the standby area 270 and executes the execution job based on the order in which the standby jobs are registered in the standby area 270 regardless of the order in which the preparation jobs are registered in the preparation area 260. Select. When there is no standby job in the standby area 270, the execution control process (P3) sleeps.
As described above, the roles of the process for registering a preparation job (P1), the process for selecting a standby job (P2), and the process for selecting an execution job (P3) are clarified. Based on the contents of the H.270, it is configured to cooperate gently.

According to such a processing method, the above-described problems D1 and D2 can be solved.
In the standby registration process (P2), an executable job is selected as a standby job regardless of the reception order of the composite instruction. For example, when it takes time to execute job 3 with respect to the first instruction and job 5 that is a subsequent job cannot be executed, the standby registration process (P2) selects a standby job from the preparation jobs for the second instruction. Just choose. For this reason, the composite process based on the second instruction does not need to wait for the completion of the composite process based on the first instruction.

  Further, even when compound instructions are concentrated in a short time, it is not necessary to start a large number of “processes” unlike the second method. Even if the preparation registration process (P2) receives a large number of compound instructions, the standby registration process (P2) and the execution control process (P3) select the standby job and the execution job one by one, and the large number of preparation jobs are sequential. Executed. In other words, since it is a method of sequentially selecting a job that can be executed from a large number of preparation jobs, it is not necessary to start a process every time a composite instruction is input.

  By clearly separating the “process for specifying the standby job” and the “process for specifying the execution job” as the standby registration process (P2) and the execution control process (P3), respectively, in the program structure, the code of each process Are difficult to mix. For example, even if it is necessary to change an algorithm for specifying a standby job, it is difficult to change a code corresponding to the execution control process (P3), so that the business information system has excellent readability and maintainability. It is easy to realize.

FIG. 9 is a functional block diagram of the job management apparatus 100.
Each block shown here can be realized in hardware by an element such as a CPU of a computer or a mechanical device, and in software it is realized by a computer program or the like. Draw functional blocks. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software.

The job management apparatus 100 includes a UI (user interface) unit 110, a data processing unit 120, and a data holding unit 130.
The UI unit 110 is responsible for processing related to the entire user interface, such as input processing from the back office and information display for the back office.
The data processing unit 120 executes various data processing based on data acquired from the UI unit 110, the data holding unit 130, the job execution device group 220, the external storage device 210, or the like. The data processing unit 120 also serves as an interface between the UI unit 110 and the data holding unit 130.
The data holding unit 130 stores various setting data prepared in advance and data received from the data processing unit 120.

UI unit 110:
The UI unit 110 includes a command receiving unit 112 and a state notification unit 114. The command receiving unit 112 receives various commands from the back office. The status notification unit 114 notifies the back office of the job execution status. The notification state of the execution state will be described later in detail with reference to FIG.

Data holding unit 130:
The data holding unit 130 includes a preparation job holding unit 132, a standby job holding unit 134, and a job execution state holding unit 136. The preparation job holding unit 132 is a recording area corresponding to the preparation area 260. The standby job holding unit 134 is a recording area corresponding to the standby area 270. The job execution state holding unit 136 holds “execution state information” indicating the execution state of each job.

Data processing unit 120:
The data processing unit 120 includes a preparation registration unit 122, a standby registration unit 124, and an execution control unit 126. The preparation registration unit 122 executes preparation registration processing (P1) in the same process as the UI unit 110. The standby registration unit 124 executes standby registration processing (P2). The execution control unit 126 executes an execution control process (P3).

FIG. 10 is a flowchart showing the processing steps in this embodiment of the composite processing.
Here, the description will be made on the assumption that two compound instructions are continuously input. The command receiving unit 112 receives the composite command (first command) (S10), and the preparation registration unit 122 registers the job to be executed by the first command in the preparation job holding unit 132 as a preparation job (S12). The command receiving unit 112 further receives a composite command (second command) (S16), and the preparation registration unit 122 registers a job to be executed by the second command in the preparation job holding unit 132 as a preparation job (S18).

  As a loop process separate from the instruction receiving unit 112 and the preparation registration unit 122, the standby registration unit 124 executes a standby registration process (P2) shown in S50 to S54. First, the standby registration unit 124 determines whether there is a preparation job in the preparation job holding unit 132 (S50). If no preparation job is registered (N in S50), a standby job is newly created for a predetermined period of time. Sleep until registered. If the preparation job is registered (Y in S50), the standby registration unit 124 refers to the job relation information and determines whether there is an executable preparation job (S52). If there is an executable preparation job (Y in S52), the preparation job holding unit 132 changes the registration to the standby job holding unit 134 as a standby job (S54). If there is no executable preparation job (N in S52), the standby registration unit 124 sleeps for a predetermined time or until a newly executable preparation job is detected.

  As a loop process that is separate from the preparation registration unit 122 and the standby registration unit 124, the execution control unit 126 executes an execution control process (P3) shown in S56 to S64. First, the execution control unit 126 determines whether there is a standby job in the standby job holding unit 134 (S56). If no standby job is registered (N in S56), a new standby job is generated for a predetermined time. Sleep until registered. If a standby job is registered (Y in S56), the execution control unit 126 takes out one standby job by the FIFO method and instructs the job execution apparatus 202 to execute it (S58). In addition, the registered standby job is unregistered from the standby job holding unit 134 (S60). At this time, the execution state information of the job execution state holding unit 136 is updated. By updating the execution state information, the standby registration unit 124 may detect a preparation job that can be newly executed.

When any composite processing is completed by executing the job (Y in S62), the user who has requested the composite processing is notified of the completion of the composite processing (S64). When the combined process is not completed (N in S62), S64 is skipped and the process returns to S56.
As described above, the three processes are executed in cooperation with each other via the preparation area 260 and the standby area 270 while being asynchronously executed.

FIG. 11 is a screen diagram of the status notification screen 290.
The status notification unit 114 causes the status notification screen 290 to be displayed on the screen used by the terminal used by the person who inputs the composite command. For example, when the staff A with the back office inputs an operation result calculation command for the customer B to the job management apparatus 100, the status notification unit 114 displays the dependency relationship of the jobs 1 to 5 constituting the operation result calculation process. Display. Then, the status notification unit 114 appropriately updates the display content of the status notification screen 290 while referring to the registration contents of the preparation job holding unit 132 and the standby job holding unit 134 and the execution status information of the job execution status holding unit 136. To do. In the case of the figure, job 1 and job 2 are completed, job 3 is a standby job, job 4 is an execution job, and job 5 is a preparation job.
Through the status notification screen 290, the input person of the composite command can check the job dependency related to the composite command and its execution status on the screen.

The job management apparatus 100 has been described above based on the embodiments.
According to the job management apparatus 100, the standby registration process (P2) and the execution control process (P3) can be clearly separated in the program structure. Therefore, even when a large number of jobs need to be temporarily executed due to a large number of compound instructions being input in a short period of time, it is easy to execute these jobs sequentially. It is also effective for improving the readability of the program. Program readability is particularly important for business information systems that have been operating for years or decades.

Since the standby registration process and the execution control process are executed simultaneously in parallel, there is no need to wait for the completion of the preceding compound instruction when executing a certain compound instruction. Moreover, even when a large number of compound instructions are input in a short period of time, it is not necessary to start a large number of processes as in the second method, so that overhead can be suppressed. The standby registration process and the execution control process may be executed on different CPUs.
Further, the job execution status is appropriately displayed on the status notification screen 290. Even after requesting the composite process, the user can appropriately check the progress of the composite process, so that his / her work can be easily scheduled. In addition, the execution control process can be simplified by forming the standby area 270 as a queue structure.

  The present invention has been described based on the embodiments. The embodiments are exemplifications, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are within the scope of the present invention. .

It is a schematic diagram of asset management business. It is a hardware block diagram of an asset management system. It is a figure which shows the dependence relationship of the job in an operation result calculation instruction. FIG. 4 is a data structure diagram of job relationship information for setting job dependency relationships shown in FIG. 3. It is a flowchart which shows the 1st method which is a general process of a composite process. It is a flowchart which shows the detailed process process of the composite process in S30 and S40 of FIG. It is a flowchart which shows the 2nd method which is a general process of a composite process. It is a schematic diagram of the composite process in a present Example. It is a functional block diagram of a job management apparatus. It is a flowchart which shows the process in the present Example of a composite process. It is a screen figure of a status notification screen.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 Job management apparatus, 110 UI part, 112 Command receiving part, 114 Status notification part, 120 Data processing part, 122 Preparation registration part, 124 Standby registration part, 126 Execution control part, 130 Data holding part, 132 Preparation job holding part, 134 standby job holding unit, 136 job execution state holding unit, 200 asset management system, 202 job execution device, 210 external storage device, 220 job execution device group, 240 job related information, 254 target job column, 256 preceding job column, 260 Preparation area, 270 Standby area, 280 Preparation job group, 290 Status notification screen.

Claims (8)

An instruction realized by a plurality of jobs whose dependencies are determined so that one or more jobs corresponding to the subsequent stage are executed on condition that one or more jobs corresponding to the preceding stage are executed is defined as a compound instruction. A compound instruction acquisition unit for detecting an input;
A preparation registration unit that registers the plurality of jobs in a predetermined preparation area when the composite instruction is input;
The job relation information that defines the dependency relation of the plurality of jobs is referred to, a job in an executable state is identified from among the plurality of jobs, and the specified job is registered and changed from the preparation area to a predetermined standby area. A standby registration unit;
An execution control unit that selects a job to be executed from jobs registered in the standby area, and executes the selected job;
The preparation registration unit changes the registration of a job that is newly executable after the execution of the job from the preparation area to the standby area.   The process for specifying a job in a state where the standby registration unit can be executed and the process for selecting a job to be executed by the execution control unit are executed in parallel in time. The job management apparatus according to 1. In a situation where the second compound instruction is input by the second user after the first compound instruction is input by the first user,
The standby registration unit can change the registration of a job based on the second composite instruction from the preparation area to the standby area in preference to a job based on the first composite instruction. Or the job management apparatus of 2.   The job management apparatus according to claim 3, wherein the execution control unit is capable of executing a job based on the second composite instruction in preference to a job based on the first composite instruction.   The standby registration unit refers to the job-related information, and determines that a job for which a job corresponding to the previous stage does not exist or a job for which a job corresponding to the previous stage has been executed is in an executable state. The job management apparatus according to any one of 1 to 4.   The job management apparatus according to claim 1, further comprising a state notification unit that displays a screen on which a job execution state based on the composite instruction is displayed.   7. The job management apparatus according to claim 1, wherein the standby area is configured as a queue structure in which jobs to be executed are selected in the order of registration. An instruction realized by a plurality of jobs whose dependencies are determined so that one or more jobs corresponding to the subsequent stage are executed on condition that one or more jobs corresponding to the preceding stage are executed is defined as a compound instruction. Processing to detect input;
Processing for registering the plurality of jobs in a predetermined preparation area when the composite command is input;
The job relation information that defines the dependency relation of the plurality of jobs is referred to, a job in an executable state is identified from among the plurality of jobs, and the specified job is registered and changed from the preparation area to a predetermined standby area. Processing,
A process of selecting a job to be executed from jobs registered in the standby area and executing the selected job;
To the computer,
A job management program that changes a registration of a job that is newly executable after execution of the job from the preparation area to the standby area.

Images