Job Management Partner 1/Automatic Job Management System 3 Overview

5.3.9 Distributing jobs among execution hosts (agent hosts)

Organization of this subsection

(1) Distributing jobs among execution agents in an execution agent group

(2) Error detection and job distribution to execution hosts (agent hosts)

(1) Distributing jobs among execution agents in an execution agent group

You can connect multiple execution agents with assigned priorities within an execution agent group. Jobs can then be distributed to the execution agents in accordance with the specified priorities. This functionality applies to Unix jobs, PC jobs, action jobs, and custom jobs. Queueless jobs cannot be distributed among execution agents.

Specify the execution agent priorities to suit your system operation. If you assign different priorities, each job will be sent for execution to the execution agent that has the highest priority. When that agent's usage rate^# reaches 100%, the next job is sent to the agent that has the next highest priority. For example, if the execution agent with the highest priority is already fully occupied or is in failed or stopped state and cannot run the job, the execution agent with the next highest priority can run it instead. Setting different priorities is useful for this type of system operation.

If you set the same priority for each execution agent, each job will be sent to the execution agent that has the lowest agent usage rate. If no particular execution agent takes precedence, jobs are distributed evenly among the execution agents. Setting identical priorities is useful for this type of load-balancing system.

#

Agent usage rate is the ratio of active jobs to the maximum number of concurrently executable jobs at an execution agent. It is given by the following equation, rounded to four decimal points:

Agent usage rate = number of active jobs / maximum number of concurrently executable jobs

Cautionary note

When two or more execution agents have the same priority and usage rate, the execution agent with the highest agent ID^# is selected by default to execute the job. For example, if the jobs are short and quickly completed, the execution agent's usage rate hardly increases and differs only slightly from that of other execution agents.

Consequently, because jobs are always assigned to the execution agent having the highest agent ID, that agent executes more jobs than the others, resulting in asymmetric system usage. In such situations, you can distribute jobs more uniformly if, instead of the agent ID method, you set a job distribution method that prioritizes the execution agent that has not been used for the longest time.

For details, see 6.2.9 Setting the method for determining the agent host to which a job will be delivered in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (Windows) or see 14.2.9 Setting the method for determining the agent host to which a job will be delivered in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (UNIX).

#

Agent IDs are assigned internally as each execution agent is registered, in ascending order of the unused IDs. When execution agent hosts are displayed by the ajsagtshow command, they are listed in ascending order of their agent IDs.

For the ajsagtshow command syntax, see ajsagtshow in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(2) Error detection and job distribution to execution hosts (agent hosts)

In the following two cases, there may be a delay of up to 15 minutes in distributing jobs to execution hosts that are operating normally. During this period, the jobs remain in Now queuing status:

When a failure occurs simultaneously on three or more agent hosts

When three or more agent hosts have stopped

In such cases, restart the affected execution agent hosts.

[Contents][Back][Next]

[Trademarks]