Queuing
The Queuing tab allows you to define the Job Queue to which this job will be submitted. Here you also setup queue priority, runtime priority and held status.
- Job Queue - Select the Job Queue that this job will be submitted to. The Job Queue determines when the job will start. Based upon how the queues have been configured a job submitted to a queue may start immediately, may start when others in the queue before it have finished or may not start until the queue is released. If you want the job to start immediately choose QIMMED. If you have just created a new Job Queue in the Server manager press the refresh button to update the pulldown list of Job Queues.
- Queue Priority - select the queue priority for this job. Priorities are from 1-10, 10 being the highest priority or most important task, with 1 being low priority. A job with priority 10 will jump ahead of others on the queue that have a lower priority. Jobs that are held on a Job Queue will not run at all and therefore their priority will have not effect until they are released.
- Execution Priority - select the initial execution priority to assign to this job when is starts in the subsystem that the Job Queue is attached to. A job with priority 10 will be assigned more system resources than one with a lower priority. The priority that the subsystem is running at will also affect the overall priority of the jobs running within it. A job running with priority 5 in a subsystem running at priority 8 will receive more system resources than a similar job running at priority 5 in a subsystem running at priority 4.
- Held on Queue - select whether this job should be held when it is submitted to the Job Queue. It will then need to be manually release before it can become active.