4.2.3 Procedure for executing the batch applications using the scheduling functionality
This subsection describes the procedure for executing batch applications.
If you use the scheduling functionality, the batch applications executed on batch servers are differentiated by job IDs. A Job ID is a string used for differentiating execution requests for the batch applications to be executed. You can specify any value when executing a command. If you omit a job ID while executing a command, the scheduling functionality automatically generates a job ID. This Job ID is managed by CTM.
A batch server group, to which batch applications are distributed using CTM, is called a schedule group. A schedule queue is created for respective schedule groups. Specify the schedule group, if you want to control the number of concurrent operations for respective business classifications of batch applications. Set up a unique schedule group in a system. You must set up the schedule groups separately even if CTM is different for each machine. When specifying the schedule groups, you must specify with the batch execution commands and on the batch servers. For details on how to perform settings, see 4.7 Settings of the execution environment.
Even when you use the scheduling functionality, you can integrate the execution environment of batch applications with JP1/AJS.
The following figure shows the flow of execution of batch applications by using the scheduling functionality.
|
|
In this figure, the batch application execution requests are distributed from batch server 1 through batch server 3, which belong to the same schedule group, by using CTM. The batch application execution requests which overflow from the schedule queue give an error.
The following figure shows the flow of execution of batch applications by using multiple schedule groups.
|
|
This figure shows an example where two schedule groups GroupA and GroupB are specified, and two schedule queues are created. You use a command to define the schedule group to be used. The batch applications are distributed to schedule queues according to the schedule group settings of the command. In this figure, batch applications are running on batch servers of schedule groups, so the batch applications received by CTM are on standby in a schedule queue.