B.12 Limits for flexible job execution control
The following table shows the limits for executing flexible jobs in JP1/AJS3.
|
Agent |
Number of Jobs |
Maximum number |
|---|---|---|
|
Relay agent#1 |
Number of jobs per second |
1 |
|
Number of jobs concurrently running#3 |
15 |
|
|
Destination agent#2 |
Number of jobs per second |
1 |
|
Number of jobs concurrently running#3 |
10 |
|
|
Broadcast agent |
(Number of jobs x Number of broadcast-execution destination agents#4) per second |
3 |
|
Number of jobs concurrently running#5 |
10 |
|
|
Number of jobs concurrently running#5 x Number of broadcast-execution destination agents#4 |
100 |
- #1
-
If you do not use the relay agent, use the manager host.
- #2
-
If broadcast execution is used, these limit values also apply to the broadcast-execution destination agents.
- #3
-
This indicates the number of jobs that are concurrently running on the relevant agents.
- #4
-
When estimating, use the maximum number of agents that can become broadcast-execution destinations. Note that a broadcast agent can manage a maximum of 100 destination agents.
- #5
-
This indicates the number of jobs that are concurrently running on the broadcast agent.
- Cautionary notes
-
-
If you use flexible jobs, make sure that the maximum numbers shown in Table B-13 Limits for flexible job execution control are not exceeded. If a maximum number shown in the table is exceeded, a problem might occur. For example, the status of a flexible job does not change from Now running, execution performance is degraded, or a flexible job terminates abnormally.
-
All the maximum numbers shown in Table B-13 Limits for flexible job execution control are machine-based values. Because relay agents support a cluster configuration, a relay agent might have multiple logical hosts in addition to its physical host. If flexible jobs are executed on the physical host and logical hosts, make sure that the total number of jobs executed on all of these hosts does not exceed the maximum number.
-