The six queues shown in the table below are provided by default when Systemwalker Operation Manager is installed.
Standard settings are configured when Systemwalker Operation Manager is installed, so queues can be operated without any particular changes being made to the settings. The table below lists the settings that are defined in the Operating control tab of the Define Operating Information window and configured at installation.
Queue settings at installation
Registered queues |
|
Maximum number of jobs that can be executed simultaneously (Max Execution Jobs for all servers on which Systemwalker Operation Manager is installed) | 30 (Windows) 256 (UNIX) |
"queue1" is set as the default queue.
It is possible to specify the destination queue for each job or job net, but if a queue is not specified, jobs or job nets will be submitted to the default queue.
The table below lists the main settings at installation for each queue. These settings are defined in the Create/Edit Queue window.
Queue status at installation
Maximum number of jobs that can be executed simultaneously (Max Execution Jobs for a queue) |
|
Limit for job elapsed time |
|
Number of jobs that can be submitted (Total number of jobs that can exist in a queue) | No limit |
Job priority | Set to 31 by default |
Job execution priority | Not specified |
Note that when jobs are executed, they reside in memory as processes until the Max Execution Jobs setting is reached. By adjusting queue settings, such as Max Execution Jobs, it is possible to create a safe, efficient job execution environment.
For this reason, take into account factors, such as the number of jobs that will be executed by business applications, the execution time for each job, the hardware performance, and the load on servers and, if the settings need to be reviewed, consider changing the queue settings.
Designing queues
Design the queue configuration and settings in situations, such as the following:
When simultaneously executing a large number of jobs
When terminating jobs that have been running for a certain amount of time
When minimizing the impact on online job responses
When executing online jobs
Limiting the number of jobs that can be executed simultaneously
Limitations can be imposed on the number of jobs that can be executed simultaneously, both for the entire system and for jobs in queues.
The relationship between the limit defined for each differs as follows:
If the sum total of jobs executed simultaneously in queues is equal to the total number of jobs executed simultaneously on the entire system:
The actual number of jobs that are executed simultaneously on a queue is guaranteed to increase until Max Execution Jobs is reached, and this number will not be affected by the number of jobs being executed simultaneously in other queues.
If the number of jobs being executed simultaneously on another queue is less, in other words, if the number of jobs being currently executed on the entire system is less than Max Execution Jobs configured for the entire system, the queue cannot simultaneously execute more jobs than Max Execution Jobs configured for the queue.
If the sum total of jobs executed simultaneously in queues is greater than the total number of jobs executed simultaneously on the entire system:
The actual number of jobs that are executed simultaneously is not guaranteed to increase until Max Execution Jobs is reached in each queue, and this number will be affected by the number of jobs being executed simultaneously in other queues.
If the number of jobs being executed simultaneously in another queue is less, the queue can execute more jobs simultaneously compared to the case described in "a."
