QUEUE commands

The scheduling queues can be viewed and managed using the following commands.

Each queue in Schedule for Windows represents a scheduling state. Queues are identified by a single letter. Active jobs move between these states as they progress through the system. Generally they start at the top and go to the bottom (this varies depending on the job attributes).

Each entry in the scheduling queues has a unique index entry number.

The various queues are listed below:

COMPUTE NEXT START Any job that is to be examined to determine when it will start again is entered here. The next start time is computed and the job proceeds on.

WAIT FOR NEXT START TIME Any job that has a start time set is entered into this queue and stays here until the start time occurs.

INITIATE WITH NO SET ID Any job that has been initiated either manually or automatically that does NOT have a SET ID assigned is entered here. The job is assigned a number and then proceeds.

WORKGROUP MANAGER Workgroup processing is performed in this state. Node analysis and selection is performed. Only affects jobs that are part of a workgroup.

WAIT FOR LOCAL PREREQUISITE Any job that has prerequisites on the local system (or cluster) is entered into this queue. Once all the prerequisite jobs have successfully completed the job proceeds.

REQUEST REMOTE PREREQUISITE Any job that has a prerequisite specified that is on a remote node is entered here. A request is transmitted to the remote node and then the job proceeds.

WAIT FOR REMOTE PREREQUISITE Once a job has requested a completion event from a remote node it then waits in this queue until the event occurs. Once all responses have been received the job proceeds on.

WAIT FOR A REQUIRED FILE Any job that requires a file to be present is entered into this queue. Once the file has been created the job proceeds.

WAIT FOR DISK SPACE REQUIREMENTS Any job that requires a certain amount of disk space to be present before proceeding will stay in this queue until the space is available.

READY TO SUBMIT Once a job has met all the resource and other requirements it is entered into this queue. The job is then entered into a batch execution queue and the job proceeds.

SUBMITTED FOR EXECUTION Once the job has been submitted for execution an entry is made into this queue.

EXECUTION STARTED Once the job starts to execute an entry is made into this queue.

JOB COMPLETED When the job completes execution it is entered into this queue.

INITIATE DESCENDANTS JOBS On completion the initiate list of each job is examined. Any jobs that are to be activated are entered into the B queue.

SEND INITIATE REQUEST TO A REMOTE NODE Any remote initiate job request is placed into this queue. The request is then transmitted over to the remote node.

HOLDING PREVIOUS COMPLETIONS When a job completes it is entered into this queue. Entries are held in this queue to be used to satisfy future prerequisite requirements. After a short period typically 1 day the entries are removed.

EVENT MESSAGES Foreground processing signal messages are entered into this queue before dispatching them.

JOB COMPLETION MESSAGES Foreground job completion messages containing complete history information are entered into this queue before dispatching.

REMOTE COMPLETION MESSAGES Remote messages requesting information when a job has completed are kept in this queue until the job completes. At that time a message is sent back to the requesting node.

EVALUATING VARIABLES The job is currently evaluating variables and determining the course that the job group will go depending on the resource list, initiates, prerequisites, and end action list.