| Moab Workload Manager® |
showq | (Show Queue) |
Synopsis
showq [-b] [-g] [-l] [-c|-i|-r] [-p partition] [-R rsvid] [-v] [-w <CONSTRAINT>]
Overview
Displays information about active, eligible, blocked, and/or recently completed jobs. Since the resource manager is not actually scheduling jobs, the job ordering it displays is not valid. The showq command displays the actual job ordering under the Moab Workload Manager. When used without flags, this command displays all jobs in active, idle, and non-queued states.Access
By default, this command can be run by any user. However, the -c, -i, and -r flags can only be used by level 1, 2, or 3 Moab administrators.Flags
| -b | display blocked jobs only |
| -c | display details about recently completed jobs (see example, JOBCPURGETIME). |
| -g | display grid job and system id's for all jobs. |
| -i | display extended details about idle jobs. (see example) |
| -l | display local/remote view. For use in a Grid environment, displays job usage of both local and remote compute resources. |
| -p | display only jobs assigned to the specified partition. |
| -r | display extended details about active (running) jobs. (see example) |
| -R | display only jobs which overlap the specified reservation. |
| -v | display local and full resource manager job ids. If specified with the '-i' option, will display job reservation time. |
| -w | display only jobs associated with the specified constraint. Valid constraints include user, group, account, class, and qos. (see showq -w example.) |
Details
Beyond job information, the showq command will also report if the scheduler is stopped or paused or if a system reservation is in place. Further, the showq command will also report public system messages.Examples
- Example 1: Default Report
- Example 2: Detailed Active/Running Job Report
- Example 3: Detailed Eligible/Idle Job Report
- Example 4: Detailed Completed Job Report
- Example 5: Filtered Job Report
Example 1: Default Report
The output of this command is divided into three parts, Active Jobs, Eligible Jobs, and Blocked Jobs.The fields are as follows:
| JOBID | job identifier. |
| USERNAME | User owning job. |
| STATE | Job State. Current batch state of the job. |
| PROC | Number of processors being used by the job. |
| REMAINING/WCLIMIT | For active jobs, the time the job has until it has reached its wall clock limit or for idle/blocked jobs, the amount of time requested by the job. Time specified in [DD:]HH:MM:SS notation. |
| STARTTIME | Time job started running. |
Active jobs are those that are Running or Starting and consuming resources. Displayed are the job id*, the job's owner, and the job state. Also displayed are the number of processors allocated to the job, the amount of time remaining until the job completes (given in HH:MM:SS notation), and the time the job started. All active jobs are sorted in "Earliest Completion Time First" order.
* NOTE: Job id's may be marked with a single character to to specify the following conditions:
NOTE: Detailed active job information can be obtained using the '-r' flag.
| Character | Description |
| _ (underbar) | job violates usage limit |
| * (asterisk) | job is backfilled AND is preemptible |
| + (plus) | job is backfilled AND is NOT preemptible |
| - (hyphen) | job is NOT backfilled AND is preemptible |
Eligible Jobs are those that are queued and eligible to be scheduled. They are all in the Idle job state and do not violate any fairness policies or have any job holds in place. The jobs in the Idle section display the same information as the Active Jobs section except that the wall clock CPULIMIT is specified rather than job time REMAINING, and job QUEUETIME is displayed rather than job STARTTIME. The jobs in this section are ordered by job priority. Jobs in this queue are considered eligible for both scheduling and backfilling.
NOTE: Detailed eligible job information can be obtained using the '-i' flag.
Blocked jobs are those that are ineligible to be run or queued. Jobs listed here could be in a number of states for the following reasons:
| Idle | Job violates a fairness policy. Use diagnose -q for more information. |
| UserHold | A user hold is in place. |
| SystemHold | An administrative or system hold is in place. |
| BatchHold | A scheduler batch hold is in place (used when the job cannot be run because the requested resources are not available in the system or because the resource manager has repeatedly failed in attempts to start the job). |
| Deferred | A scheduler defer hold is in place (a temporary hold used when a job has been unable to start after a specified number of attempts. This hold is automatically removed after a short period of time). |
| NotQueued | Job is in the resource manager state NQ (indicating the job's controlling scheduling daemon in unavailable). |
A summary of the job queue's status is provided at the end of the output.
Example 2: Detailed Active/Running Job Report
The fields are as follows:
| JOBID | Name of active job. |
| S | Job State. Either "R" for Running or "S" for Starting. |
| PAR | Partition in which job is running. |
| EFFIC | CPU efficiency of job. |
| XFACTOR | Current expansion factor of job, where XFactor = (QueueTime + WallClockLimit) / WallClockLimit |
| Q | Quality Of Service specified for job. |
| USERNAME | User owning job. |
| GROUP | Primary group of job owner. |
| MHOST | Master Host running primary task of job. |
| PROC | Number of processors being used by the job. |
| REMAINING | Time the job has until it has reached its wall clock limit. Time specified in HH:MM:SS notation. |
| STARTTIME | Time job started running. |
After displaying the running jobs, a summary is provided indicating the number of jobs, the number of allocated processors, and the system utilization.