5.1.3 Execution agent group
An execution agent group allows job processing to be distributed among multiple execution agents. Based on the priorities you set for the agents in the group, JP1/AJS3 determines which agent host to send each job to.
The following figure illustrates how jobs are executed using an execution agent group.
|
|
![[Figure]](GRAPHICS/ZUF05150.GIF)
You can specify an execution agent group for any of the following units:
-
Jobnet#1
-
Nested jobnet#1
-
PC job
-
Unix job
-
Flexible job#2
-
HTTP connection job#3
-
Action job
-
Custom job
Note that this applies only when Standard is selected for Exec. Service in the detailed definition of a job.
- #1
-
Event jobs do not support operations that use execution agent groups. If an event job without a specified execution agent is included in a root jobnet or nested jobnet for which an execution agent group is specified, JP1/AJS3 will attempt to use the agent group specified for the jobnet as the execution agent for the event job. If an execution agent with the same name as the agent group exists, the event job will be executed by that execution agent. If there is no execution agent with the same name as the agent group, an error occurs and the following message is output to the integrated trace log: KAVT0403-E The specified agent is not defined in the job execution environment. (host=agent-host-name, maintenance-information). Therefore, if you want to specify an execution agent group for a root jobnet or nested jobnet, make sure that an execution agent is explicitly specified for the event job in the jobnet.
- #2
-
For flexible jobs, replace execution agent with relay agent.
- #3
-
The service for executing HTTP connection jobs is fixed to Standard.