B.8 Limits for the event/action control
The following table lists the limits for executing event jobs in JP1/AJS3.
|
Item |
Maximum |
|---|---|
|
Number of event jobs (including those set in start conditions) that can be concurrently registered for execution or forcibly terminated on an agent host from one or more manager hosts |
1,000#1 |
|
Number of event jobs (including those set in start conditions) that can be concurrently registered for execution or forcibly terminated on multiple agent hosts from one manager host |
4,000#1 |
|
Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host |
1,000#1 |
|
Maximum number of event jobs (including those set in start conditions) that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host, per scheduler service |
4,000#1 |
|
Maximum number of event jobs (including those set in start conditions) that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host, per manager host |
80,000#1 |
|
Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the restart process of a JP1/AJS3 service on an agent host, per agent host |
1,000#1 |
|
Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the execution of the jajs_maintain command with the -F option specified |
-- |
|
Maximum number of event jobs (including those set in start conditions) that can continue to run through the execution of the jajs_maintain command with the -F option specified per scheduler service |
-- |
|
Maximum number of event jobs (including those set in start conditions) that can continue to run through the execution of the jajs_maintain command without the -F option specified per manager host |
-- |
|
Number of ajskill or ajsintrpt commands that can be executed consecutively on event jobs (including those set in start conditions) |
4,000#1, #2 |
|
Number of Monitoring Log Files jobs that can be executed concurrently on one execution host |
150#3 |
|
Number of email reception monitoring job that can be executed concurrently on one execution host |
60 |
- Legend:
-
--: Not applicable
- #1
-
The value when no events have occurred. If events are likely to occur at the same time, configure the system so that the maximum value, counting events and event jobs, will not be exceeded.
If the maximum is exceeded, and an operation is performed on an event job, or an event job (including an event job in a start condition) detects the monitored event, the following issues might occur:
-
Event jobs registered for execution (including those in start conditions) remain in queuing status.
-
Active event jobs, and jobnets with start conditions that JP1/AJS3 is monitoring, fail to end when killed.
-
Event jobs (including those in start conditions) do not detect monitored events.
Be aware of these issues, but note that in some high-performance environments, exceeding any of the limits might not cause problems.
These issues are due to the high volume of communication that takes place in the processing of a large number of jobs. For details about what causes the issues and recovery procedures, see 7.6.8 Notes on restarting the JP1/AJS3 service while event jobs are running in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
-
- #2
-
Executing these commands consecutively over a short duration results in a high volume of communication. If the maximum value is exceeded, the issues in #1 above might occur. For details about what causes the issues and recovery procedures, see 7.6.8 Notes on restarting the JP1/AJS3 service while event jobs are running in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
- #3
-
This is the maximum value under the following conditions:
-
The Monitoring Log Files jobs run under Windows.
-
Each Monitoring Log Files job monitors one log file only.
-
Log files are monitored by Monitoring Log Files jobs only, not in conjunction with the JP1/Base log file trapping function.
In UNIX, when one Monitoring Log Files job monitors multiple log files, or is used in conjunction with the JP1/Base log file trapping function, estimate the number of Monitoring Log Files jobs that can be executed based on the number of log files that can be monitored by the log file trapping function. For details, see the JP1/Base User's Guide.
-