2.5.4 Maximum number of concurrently executable jobs
In JP1/AJS3, you can set the maximum number of jobs that an agent host can execute concurrently. When this maximum is reached, subsequent jobs are placed in a wait status. By setting a maximum number of concurrently executable jobs, you can distribute the load during set time periods, or among multiple agent hosts when more than one agent host is connected.
The maximum number of concurrent jobs must be specified per execution agent. You cannot perform this setting for an execution agent group. The setting applies to Unix jobs (other than queueless jobs), PC jobs (other than queueless jobs), flexible jobs, HTTP connection jobs, action jobs, custom jobs, and Passing information settings jobs.
For the procedure and notes on setting a maximum number of concurrently executable QUEUE jobs and submit jobs, see 7.1.1(4) Notes on the execution environment required for QUEUE jobs and submit jobs.
- Organization of this subsection
(1) Notes on setting a maximum number of concurrently executable jobs
The following provides notes on setting a maximum number of concurrently executable jobs:
-
You can set and change the maximum number of concurrently executable jobs using the ajsagtadd command or ajsagtalt command. To check the current setting, use the ajsagtshow command. You can also perform these operations from JP1/AJS3 - Web Console.
If you add an execution agent using the ajsagtadd command, but do not specify a maximum number of concurrently executable jobs, the default setting 00:00-00:00=5 (maximum of five concurrent jobs, 24 hours a day) is assumed.
The default setting will suffice if only short jobs are executed, and no more than a few jobs will be registered for execution simultaneously. However, if you execute jobs with long execution times or register many jobs at the same time, the number of concurrent jobs will quickly reach the maximum, and remain there for extended periods of time. This might affect the execution of subsequent jobs.
When the maximum number of concurrently executable jobs is reached on an agent host, subsequent jobs are made to wait in the queuing status until the active jobs finish. In such cases, jobs will take longer than expected to execute. Take the job execution time and the number of jobs executed per unit time into consideration when you set the maximum number of concurrently executable jobs.
-
The maximum number of concurrently executable jobs you specify applies to each execution agent. If different execution agents are mapped to the same execution host, the sum of the maximum number of concurrently executable jobs specified for these execution agents is set for the jobs that will be executed on that execution host.
As an example, take the addition of an execution agent that uses the local host name and whose maximum number of concurrently executable jobs is set to 00:00-00:00=10 (maximum of 10 concurrent jobs, 24 hours a day). In this case, because the maximum number of concurrently executable jobs for the default execution agent is 00:00-00:00=5 (maximum of five concurrent jobs, 24 hours a day), a maximum of 15 jobs could be executed concurrently.
When you specify a maximum number of concurrently executable jobs, specify a value appropriate for the execution host.
(2) Checking whether the maximum number of concurrent jobs has been reached when jobs remain in queuing status
When the number of active jobs on an agent host reaches the maximum number of concurrently executable jobs, subsequent jobs might remain in the queuing status for a long time before being executed. To check whether the maximum number of concurrently executable jobs has been reached, execute the ajsagtshow command and compare the number of active jobs (JOB) against the maximum number of concurrently executable jobs (CON-EXE). For details about the ajsagtshow command, see ajsagtshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference. Note that you can also perform this operation from JP1/AJS3 - Web Console.
By setting up JP1/AJS3 to output the following message to the integrated trace log when the maximum number of concurrent jobs is reached and no more jobs can be registered for execution, you can check whether this is the reason for execution delays.
KAVU4310-I The number of executing jobs reaches the concurrently-executable-job-limit (maximum-number-of-concurrently-executable-jobs) at the agent. (agent-host-name) (host name: host-name, job number: job-number)
For details about how to perform this setting, see the following descriptions:
- In Windows:
-
6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the JP1/Automatic Job Management System 3 Configuration Guide
- In UNIX:
-
15.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the JP1/Automatic Job Management System 3 Configuration Guide