    .SH "DESCRIPTION"
    \fBsqueue\fR is used to view job and job step information for jobs managed by
    Slurm.

    .SH "OPTIONS"

    .TP
    \fB\-A <account_list>\fR, \fB\-\-account=<account_list>\fR
    Specify the accounts of the jobs to view. Accepts a comma separated
    list of account names. This has no effect when listing job steps.

    .TP
    \fB\-a\fR, \fB\-\-all\fR
    Display information about jobs and job steps in all partitions.
    This causes information to be displayed about partitions that are configured as
    hidden and partitions that are unavailable to user's group.

    .TP
    \fB\-r\fR, \fB\-\-array\fR
    Display one job array element per line.
    Without this option, the display will be optimized for use with job arrays
    (pending job array elements will be combined on one line of output with the
    array index values printed using a regular expression).

    .TP
    \fB\-\-array-unique\fR
    Display one unique pending job array element per line. Without this option,
    the pending job array elements will be grouped into the master array job to
    optimize the display.  This can also be set with the environment variable
    SQUEUE_ARRAY_UNIQUE.

    .TP
    \fB\-\-federation\fR
    Show jobs from the federation if a member of one.

    .TP
    \fB\-h\fR, \fB\-\-noheader\fR
    Do not print a header on the output.

    .TP
    \fB\-\-help\fR
    Print a help message describing all options \fBsqueue\fR.

    .TP
    \fB\-\-hide\fR
    Do not display information about jobs and job steps in all partitions. By default,
    information about partitions that are configured as hidden or are not available
    to the user's group will not be displayed (i.e. this is the default behavior).

    .TP
    \fB\-i <seconds>\fR, \fB\-\-iterate=<seconds>\fR
    The job ID format is "job_id[_array_id]".
    Performance of the command can be measurably improved for systems with large
    numbers of jobs when a single job ID is specified.
    By default, this field size will be limited to 64 bytes.
    Use the environment variable SLURM_BITSTR_LEN to specify larger field sizes.

    .TP
    \fB\-\-local\fR
    Show only jobs local to this cluster. Ignore other clusters in this federation
    (if any). Overrides \-\-federation.

    .TP
    \fB\-l\fR, \fB\-\-long\fR
    Report more of the available information for the selected jobs or job steps,
    subject to any constraints specified.

    .TP
    \fB\-L\fR, \fB\-\-licenses=<license_list>\fR
    Request jobs requesting or using one or more of the named licenses.
    The license list consists of a comma separated list of license names.

    .TP
    \fB\-M\fR, \fB\-\-clusters\fR=<\fIstring\fR>
    Clusters to issue commands to.  Multiple cluster names may be comma separated.
    A value of of '\fIall\fR' will query to run on all clusters.
    This option implicitly sets the \fB\-\-local\fR option.

    .TP
    \fB\-n\fR, \fB\-\-name=<name_list>\fR
    Request jobs or job steps having one of the specified names.  The
    list consists of a comma separated list of job names.

    .TP
    \fB\-\-noconvert\fR
    Don't convert units from their original type (e.g. 2048M won't be converted to
    2G).

    .TP
    \fB\-o <output_format>\fR, \fB\-\-format=<output_format>\fR
    Specify the information to be displayed, its size and position
    (right or left justified).
    Also see the \fB\-O <output_format>\fR, \fB\-\-Format=<output_format>\fR
    option described below (which supports less flexibility in formatting, but
    supports access to all fields).
    The default formats with various options are

    .RS
    .TP 15
    \fIdefault\fR
    "%.18i %.9P %.8j %.8u %.2t %.10M %.6D %R"
    .TP
    .TP
    \fI .\fR
    indicates the output should be right justified and size must be specified.
    By default, output is left justified.
    .RE

    .IP
    Note that many of these \fItype\fR specifications are valid
    only for jobs while others are valid only for job steps.
    Valid \fItype\fR specifications include:

    .RS
    .TP 6
    \fB%all\fR
    Print all fields available for this data type with a vertical bar separating
    each field.
    .TP
    \fB%a\fR
    Account associated with the job.
    (Valid for jobs only)
    .TP
    \fB%A\fR
    Number of tasks created by a job step.
    This reports the value of the \fBsrun \-\-ntasks\fR option.
    (Valid for job steps only)
    .TP
    \fB%A\fR
    Job id.
    This will have a unique value for each element of job arrays.
    (Valid for jobs only)
    .TP
    \fB%B\fR
    Executing (batch) host. For an allocated session, this is the host on which
    the session is executing (i.e. the node from which the \fBsrun\fR or the
    \fBsalloc\fR command was executed). For a batch job, this is the node executing
    the batch script. In the case of a typical Linux cluster, this would be the
    compute node zero of the allocation. In the case of a Cray ALPS
    system, this would be the front\-end host whose slurmd daemon executes the job
    script.
    .TP
    \fB%c\fR
    Minimum number of CPUs (processors) per node requested by the job.
    This reports the value of the \fBsrun \-\-mincpus\fR option with a
    default value of zero.
    (Valid for jobs only)
    .TP
    \fB%C\fR
    Number of CPUs (processors) requested by the job or allocated to
    it if already running.  As a job is completing this number will
    reflect the current number of CPUs allocated.
    (Valid for jobs only)
    .TP
    \fB%e\fR
    Time at which the job ended or is expected to end (based upon its time limit).
    (Valid for jobs only)
    .TP
    \fB%E\fR
    Job dependencies remaining. This job will not begin execution until these
    dependent jobs complete. In the case of a job that can not run due to job
    dependencies never being satisfied, the full original job dependency
    specification will be reported. A value of NULL implies this job has no
    dependencies.
    (Valid for jobs only)
    .TP
    \fB%f\fR
    Features required by the job.
    (Valid for jobs only)
    .TP
    \fB%F\fR
    Job array's job ID. This is the base job ID.
    For non\-array jobs, this is the job ID.
    (Valid for jobs only)
    .TP
    \fB%g\fR
    Group name of the job.
    (Valid for jobs only)
    .TP
    \fB%G\fR
    Group ID of the job.
    (Valid for jobs only)
    .TP
    \fB%h\fR
    Can the compute resources allocated to the job be over subscribed by other jobs.
    The resources to be over subscribed can be nodes, sockets, cores, or
    hyperthreads depending upon configuration.
    The value will be "YES" if the job was submitted with the oversubscribe option
    or the partition is configured with OverSubscribe=Force,
    "NO" if the job requires exclusive node access,
    "USER" if the allocated compute nodes are dedicated to a single user,
    "MCS" if the allocated compute nodes are dedicated to a single security class
    (See MCSPlugin and MCSParameters configuration parameters for more information),
    "OK" otherwise (typically allocated dedicated CPUs),
    (Valid for jobs only)
    .TP
    \fB%H\fR
    Number of sockets per node requested by the job.
    This reports the value of the \fBsrun \-\-sockets\-per\-node\fR option.
    When \-\-sockets\-per\-node has not been set, "*" is displayed.
    (Valid for jobs only)
    .TP
    \fB%i\fR
    Job or job step id.
    In the case of job arrays, the job ID format will be of the form
    "<base_job_id>_<index>".
    Job or job step name.
    (Valid for jobs and job steps)
    .TP
    \fB%J\fR
    Number of threads per core requested by the job.
    This reports the value of the \fBsrun \-\-threads\-per\-core\fR option.
    When \-\-threads\-per\-core has not been set, "*" is displayed.
    (Valid for jobs only)
    .TP
    \fB%k\fR
    Comment associated with the job.
    (Valid for jobs only)
    .TP
    \fB%K\fR
    Job array index.
    By default, this field size will be limited to 64 bytes.
    Use the environment variable SLURM_BITSTR_LEN to specify larger field sizes.
    (Valid for jobs only)
    .TP
    \fB%l\fR
    Time limit of the job or job step in days\-hours:minutes:seconds.
    The value may be "NOT_SET" if not yet established or "UNLIMITED" for no limit.
    (Valid for jobs and job steps)
    .TP
    \fB%L\fR
    Time left for the job to execute in days\-hours:minutes:seconds.
    This value is calculated by subtracting the job's time used from its time
    limit.
    The value may be "NOT_SET" if not yet established or "UNLIMITED" for no limit.
    (Valid for jobs only)
    .TP
    \fB%m\fR
    Minimum size of memory (in MB) requested by the job.
    (Valid for jobs only)
    .TP
    \fB%M\fR
    Time used by the job or job step in days\-hours:minutes:seconds.
    The days and hours are printed only as needed.
    For job steps this field shows the elapsed time since execution began
    and thus will be inaccurate for job steps which have been suspended.
    Clock skew between nodes in the cluster will cause the time to be inaccurate.
    If the time is obviously wrong (e.g. negative), it displays as "INVALID".
    (Valid for jobs and job steps)
    .TP
    \fB%n\fR
    List of node names explicitly requested by the job.
    (Valid for jobs only)
    .TP
    \fB%N\fR
    List of nodes allocated to the job or job step. In the case of a
    \fICOMPLETING\fR job, the list of nodes will comprise only those
    nodes that have not yet been returned to service.
    \fB%P\fR
    Partition of the job or job step.
    (Valid for jobs and job steps)
    .TP
    \fB%q\fR
    Quality of service associated with the job.
    (Valid for jobs only)
    .TP
    \fB%Q\fR
    Priority of the job (generally a very large unsigned integer).
    Also see \fB%p\fR.
    (Valid for jobs only)
    .TP
    \fB%r\fR
    The reason a job is in its current state.
    See the \fBJOB REASON CODES\fR section below for more information.
    (Valid for jobs only)
    .TP
    \fB%R\fR
    For pending jobs: the reason a job is waiting for execution
    is printed within parenthesis.
    For terminated jobs with failure: an explanation as to why the
    job failed is printed within parenthesis.
    For all other job states: the list of allocate nodes.
    See the \fBJOB REASON CODES\fR section below for more information.
    (Valid for jobs only)
    .TP
    \fB%s\fR
    Node selection plugin specific data for a job. Possible data includes:
    Geometry requirement of resource allocation (X,Y,Z dimensions),
    Connection type (TORUS, MESH, or NAV == torus else mesh),
    Permit rotation of geometry (yes or no),
    Node use (VIRTUAL or COPROCESSOR), etc.
    (Valid for jobs only)
    .TP
    \fB%S\fR
    Actual or expected start time of the job or job step.
    (Valid for jobs and job steps)
    .TP
    \fB%t\fR
    Job state in compact form.
    See the \fBJOB STATE CODES\fR section below for a list of possible states.
    (Valid for jobs only)
    .TP
    \fB%T\fR
    Job state in extended form.
    See the \fBJOB STATE CODES\fR section below for a list of possible states.
    (Valid for jobs only)
    .TP
    \fB%u\fR
    User name for a job or job step.
    (Valid for jobs and job steps)
    (Valid for jobs only)
    .TP
    \fB%W\fR
    Licenses reserved for the job.
    (Valid for jobs only)
    .TP
    \fB%x\fR
    List of node names explicitly excluded by the job.
    (Valid for jobs only)
    .TP
    \fB%X\fR
    Count of cores reserved on each node for system use (core specialization).
    (Valid for jobs only)
    .TP
    \fB%y\fR
    Nice value (adjustment to a job's scheduling priority).
    (Valid for jobs only)
    .TP
    \fB%Y\fR
    For pending jobs, a list of the nodes expected to be used when the job is
    started.
    .TP
    \fB%z\fR
    Number of requested sockets, cores, and threads (S:C:T) per node for the job.
    When (S:C:T) has not been set, "*" is displayed.
    (Valid for jobs only)
    .TP
    \fB%Z\fR
    The job's working directory.
    .RE

    .TP
    \fB\-O <output_format>\fR, \fB\-\-Format=<output_format>\fR
    Specify the information to be displayed.
    Also see the \fB\-o <output_format>\fR, \fB\-\-format=<output_format>\fR
    option described below (which supports greater flexibility in formatting, but
    does not support access to all fields because we ran out of letters).
    Requests a comma separated list of job information to be displayed.

    .IP
    The format of each field is "type[:[.]size]"
    .RS
    .TP 8
    \fIsize\fR
    is the minimum field size.
    If no size is specified, 20 characters will be allocated to print the information.
    .TP
    \fI .\fR
    indicates the output should be right justified and size must be specified.
    By default, output is left justified.
    .RE
    (Valid for jobs only)
    .TP
    \fBadmin_comment\fR
    Administrator comment associated with the job.
    (Valid for jobs only)
    .TP
    \fBallocnodes\fR
    Print the nodes allocated to the job.
    (Valid for jobs only)
    .TP
    \fBallocsid\fR
    Print the session ID used to submit the job.
    (Valid for jobs only)
    .TP
    \fBarrayjobid\fR
    Prints the job ID of the job array.
    (Valid for jobs and job steps)
    .TP
    \fBarraytaskid\fR
    Prints the task ID of the job array.
    (Valid for jobs and job steps)
    .TP
    \fBassocid\fR
    Prints the id of the job association.
    (Valid for jobs only)
    .TP
    \fBbatchflag\fR
    Prints whether the batch flag has been set.
    (Valid for jobs only)
    .TP
    \fBbatchhost\fR
    Executing (batch) host. For an allocated session, this is the host on which
    the session is executing (i.e. the node from which the \fBsrun\fR or the
    \fBsalloc\fR command was executed). For a batch job, this is the node executing
    the batch script. In the case of a typical Linux cluster, this would be the
    compute node zero of the allocation. In the case of a Cray ALPS
    system, this would be the front\-end host whose slurmd daemon executes the job
    script.
    (Valid for jobs only)
    .TP
    \fBboardspernode\fR
    Prints the number of boards per node allocated to the job.
    (Valid for jobs only)
    .TP
    \fBburstbuffer\fR
    Burst Buffer specification
    (Valid for jobs only)
    .TP
    \fBburstbufferstate\fR
    Burst Buffer state
    (Valid for jobs only)
    .TP
    .TP
    \fBcommand\fR
    The command to be executed.
    (Valid for jobs only)
    .TP
    \fBcomment\fR
    Comment associated with the job.
    (Valid for jobs only)
    .TP
    \fBcontiguous\fR
    Are contiguous nodes requested by the job.
    (Valid for jobs only)
    .TP
    \fBcores\fR
    Number of cores per socket requested by the job.
    This reports the value of the \fBsrun \-\-cores\-per\-socket\fR option.
    When \-\-cores\-per\-socket has not been set, "*" is displayed.
    (Valid for jobs only)
    .TP
    \fBcorespec\fR
    Count of cores reserved on each node for system use (core specialization).
    (Valid for jobs only)
    .TP
    \fBcpufreq\fR
    Prints the frequency of the allocated CPUs.
    (Valid for job steps only)
    .TP
    \fBcpus\-per\-task\fR
    Prints the number of CPUs per tasks allocated to the job.
    (Valid for jobs only)
    .TP
    \fBcpus\-per\-tres\fR
    Print the memory required per trackable resources allocated to the job or job step.
    .TP
    \fBdeadline\fR
    Prints the deadline affected to the job
    (Valid for jobs only)
    .TP
    \fBdependency\fR
    Job dependencies remaining. This job will not begin execution until these
    dependent jobs complete. In the case of a job that can not run due to job
    dependencies never being satisfied, the full original job dependency
    specification will be reported. A value of NULL implies this job has no
    dependencies.
    (Valid for jobs only)
    .TP
    \fBdelayboot\fR
    Delay boot time.
    (Valid for jobs only)
    .TP
    \fBderivedec\fR
    Derived exit code for the job, which is the highest exit code of any job step.
    \fBfeature\fR
    Features required by the job.
    (Valid for jobs only)
    .TP
    \fBgroupid\fR
    Group ID of the job.
    (Valid for jobs only)
    .TP
    \fBgroupname\fR
    Group name of the job.
    (Valid for jobs only)
    .TP
    \fBjobarrayid\fR
    Job array's job ID. This is the base job ID.
    For non\-array jobs, this is the job ID.
    (Valid for jobs only)
    .TP
    \fBjobid\fR
    Job id.
    This will have a unique value for each element of job arrays and each
    component of heterogeneous jobs.
    (Valid for jobs only)
    .TP
    \fBlastschedeval\fR
    Prints the last time the job was evaluated for scheduling.
    (Valid for jobs only)
    .TP
    \fBlicenses\fR
    Licenses reserved for the job.
    (Valid for jobs only)
    .TP
    \fBmaxcpus\fR
    Prints the max number of CPUs allocated to the job.
    (Valid for jobs only)
    .TP
    \fBmaxnodes\fR
    Prints the max number of nodes allocated to the job.
    (Valid for jobs only)
    .TP
    \fBmcslabel\fR
    Prints the MCS_label of the job.
    (Valid for jobs only)
    .TP
    \fBmem\-per-tres\fR
    Print the memory (in MB) required per trackable resources allocated to the job
    or job step.
    .TP
    \fBminmemory\fR
    Minimum size of memory (in MB) requested by the job.
    (Valid for jobs only)
    \fmintime\fR
    .TP
    \fBname\fR
    Job or job step name.
    (Valid for jobs and job steps)
    .TP
    \fBnetwork\fR
    The network that the job is running on.
    (Valid for jobs and job steps)
    .TP
    \fBnice\fR
    Nice value (adjustment to a job's scheduling priority).
    (Valid for jobs only)
    .TP
    \fBnodes\fR
    List of nodes allocated to the job or job step. In the case of a
    \fICOMPLETING\fR job, the list of nodes will comprise only those
    nodes that have not yet been returned to service.
    (Valid job steps only)
    .TP
    \fBnodelist\fR
    List of nodes allocated to the job or job step. In the case of a
    \fICOMPLETING\fR job, the list of nodes will comprise only those
    nodes that have not yet been returned to service.
    (Valid for jobs only)
    .TP
    \fBntperboard\fR
    The number of tasks per board allocated to the job.
    (Valid for jobs only)
    .TP
    \fBntpercore\fR
    The number of tasks per core allocated to the job.
    (Valid for jobs only)
    .TP
    \fBntpernode\fR
    The number of task per node allocated to the job.
    (Valid for jobs only)
    .TP
    \fBntpersocket\fR
    The number of tasks per socket allocated to the job.
    (Valid for jobs only)
    .TP
    \fBnumcpus\fR
    Number of CPUs (processors) requested by the job or allocated to
    it if already running.  As a job is completing, this number will
    reflect the current number of CPUs allocated.
    (Valid for jobs and job steps)
    .TP
    \fBnumnodes\fR
    Number of nodes allocated to the job or the minimum number of nodes
    required by a pending job. The actual number of nodes allocated to a pending
    job may exceed this number if the job specified a node range count (e.g.
    minimum and maximum node counts) or the job specifies a processor
    count instead of a node count and the cluster contains nodes with varying
    Cluster ID where federated job originated from.
    (Valid for federated jobs only)
    .TP
    \fBoversubscribe\fR
    Can the compute resources allocated to the job be over subscribed by other jobs.
    The resources to be over subscribed can be nodes, sockets, cores, or
    hyperthreads depending upon configuration.
    The value will be "YES" if the job was submitted with the oversubscribe option
    or the partition is configured with OverSubscribe=Force,
    "NO" if the job requires exclusive node access,
    "USER" if the allocated compute nodes are dedicated to a single user,
    "MCS" if the allocated compute nodes are dedicated to a single security class
    (See MCSPlugin and MCSParameters configuration parameters for more information),
    "OK" otherwise (typically allocated dedicated CPUs),
    (Valid for jobs only)
    .TP
    \fBpackjobid\fR
    Job ID of the heterogeneous job leader.
    .TP
    \fBpackjoboffset\fR
    Zero origin offset within a collection of heterogeneous jobs.
    .TP
    \fBpackjobidset\fR
    Expression identifying all job IDs within a heterogeneous job.
    .TP
    \fBpartition\fR
    Partition of the job or job step.
    (Valid for jobs and job steps)
    .TP
    \fBpriority\fR
    Priority of the job (converted to a floating point number between 0.0 and 1.0).
    Also see \fBprioritylong\fR.
    (Valid for jobs only)
    .TP
    \fBprioritylong\fR
    Priority of the job (generally a very large unsigned integer).
    Also see \fBpriority\fR.
    (Valid for jobs only)
    .TP
    \fBprofile\fR
    Profile of the job.
    (Valid for jobs only)
    .TP
    \fBpreemptime\fR
    The preempt time for the job.
    (Valid for jobs only)
    .TP
    \fBqos\fR
    Quality of service associated with the job.
    (Valid for jobs only)
    .TP
    \fBreason\fR
    Indicates if the allocated nodes should be rebooted before starting the job.
    (Valid on jobs only)
    .TP
    \fBreqnodes\fR
    List of node names explicitly requested by the job.
    (Valid for jobs only)
    .TP
    \fBreqswitch\fR
    The max number of requested switches by for the job.
    (Valid for jobs only)
    .TP
    \fBrequeue\fR
    Prints whether the job will be requeued on failure.
    (Valid for jobs only)
    .TP
    \fBreservation\fR
    Reservation for the job.
    (Valid for jobs only)
    .TP
    \fBresizetime\fR
    The amount of time changed for the job to run.
    (Valid for jobs only)
    .TP
    \fBrestartcnt\fR
    The number of checkpoint restarts for the job.
    (Valid for jobs only)
    .TP
    \fBresvport\fR
    Reserved ports of the job.
    (Valid for job steps only)
    .TP
    \fBschednodes\fR
    For pending jobs, a list of the nodes expected to be used when the job is
    started.
    (Valid for jobs only)
    .TP
    \fBsct\fR
    Number of requested sockets, cores, and threads (S:C:T) per node for the job.
    When (S:C:T) has not been set, "*" is displayed.
    (Valid for jobs only)
    .TP
    \fBselectjobinfo\fR
    Node selection plugin specific data for a job. Possible data includes:
    Geometry requirement of resource allocation (X,Y,Z dimensions),
    Connection type (TORUS, MESH, or NAV == torus else mesh),
    Permit rotation of geometry (yes or no),
    Node use (VIRTUAL or COPROCESSOR), etc.
    (Valid for jobs only)
    .TP
    \fBsiblingsactive\fR
    Cluster names of where federated sibling jobs exist.
    (Valid for federated jobs only)
    Number of sockets per node requested by the job.
    This reports the value of the \fBsrun \-\-sockets\-per\-node\fR option.
    When \-\-sockets\-per\-node has not been set, "*" is displayed.
    (Valid for jobs only)
    .TP
    \fBsperboard\fR
    Number of sockets per board allocated to the job.
    (Valid for jobs only)
    .TP
    \fBstarttime\fR
    Actual or expected start time of the job or job step.
    (Valid for jobs and job steps)
    .TP
    \fBstate\fR
    Job state in extended form.
    See the \fBJOB STATE CODES\fR section below for a list of possible states.
    (Valid for jobs only)
    .TP
    \fBstatecompact\fR
    Job state in compact form.
    See the \fBJOB STATE CODES\fR section below for a list of possible states.
    (Valid for jobs only)
    .TP
    \fBstderr\fR
    The directory for standard error to output to.
    (Valid for jobs only)
    .TP
    \fBstdin\fR
    The directory for standard in.
    (Valid for jobs only)
    .TP
    \fBstdout\fR
    The directory for standard out to output to.
    (Valid for jobs only)
    .TP
    \fBstepid\fR
    Job or job step id.
    In the case of job arrays, the job ID format will be of the form
    "<base_job_id>_<index>".
    (Valid forjob steps only)
    .TP
    \fBstepname\fR
    job step name.
    (Valid for job steps only)
    .TP
    \fBstepstate\fR
    The state of the job step.
    (Valid for job steps only)
    .TP
    \fBsubmittime\fR
    The time that the job was submitted at.
    (Valid for jobs only)
    limit.
    The value may be "NOT_SET" if not yet established or "UNLIMITED" for no limit.
    (Valid for jobs only)
    .TP
    \fBtimelimit\fR
    Timelimit for the job or job step.
    (Valid for jobs and job steps)
    .TP
    \fBtimeused\fR
    Time used by the job or job step in days\-hours:minutes:seconds.
    The days and hours are printed only as needed.
    For job steps this field shows the elapsed time since execution began
    and thus will be inaccurate for job steps which have been suspended.
    Clock skew between nodes in the cluster will cause the time to be inaccurate.
    If the time is obviously wrong (e.g. negative), it displays as "INVALID".
    (Valid for jobs and job steps)
    .TP
    \fBtres\-alloc\fR
    Print the trackable resources allocated to the job if running.
    If not running, then print the trackable resources requested by the job.
    .TP
    \fBtres\-bind\fR
    Print the trackable resources task binding requested by the job or job step.
    .TP
    \fBtres\-freq\fR
    Print the trackable resources frequencies requested by the job or job step.
    .TP
    \fBtres\-per\-job\fR
    Print the trackable resources requested by the job.
    .TP
    \fBtres\-per\-node\fR
    Print the trackable resources per node requested by the job or job step.
    .TP
    \fBtres\-per\-socket\fR
    Print the trackable resources per socket requested by the job or job step.
    .TP
    \fBtres\-per\-step\fR
    Print the trackable resources requested by the job step.
    .TP
    \fBtres\-per\-task\fR
    Print the trackable resources per task requested by the job or job step.
    .TP
    \fBuserid\fR
    User ID for a job or job step.
    (Valid for jobs and job steps)
    .TP
    \fBusername\fR
    User name for a job or job step.
    (Valid for jobs and job steps)
    .TP
    \fBwait4switch\fR
    The amount of time to wait for the desired number of switches.
    list of partition names.

    .TP
    \fB\-P\fR, \fB\-\-priority\fR
    For pending jobs submitted to multiple partitions, list the job once per
    partition. In addition, if jobs are sorted by priority, consider both the
    partition and job priority. This option can be used to produce a list of
    pending jobs in the same order considered for scheduling by Slurm with
    appropriate additional options (e.g. "\-\-sort=\-p,i \-\-states=PD").

    .TP
    \fB\-q <qos_list>\fR, \fB\-\-qos=<qos_list>\fR
    Specify the qos(s) of the jobs or steps to view. Accepts a comma
    separated list of qos's.

    .TP
    \fB\-R\fR, \fB\-\-reservation\fR=\fIreservation_name\fR
    Specify the reservation of the jobs to view.

    .TP
    \fB\-s\fR, \fB\-\-steps\fR
    Specify the job steps to view.  This flag indicates that a comma separated list
    of job steps to view follows without an equal sign (see examples).
    The job step format is "job_id[_array_id].step_id". Defaults to all job
    steps. Since this option's argument is optional, for proper parsing
    the single letter option must be followed immediately with the value
    and not include a space between them. For example "\-s1008.0" and not
    "\-s 1008.0".

    .TP
    \fB\-\-sibling\fR
    Show all sibling jobs on a federated cluster. Implies \-\-federation.

    .TP
    \fB\-S <sort_list>\fR, \fB\-\-sort=<sort_list>\fR
    Specification of the order in which records should be reported.
    This uses the same field specification as the <output_format>.
    The long format option "cluster" can also be used to sort jobs or job steps by
    cluster name (e.g. federated jobs).
    Multiple sorts may be performed by listing multiple sort fields
    separated by commas.
    The field specifications may be preceded by "+" or "\-" for
    ascending (default) and descending order respectively.
    For example, a sort value of "P,U" will sort the
    records by partition name then by user id.
    The default value of sort for jobs is "P,t,\-p" (increasing partition
    name then within a given partition by increasing job state and then
    decreasing priority).
    The default value of sort for job steps is "P,i" (increasing partition
    name then within a given partition by increasing step id).

    .TP
    Specify the states of jobs to view.  Accepts a comma separated list of
    state names or "all". If "all" is specified then jobs of all states will be
    reported. If no state is specified then pending, running, and completing
    jobs are reported. See the \fBJOB STATE CODES\fR section below for a list of
    valid states. Both extended and compact forms are valid.
    Note the \fB<state_list>\fR supplied is case insensitive ("pd" and "PD" are
    equivalent).

    .TP
    \fB\-u <user_list>\fR, \fB\-\-user=<user_list>\fR
    Request jobs or job steps from a comma separated list of users.
    The list can consist of user names or user id numbers.
    Performance of the command can be measurably improved for systems with large
    numbers of jobs when a single user is specified.

    .TP
    \fB\-\-usage\fR
    Print a brief help message listing the \fBsqueue\fR options.

    .TP
    \fB\-v\fR, \fB\-\-verbose\fR
    Report details of squeues actions.

    .TP
    \fB\-V\fR , \fB\-\-version\fR
    Print version information and exit.

    .TP
    \fB\-w <hostlist>\fR, \fB\-\-nodelist=<hostlist>\fR
    Report only on jobs allocated to the specified node or list of nodes.
    This may either be the \fBNodeName\fR or \fBNodeHostname\fR
    as defined in \fBslurm.conf(5)\fR in the event that they differ.
    A node_name of \fBlocalhost\fR is mapped to the current host name.

    .SH "JOB REASON CODES"
    These codes identify the reason that a job is waiting for execution.
    A job may be waiting for more than one reason, in which case only
    one of those reasons is displayed.
    .TP 22
    \fBAssociationJobLimit\fR
    The job's association has reached its maximum job count.
    .TP
    \fBAssociationResourceLimit\fR
    The job's association has reached some resource limit.
    .TP
    \fBAssociationTimeLimit\fR
    The job's association has reached its time limit.
    .TP
    \fBBadConstraints\fR
    The job's constraints can not be satisfied.
    .TP
    \fBBeginTime\fR
    \fBInvalidAccount\fR
    The job's account is invalid.
    .TP
    \fBInvalidQOS\fR
    The job's QOS is invalid.
    .TP
    \fBJobHeldAdmin\fR
    The job is held by a system administrator.
    .TP
    \fBJobHeldUser\fR
    The job is held by the user.
    .TP
    \fBJobLaunchFailure\fR
    The job could not be launched.
    This may be due to a file system problem, invalid program name, etc.
    .TP
    \fBLicenses\fR
    The job is waiting for a license.
    .TP
    \fBNodeDown\fR
    A node required by the job is down.
    .TP
    \fBNonZeroExitCode\fR
    The job terminated with a non\-zero exit code.
    .TP
    \fBPartitionDown\fR
    The partition required by this job is in a DOWN state.
    .TP
    \fBPartitionInactive\fR
    The partition required by this job is in an Inactive state and not able to
    start jobs.
    .TP
    \fBPartitionNodeLimit\fR
    The number of nodes required by this job is outside of it's
    partitions current limits.
    Can also indicate that required nodes are DOWN or DRAINED.
    .TP
    \fBPartitionTimeLimit\fR
    The job's time limit exceeds it's partition's current time limit.
    .TP
    \fBPriority\fR
    One or more higher priority jobs exist for this partition or advanced reservation.
    .TP
    \fBProlog\fR
    It's PrologSlurmctld program is still running.
    .TP
    \fBQOSJobLimit\fR
    The job's QOS has reached its maximum job count.
    .TP
    \fBQOSResourceLimit\fR
    The job's QOS has reached some resource limit.
    .TP
    \fBResources\fR
    The job is waiting for resources to become available.
    .TP
    \fBSystemFailure\fR
    Failure of the Slurm system, a file system, the network, etc.
    .TP
    \fBTimeLimit\fR
    The job exhausted its time limit.
    .TP
    \fBQOSUsageThreshold\fR
    Required QOS threshold has been breached.
    .TP
    \fBWaitingForScheduling\fR
    No reason has been set for this job yet.
    Waiting for the scheduler to determine the appropriate reason.

    .SH "JOB STATE CODES"
    Jobs typically pass through several states in the course of their
    execution.
    The typical states are PENDING, RUNNING, SUSPENDED, COMPLETING, and COMPLETED.
    An explanation of each state follows.
    .TP 20
    \fBBF  BOOT_FAIL\fR
    Job terminated due to launch failure, typically due to a hardware failure
    (e.g. unable to boot the node or block and the job can not be requeued).
    .TP
    \fBCA  CANCELLED\fR
    Job was explicitly cancelled by the user or system administrator.
    The job may or may not have been initiated.
    .TP
    \fBCD  COMPLETED\fR
    Job has terminated all processes on all nodes with an exit code of zero.
    .TP
    \fBCF  CONFIGURING\fR
    Job has been allocated resources, but are waiting for them to become ready for use
    (e.g. booting).
    .TP
    \fBCG  COMPLETING\fR
    Job is in the process of completing. Some processes on some nodes may still be active.
    .TP
    \fBDL  DEADLINE\fR
    Job terminated on deadline.
    .TP
    \fBF   FAILED\fR
    Job terminated with non\-zero exit code or other failure condition.
    .TP
    \fBNF  NODE_FAIL\fR
    Job terminated due to failure of one or more allocated nodes.
    .TP
    \fBOOM OUT_OF_MEMORY\fR
    Job experienced out of memory error.
    .TP
    .TP
    \fBRH  REQUEUE_HOLD\fR
    Held job is being requeued.
    .TP
    \fBRQ  REQUEUED\fR
    Completing job is being requeued.
    .TP
    \fBRS  RESIZING\fR
    Job is about to change size.
    .TP
    \fBRV  REVOKED\fR
    Sibling was removed from cluster due to other cluster starting the job.
    .TP
    \fBSI  SIGNALING\fR
    Job is being signaled.
    .TP
    \fBSE  SPECIAL_EXIT\fR
    The job was requeued in a special state. This state can be set by
    users, typically in EpilogSlurmctld, if the job has terminated with
    a particular exit value.
    .TP
    \fBSO  STAGE_OUT\fR
    Job is staging out files.
    .TP
    \fBST  STOPPED\fR
    Job has an allocation, but execution has been stopped with SIGSTOP signal.
    CPUS have been retained by this job.
    .TP
    \fBS   SUSPENDED\fR
    Job has an allocation, but execution has been suspended and CPUs have been
    released for other jobs.
    .TP
    \fBTO  TIMEOUT\fR
    Job terminated upon reaching its time limit.

    .SH "ENVIRONMENT VARIABLES"
    .PP
    Some \fBsqueue\fR options may be set via environment variables. These
    environment variables, along with their corresponding options, are listed
    below. (Note: Commandline options will always override these settings.)
    .TP 20
    \fBSLURM_BITSTR_LEN\fR
    Specifies the string length to be used for holding a job array's task ID
    expression.
    The default value is 64 bytes.
    A value of 0 will print the full expression with any length required.
    Larger values may adversely impact the application performance.
    .TP
    \fBSLURM_CLUSTERS\fR
    Same as \fB\-\-clusters\fR
    .TP
    "%a %T" will report the day of the week and a time stamp (e.g. "Mon 12:34:56").
    .TP
    \fBSQUEUE_ACCOUNT\fR
    \fB\-A <account_list>, \-\-account=<account_list>\fR
    .TP
    \fBSQUEUE_ALL\fR
    \fB\-a, \-\-all\fR
    .TP
    \fBSQUEUE_ARRAY\fR
    \fB\-r, \-\-array\fR
    .TP
    \fBSQUEUE_NAMES\fR
    \fB\-\-name=<name_list>\fR
    .TP
    \fBSQUEUE_FEDERATION\fR
    \fB\-\-federation\fR
    .TP
    \fBSQUEUE_FORMAT\fR
    \fB\-o <output_format>, \-\-format=<output_format>\fR
    .TP
    \fBSQUEUE_FORMAT2\fR
    \fB\-O <output_format>, \-\-Format=<output_format>\fR
    .TP
    \fBSQUEUE_LICENSES\fR
    \fB\-p-l <license_list>, \-\-license=<license_list>\fR
    .TP
    \fBSQUEUE_LOCAL\fR
    \fB\-\-local\fR
    .TP
    \fBSQUEUE_PARTITION\fR
    \fB\-p <part_list>, \-\-partition=<part_list>\fR
    .TP
    \fBSQUEUE_PRIORITY\fR
    \fB\-P\fR, \fB\-\-priority\fR
    .TP
    \fBSQUEUE_QOS\fR
    \fB\-p <qos_list>, \-\-qos=<qos_list>\fR
    .TP
    \fBSQUEUE_SIBLING\fR
    \fB\-\-sibling\fR
    .TP
    \fBSQUEUE_SORT\fR
    \fB\-S <sort_list>, \-\-sort=<sort_list>\fR
    .TP
    \fBSQUEUE_STATES\fR
    \fB\-t <state_list>, \-\-states=<state_list>\fR
    .TP
    \fBSQUEUE_USERS\fR
    \fB\-u <user_list>, \-\-users=<user_list>\fR

    .SH "EXAMPLES"
    .eo

    .eo
    Print the job steps in the debug partition sorted by user:
    .br
    # squeue -s -p debug -S u
    .br
      STEPID        NAME PARTITION     USER      TIME NODELIST
    .br
     65552.1       test1     debug    alice      0:23 dev[1-4]
    .br
     65562.2     big_run     debug      bob      0:18 dev22
    .br
     65550.1      param1     debug  candice   1:43:21 dev[6-12]
    .ec

    .eo
    Print information only about jobs 12345,12345, and 12348:
    .br
    # squeue --jobs 12345,12346,12348
    .br
     JOBID PARTITION NAME USER ST  TIME  NODES NODELIST(REASON)
    .br
     12345     debug job1 dave  R   0:21     4 dev[9-12]
    .br
     12346     debug job2 dave PD   0:00     8 (Resources)
    .br
     12348     debug job3 ed   PD   0:00     4 (Priority)
    .ec

    .eo
    Print information only about job step 65552.1:
    .br
    # squeue --steps 65552.1
    .br
      STEPID     NAME PARTITION    USER    TIME  NODELIST
    .br
     65552.1    test2     debug   alice   12:49  dev[1-4]
    .ec

    .SH "COPYING"
    Copyright (C) 2002\-2007 The Regents of the University of California.
    Produced at Lawrence Livermore National Laboratory (cf, DISCLAIMER).
    .br
    Copyright (C) 2008\-2010 Lawrence Livermore National Security.
    .br
    Copyright (C) 2010\-2016 SchedMD LLC.
    .LP
    This file is part of Slurm, a resource management program.
    For details, see <https://slurm.schedmd.com/>.
    .LP
    Slurm is free software; you can redistribute it and/or modify it under
    the terms of the GNU General Public License as published by the Free