A JAMS Queue provides a temporary holding place for pending Jobs and Setups on a first-in-first-out basis. Queues can be assigned to Jobs, Setups and Folders.
Queues are either in a started or stopped state and can be set to run multiple jobs simultaneously. To enhance load balancing capabilities you can also specify what node a Queue is started on.
![]() |
Note: Defining and using Queues in JAMS is optional. |
To define a new Queue, follow the steps below:
Queues can be modified by accessing its definitions window.
![]() |
Note: An Agent node name in a Job definition overrides an Agent node name in a Queue definition. However, the Job still runs on the assigned Queue and adheres to any Job Limit settings defined within the Queue. |
When a Job is waiting for a Queue Job limit slot it cannot execute. However, you can manually start a Queue by right-clicking the Queue’s context menu from the Queue Definitions View and choosing the Start command. Conversely, you can select the Stop command to manually halt the Queue.
While there are similarities between Batch Queues and Resources there are some significant differences that are spelled out below.
A Batch Queue is defined by the number of concurrent Job executions and Job limitation settings.
When submitting a Job, a Batch Queue can be adjusted, but a Resource cannot.
A Resource definition is based on the total number of unit quantities available. As these Jobs run they consume the available units that are released upon completion.
Resource requirements can be defined at the System, Folder and the Job level. These values are then added together to define the total units required for the Job to begin executing.