The format of the output is determined by other switches:

         Default - Shows jobs in the Monsanto summary format.
          -m   Synonym for the default (Monsanto summary format).
          -l   Standard NQS format with further detail.
          -s   Standard NQS format.


QUEUE STATE


The general state of a queue is defined by two principal properties of the queue.

The first property determines whether or not requests can be submitted to the queue.  If they can, then the queue is said to be enabled.  Otherwise the queue is said to be disabled. One of the words CLOSED, ENABLED, or DISABLED will appear in the queue status field to indicate the respective queue states of: enabled (with no local NQS daemon), enabled (and local NQS daemon is present), and disabled.  Requests can only be submitted to the queue if the queue is enabled, and the local NQS daemon is present.

The second principal property of a queue determines if requests which are ready to run, but are not now presently running, will be allowed to run upon the completion of any currently running requests, and whether any requests are presently running in the queue.

If queued requests not already running are blocked from running, and no requests are presently executing in the queue, then the queue is said to be stopped.  If the same situation exists with the difference that at least one  request is running, then the queue is said to be stopping, where the requests presently executing will be allowed to complete execution, but no new requests will be spawned.

If queued requests ready to run are only prevented from doing so by the NQS request scheduler, and one or more requests are presently running in the queue, then the queue is said to be running.  If the same circumstances prevail with the exception that no requests are presently running in the queue, then the queue is said to be inactive.  Finally, if the NQS daemon for the local host upon which the queue resides is not running, but the queue would otherwise be in the state of running or inactive, then the queue is said to be shutdown.  The queue states describing the second principal property of a queue are therefore respectively  displayed as STOPPED, STOPPING, RUNNING, INACTIVE, and SHUTDOWN.

REQUEST STATE


The state of a request may be arriving, holding, waiting, queued, staging, routing, running, departing, or exiting.  A
request is said to be arriving if it is being enqueued from a remote host.  Holding indicates that the request is
presently prevented from entering any other state (including the running state), because a hold has been placed on the
request.  A request is said to be waiting if it was submitted with the constraint that it not run before a
certain date and time, and that date and time have not yet arrived.  Queued requests are eligible to proceed (by
routing or running).  When a request reaches the head of a pipe queue and receives service there, it is routing.  A
request is departing from the time the pipe queue turns to other work until the request has arrived intact at its
destination.  Staging denotes a batch request that has not yet begun execution, but for which input files are being
brought on to the execution machine.  A running request has reached its final destination queue, and is actually
executing.  Finally, exiting describes a batch request that has completed execution, and will exit from the system after
the required output files have been returned (to possibly remote machines).


EXAMPLES
          $ qstat -x
          batch@beaker.monsanto.com;  type=BATCH;  [ENABLED, INACTIVE];  pri=16  lim=1
          0 exit;   0 run;   0 stage;   0 queued;   0 wait;   0 hold;   0 arrive;
          User run limit= 1

          cray@beaker.monsanto.com;  type=PIPE;  [ENABLED, INACTIVE];  pri=16  lim=1
           0 depart;   0 route;   0 queued;   0 wait;   0 hold;   0 arrive;
           Destset = {batch@cray};

          $ qstat -xl
          batch@beaker.monsanto.com;  type=BATCH;  [ENABLED, INACTIVE];  pri=16  lim=1
           0 exit;   0 run;   0 stage;   0 queued;   0 wait;   0 hold;   0 arrive;
           User run limit= 1
           Cumulative system space time = 1.98 seconds
           Cumulative user space time = 0.80 seconds
           Unrestricted access
           Per-process core file size limit = 32 megabytes <DEFAULT>
           Per-process data size limit = 32 megabytes <DEFAULT>
           Per-process permanent file size limit = 500 megabytes <DEFAULT>
           Queue nondegrading priority =    0
           Per-process execution nice value = 0 <DEFAULT>
           Per-process stack size limit = 32 megabytes <DEFAULT>
           Per-process CPU time limit = 360000.0 <DEFAULT>
           Per-process working set limit = 32 megabytes <DEFAULT>

          cray@beaker.monsanto.com;  type=PIPE;  [ENABLED, INACTIVE];  pri=16  lim=1
           0 depart;   0 route;   0 queued;   0 wait;   0 hold;   0 arrive;
           Cumulative system space time = 0.00 seconds
           Cumulative user space time = 0.00 seconds
           Unrestricted access
           Queue server: /usr/lib/nqs/pipeclient
           Destset = {batch@cray};

          $ qsub -eo -q batch -r example idle.nqs

          $ qstat
          Request         I.D.  Owner    Queue    Start Time   Time Limit  Total Time St
          -------------- ------ -------- -------- -----------  ----------  ---------- --
          example          130  jrroma   batch    4/30 11:40   4 04:00:00  0 00:00:00 R