showq [ -? ]
The showq command is located in the same directory as all LoadLeveler commands, /usr/lpp/LoadL/nfs/bin. Since LoadLeveler is no longer scheduling, the job ordering it displays is no longer valid. showq displays the actual job ordering under the new scheduler.
Example:
showq
Example output:
ACTIVE JOBS--------------------
JOBNAME USERNAME STATE PROCS REMAINING STARTTIME
[ 1] fr4n12.1393.0 userc Running 8 01:09:00 Tue May 13 08:15:33 1997
[ 2] fr4n14.1451.0 userd Running 8 01:21:32 Tue May 13 08:24:05 1997
[ 3] fr6n11.928.0 usera Starting 8 01:27:14 Tue May 13 02:28:47 1997
[ 4] fr6n14.905.0 usera Running 8 01:42:01 Tue May 13 08:53:34 1997
IDLE JOBS----------------------
JOBNAME USERNAME STATE PROCS CPULIMIT QUEUETIME
[ 5] fr17n06.1004.0 userc Idle 8 00:10:00 Mon May 5 16:44:48 1997
[ 6] fr6n06.862.0 userb Idle 64 00:28:20 Mon May 5 11:03:33 1997
[ 7] fr15n07.906.0 usere Idle 64 00:28:20 Mon May 5 12:31:59 1997
[ 8] fr6n04.955.0 usere Idle 64 00:28:20 Mon May 5 13:36:11 1997
[ 9] fr17n05.903.0 userb Idle 32 01:00:00 Tue May 6 10:01:36 1997
[ 10] fr4n13.1598.0 userg Idle 16 06:56:40 Thu Apr 24 23:18:35 1997
NON-QUEUED JOBS----------------
JOBNAME USERNAME STATE PROCS CPULIMIT QUEUETIME
[ 11] fr15n07.820.0 usere Hold 1 12:00:00 Wed Apr 2 09:10:17 1997
[ 12] fr15n09.926.0 usera Idle 32 02:00:00 Thu Mar 13 03:23:21 1997
[ 13] fr15n11.871.0 userb Hold 32 02:00:00 Tue Mar 11 07:11:05 1997
[ 14] fr17n01.900.0 userb Idle 16 23:59:00 Sun May 11 09:00:12 1997
[ 15] fr17n03.802.0 userb Idle 32 02:00:00 Wed Mar 12 22:30:23 1997
[ 16] fr17n04.734.0 userh Hold 64 04:00:00 Tue Feb 25 07:48:11 1997
[ 17] fr17n04.899.0 userb Idle 8 05:00:00 Mon May 12 18:16:35 1997
Total Jobs: 17
The output of this command is broken into three parts, Active Jobs, Idle Jobs, and Non-Queued Jobs.
Active jobs are those that are Running or Starting and actually consuming CPU resources. The command displays the job name, 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 Hour:Minute:Second notation), and the time the job started. All active jobs are sorted in "Earliest-Completion Time First" order.
Idle Jobs are those that are queued and eligible to be scheduled. They are all in the job state "Idle" and do not exceed the "Max Jobs Running" policy or the "Max Jobs Queued" policy. In the example above, policies allow a total of two jobs per user to be running and two jobs per user to be queued. This section displays the same information as the Active job section with the exception that WallClock CpuLimit is specified rather than time remaining and job QueueTime is displayed rather than job StartTime. The jobs in this section are ordered by priority. Jobs in this queue are considered eligible for both scheduling and backfilling.
The Non-Queued jobs are those that are ineligible to be run or queued. Held jobs as well as those that exceed various fairness policies would be listed here. In the above example, "usera" has one job here because he already has the maximum number of jobs running. "userb" has three jobs in the list because she already has two jobs in the Idle job queue. Other jobs located in this list are there because of job holds. Jobs in this list are not in any particular order and are not considered for scheduling or backfill.