Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ qstat(1) — CLIX 3.1r7.6.28

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

qdel(1)

qdev(1)

qlimit(1)

qpr(1)

qsub(1)

qmgr(8)



  qstat(1)                            CLIX                            qstat(1)



  NAME

    qstat - Displays the status of NQS queues

  SYNOPSIS

    qstat [-abdlmpru username] [-x] [queue-name][@hostname] ... ]

    qstat [-c] [complex-name ... ]

  FLAGS

    -a            Display the status of all requests in the queue.

    -b            Restrict the display of requests to batch queues.

    -d            Restrict the display to device queues.

    -p            Restrict the display to pipe queues.

    -r            Recursively display pipe queue destinations.  After a pipe
                  queue is displayed, display each of the respective queues
                  appearing in the pipe queue's destination list.  This flag
                  should be used with the -b, -d, or -p flag to limit the
                  queues displayed.

    -u username   Display the status of only those requests owned by user-
                  name.

  Display Format Flags

    These flags determine the output format:

    -l   Display information about requests in long format.

    -m   Display information about requests in medium-length format.

    -c   Display information about queue complexes.

    The -l flag displays the time when the request was created, an indication
    of whether mail will be sent, where mail will be sent, the username on the
    originating machine, and the requested forms (if a device queue).  If the
    queue is a batch queue, resource limits, planned disposition of stderr and
    stdout, advice concerning the command interpreter, and the umask value are
    also displayed.  The -m flag displays the time and date the request will
    run.

    The -c flag displays information about queue complexes and ignores all
    other flags.  For each queue complex, the run limit and a listing of the
    member queues in the complex is shown.




  2/94 - Intergraph Corporation                                              1






  qstat(1)                            CLIX                            qstat(1)



  DESCRIPTION

    The qstat command displays the status of Network Queuing System (NQS)
    queues.  The qstat command, without a queue-name argument, displays the
    current status of all NQS queues on the local host.  Otherwise, qstat
    displays the status of the queues specified by queue-name.  The queue is
    assumed to be on the local machine unless a particular host is specified
    by @hostname.

    The qstat command normally displays information only about requests in the
    specified queues owned by the invoker.  This may be changed by using one
    of the following flags described in FLAGS:  -a, -b, -d, -p, -r, or -u.

    For each specified queue, a queue header is displayed.  The queue header
    displays the queue name, queue type, queue state, an indication of whether
    the queue accepts requests only from pipe queues, and the number of
    requests in the queue.  Additional information about the queue may be
    obtained with the -x (extended format) flag.  This flag will display the
    priority of the queue, its run limit, access restrictions, cumulative use
    statistics, server and destinations (if a pipe queue), queue-to-device
    mappings (if a device queue), and resource limits (if a batch queue).

    The general state of a queue is defined by two principal properties.  The
    first property determines whether requests can be submitted to the queue.
    If they can and the local NQS daemon is present, the state of the queue is
    ENABLED.  If the local daemon is not present, the queue is in a CLOSED
    state.  If a request cannot be submitted, it is in a DISABLED state.
    Requests can be submitted only when the queue is in the ENABLED state.

    The second principal property of a queue determines if requests that are
    ready to run but are not running will be allowed to run when running
    requests complete.  It also determines whether any requests are running in
    the queue.  If queued requests are blocked and no requests are running,
    the queue is in a STOPPED state.  If queued requests are blocked and at
    least one request is running, the queue is in a STOPPING state.  In this
    state, requests that are running will be allowed to complete.  However, no
    new requests will be spawned.

    If the NQS daemon prevents queued requests from running and at least one
    request is running, the queue is in a RUNNING state.  If the daemon
    prevents queued requests from running and no requests are running, the
    queue is in an INACTIVE state.  If the daemon is not running but the queue
    would otherwise be in the RUNNING or INACTIVE state, the queue is in a
    SHUTDOWN state.

    Following each queue header, information about requests in the queue is
    displayed.  For each request, the following information is displayed: the
    request name, the request ID, the request owner, the relative request
    priority, the current request state, the process group (if the request is
    running), and the request size (if a device queue).  Additional
    information may be obtained by using the -l, -m, or -c flags described in



  2                                              Intergraph Corporation - 2/94






  qstat(1)                            CLIX                            qstat(1)



    FLAGS.

    The disposition of a request defines the state of the request.  If it is
    being queued from a remote host, the state of the request is ARRIVING.  If
    it is submitted with a time constraint that has not yet arrived, its state
    is WAITING.  If it is eligible to proceed to a ROUTING or a RUNNING state,
    it is in a QUEUED state.  If it is at the head of a pipe queue and is
    receiving service there, it is in a ROUTING state.  If it departed from a
    pipe queue and has not yet arrived at its destination, it is in a
    DEPARTING state.  If it reached its destination and is executing, it is in
    a RUNNING state.

  EXAMPLES

    A batch request originating on a workstation and destined for the batch
    queue of a remote machine to be run immediately would first undergo the
    states, QUEUED, ROUTING, and DEPARTING, in a local pipe queue.  The
    request would then leave the pipe queue and be received by a batch queue
    on the remote machine.  Here, it undergoes the states, ARRIVING, QUEUED,
    and RUNNING.

    1.  To display information about all requests in device queues on the
        local machine, enter the following:

        qstat -a -d


    2.  The command line that follows provides an easy way to find where the
        printers are.  When given the -p and -r flags, qstat recursively
        follows the pipe queue name print1 until a device or batch queue is
        reached.

        qstat -p -r print1


    3.  To display information about any jobs that user doe has in the ilp811
        queue on the machine host2, use the following command line:

        qstat -u doe ilp11@host2


    4.  For information about all queues on host2, with header information for
        each queue, use the following:

        qstat -x @host2


    5.  To display information about the complex named comp1, use this command
        line:

        qstat -c comp1



  2/94 - Intergraph Corporation                                              3






  qstat(1)                            CLIX                            qstat(1)



  DIAGNOSTICS

    NQS daemon not running on local host.
           NQS has been shutdown.  Seek help from an NQS manager.

  EXIT VALUES

    The qstat command exits with a nonzero value if an error occurs.

  RELATED INFORMATION

    Commands: qdel(1), qdev(1), qlimit(1), qpr(1), qsub(1), qmgr(8)










































  4                                              Intergraph Corporation - 2/94




Typewritten Software • bear@typewritten.org • Edmonds, WA 98026