QSTAT(1) Network Queuing Env. 3.3 Last changed: 4-13-98 NNAAMMEE qqssttaatt - Displays the status of NQS queues, requests, and queue complexes SSYYNNOOPPSSIISS qqssttaatt [--aa] [--bb] [--cc] [--CC _c_o_m_p_l_e_x__n_a_m_e] [--ff] [--hh _t_a_r_g_e_t__h_o_s_t] [--ii] [--jj] [--ll] [--LL] [--mm] [--pp] [--rr] [--ss] [--uu _u_s_e_r_n_a_m_e] [_q_u_e_u_e_s] [_r_e_q_u_e_s_t_i_d_s] IIMMPPLLEEMMEENNTTAATTIIOONN IRIX systems UNICOS/mk systems UNICOS systems AIX systems Digital UNIX systems HP-UX systems Solaris systems DDEESSCCRRIIPPTTIIOONN The qqssttaatt command displays the status of Network Queuing System (NQS) queues, requests, and queue complexes. If you do not specify a target host, the display information is obtained from the local host. If you omit all options and arguments, a summary of each NQS queue on the local host is displayed in an 80-column, nonpaginated format. Options let you select the queue type, display content, and display format. You can limit the display content to a particular queue, request, or queue complex. For an explanation of the various items in the displays, see the EXAMPLES section. The header indicates the origin and type of each display. To display requests, you must have proper validation. For more information on user validation, see the NOTES section on the qqssuubb(1) man page. If the UNICOS multilevel security (MLS) feature or the UNICOS/mk security enhancements are enabled on your system and NQS is configured to enforce mandatory access control (MAC), your active label must dominate the job submission label to receive status information. To display the job submission and execution label information for a specific request, use the qqssttaatt --ff command. NQS managers and operators bypass the MAC checks. The qqssttaatt command supports the following options: --aa Displays summary information about all of your requests. If your UNICOS or UNICOS/mk NQS administrator has set the NNQQEE__NNQQSS__QQSSTTAATT__SSHHOOWWAALLLL customized variable to 1, this option displays all user requests. --bb Displays information about batch queues. --cc Displays summary information about queue complexes. You cannot use this option with the --hh option because of restrictions in the NQS protocol. --CC _c_o_m_p_l_e_x__n_a_m_e Displays information about a particular queue complex. --ff Displays full details about the specified NQS queues or requests. --hh _t_a_r_g_e_t__h_o_s_t Specifies the target NQS host from which display information will be obtained. If your site is running with the UNICOS multilevel security (MLS) feature enabled or the UNICOS/mk security enhancements enabled, you cannot display information from a remote host if the execution host has a workstation access list (WAL) entry for the host of origin that restricts your access to NQS services. --ii Displays information about requests that are awaiting processing in batch and pipe queues. --jj Displays the contents of the NQS batch request job log file; requires a _r_e_q_u_e_s_t_i_d_s argument. --ll Displays summary information about NQS queue limits. --LL Displays summary information about NQS queue complex limits. --mm (Cray MPP systems only) Displays information about Cray MPP NQS queue limits. For CRAY T3E systems, this display shows the CPU time only for application processing elements (PEs). --pp Displays information about NQS pipe queues. --rr Displays a summary of requests that are currently being processed in NQS batch and pipe queues. --ss Specifies a 40-column display (contains less information than the 80-column display). --uu _u_s_e_r_n_a_m_e Restricts the requests displayed to those owned by _u_s_e_r_n_a_m_e; you cannot use --uu with options that display queue summaries. To issue the qqssttaatt request as _u_s_e_r_n_a_m_e, the originating client user must have proper validation. User _u_s_e_r_n_a_m_e must create an appropriate entry in his or her ..rrhhoossttss or ..nnqqsshhoossttss file at the target NQS server. This option may not be valid on UNICOS systems with the MLS feature or UNICOS/mk systems with security enhancements. When the UNICOS MLS feature or the UNICOS/mk security enhancements are enabled, the system might be configured to require the //eettcc//hhoossttss..eeqquuiivv and ..rrhhoossttss files to each contain a match for the remote host and require that the remote user and local user names match (that is, the --uu option is not allowed). _q_u_e_u_e_s Displays information for the specified queues. Queue names have the following format: _q_u_e_u_e__n_a_m_e [@@_h_o_s_t__n_a_m_e] The _q_u_e_u_e__n_a_m_e argument can be any valid NQS queue name. The @@_h_o_s_t__n_a_m_e argument is the NQS host on which the queue is defined; if you omit it, NQS uses the host specified by the --hh option or the local NQS server (if you omit the --hh option). _r_e_q_u_e_s_t_i_d_s Displays information about the specified requests. Requests are specified as follows: _s_e_q_u_e_n_c_e__n_u_m_b_e_r [.._o_r_i_g__h_o_s_t] [@@_c_u_r_r__h_o_s_t] The _s_e_q_u_e_n_c_e__n_u_m_b_e_r argument is the number assigned to the request when it was originally submitted. The _o_r_i_g__h_o_s_t part of the identifier is the original host of submission; if you omit it, NQS uses the local NQS server. The _c_u_r_r__h_o_s_t part of the identifier is the NQS server on which the request currently resides. If you omit it, NQS uses the server specified by the --hh option. If you omit the --hh option, NQS uses the local NQS server. QQuueeuuee SSttaattuuss The queue status is shown after the word SSttaattuuss:: at the top right of the detailed queue display (shown by using the --ff option; see the Detailed Queue Display subsection in the EXAMPLES section). Two properties define the status of a queue. The first property indicates whether you can submit requests to the queue. It can be one of the following: EENNAABBLLEEDD Requests can be accepted into the queue. DDIISSAABBLLEEDD Requests cannot be accepted (although NQS is running at the local host). The operator has disabled the queue. LLOOAADDEEDD Requests temporarily cannot be accepted (although NQS is running at the local host). This queue is a load-only queue that has reached its run limit. When any request that is currently in this queue leaves the queue, the status returns to EENNAABBLLEEDD. CCLLOOSSEEDD Requests cannot be accepted because NQS is not running at the local host. The second property indicates how the queue is currently executing requests. It can be one of the following: SSTTOOPPPPEEDD New queued requests are inhibited from running, and no requests are currently running in the queue. SSTTOOPPPPIINNGG New queued requests are inhibited from running, but requests are currently running that will be allowed to complete execution. RRUUNNNNIINNGG Queued requests are permitted to run, and requests in this queue are currently running. IINNAACCTTIIVVEE Queued requests are permitted to run, but no requests are currently running. SSHHUUTTDDOOWWNN NQS is not running at the local host on which the queue resides. RReeqquueesstt SSttaattuuss The request status is shown after the word SSttaattuuss:: at the top right of the detailed request display (shown by using the --ff option); an abbreviated form of the status also is displayed under the SSTT column of the request summary display (shown by using the --aa option). In the following descriptions, the item in the left column shows how the status is displayed in the request summary display. The request status is expressed in two parts: the major status and the minor status. The major status of a request can be one of the following: AA AARRRRIIVVIINNGG The request is arriving in a queue. CC CCHHEECCKKPPOOIINNTTEEDD (UNICOS, UNICOS/mk, and IRIX systems only) The request in a batch queue was checkpointed and is no longer running. DD DDEEPPAARRTTIINNGG The request left a pipe queue before its arrival at a destination queue. EE EEXXIITTIINNGG The request in a batch queue completed execution and is currently leaving the system. HH HHEELLDD The request was prevented from entering another state by operator action. If the request had already been running, a restart file was created. QQ QQUUEEUUEEDD The request is in a queue and is eligible for routing or running. PP PPRREEEEMMPPTTEEDD The request was preempted for SDS usage. When a request is preempted, a restart file is created. Not all platforms support SDS usage. RR RROOUUTTIINNGG The request is being routed to another queue (no minor status is associated with this status). RR RRUUNNNNIINNGG The request is in a batch queue and is currently being processed. SS SSUUSSPPEENNDDEEDD The request is executing in a batch queue, but its execution was suspended. UU UUNNKKNNOOWWNN The state of the request cannot be determined. WW WWAAIITTIINNGG The request is prevented from proceeding either by a date and/or time constraint imposed at the time of submission (by the ccqqssuubb --aa command) or by the inaccessibility of a pipe queue destination. no entry <> The status of the request is changing. This request status also can be displayed if the request was moved into the running subqueue but the associated session has not yet been created, the NQS daemon aborted or hung while the request was running, or the shepherd process is taking a long time to process the request exit. The minor status of a request can be one of the following: _n_u_m_b_e_r The number of processes started by the request that are currently active. This value can be replaced by the xxss or xxww status for requests that are run using a supported local scheduler extension, such as Miser on IRIX 6.5 systems and later. ccee (Cray MPP systems only) The complex Cray MPP processing element (PE) limit was reached. ccgg The complex group run limit was reached. ccmm The complex memory limit was reached. ccqq The complex quickfile (SDS) limit was reached. ccrr The complex run limit was reached. ccuu The complex user run limit was reached. dduu The destination queue is unavailable. ggee (Cray MPP systems only) The global Cray MPP processing element (PE) limit was reached. gggg The global group run limit was reached. ggmm The global memory limit was reached. ggqq The global quickfile (SDS) limit was reached. ggrr The global run limit was reached. ggtt The global tape drive limit was reached. gguu The global user run limit was reached. llmm A license could not be obtained for the request. mmdd (CRAY T3D systems only) The CRAY T3D device is not accessible. mmpp (Cray MPP systems only) Insufficient processing elements (PEs) are available on the Cray MPP system. nnuu The Network Load Balancer (NLB) server is unavailable. oopp The current major status of the request has occurred through operator action. qqee (Cray MPP systems only) The queue Cray MPP processing element (PE) limit was reached. qqgg The queue group run limit was reached. qqmm The queue memory limit was reached. qqqq The queue quickfile limit was reached. qqrr The queue run limit was reached. qqss The queue in which the request resides was stopped. qquu The queue user run limit was reached. rrjj (UNICOS systems only) The Unified Resource Manager (URM) rejected the request. sshh The system was shut down. ttdd The UNICOS tape daemon is unavailable, and the request asks for tape resources. uuss (UNICOS systems only) The request is in the URM scheduling pool. xxss (Available only for the Miser local scheduler running on IRIX 6.5 systems and later) The request was scheduled into a local scheduler on the execution host. When a request is run using a local scheduler, this status will be displayed instead of the number of processes. xxww (Available only for the Miser local scheduler running on IRIX 6.5 systems and later) The request is waiting to be scheduled by the local scheduler on the execution host. ???? The current status of the request is unknown. You can see the values of the limits reached in the detailed queue and queue complex displays (see the EXAMPLES section). NNOOTTEESS A batch request submitted from a UNICOS interactive session to a local NQS pipe queue for routing to a batch queue typically progresses through the following states at a local pipe queue: SSttaattee DDeessccrriippttiioonn qquueeuueedd Awaiting routing to another queue rroouuttiinngg Being moved to another queue A request progresses through the following states in a batch queue: SSttaattee DDeessccrriippttiioonn aarrrriivviinngg Being moved from another queue qquueeuueedd Awaiting processing rruunnnniinngg Being processed eexxiittiinngg Processing complete ddeeppaarrttiinngg Left the queue but not yet deleted An executing request also can have the following states: SSttaattee DDeessccrriippttiioonn hheelldd Held by operator action. pprreeeemmpptteedd Preempted by operator. cchheecckkppooiinntteedd (UNICOS, UNICOS/mk, and IRIX systems only) Saved for later processing at an NQS restart. ssuussppeennddeedd An operator or a URM directive temporarily suspended processing URM applies only to UNICOS systems. The ordering of requests within a queue does not always determine the order in which the request is processed; the NQS request scheduler determines the processing order, depending on the various limits that the system administrator or operator imposes. When requests are run on a system that is using the mmiisseerr nnoorrmmaall scheduling option, the order of the requests in a queue will determine the order in which the requests are evaluated before they are submitted to the Miser scheduler. The order that requests are executed through the Miser scheduler depends on the resources (CPU and memory) that are available on the system. If the job scheduling class for a system is mmiisseerr nnoorrmmaall, a request will use the Miser scheduler only when all of the following criteria are met: 1. The request specifies Miser resource options. 2. The job scheduling class is mmiisseerr nnoorrmmaall. 3. Miser is active on the execution host. 4. A valid Miser queue has been assigned as a destination for the NQS batch queue. If any of these criteria fail, the request will be scheduled using the OS default scheduler. EEXXIITT SSTTAATTUUSS An exit status of 0 indicates normal use. An exit status of 1 indicates a user error. An exit status of 2 indicates an NQS error. MMEESSSSAAGGEESS The standard error file (ssttddeerrrr) lists explanatory messages for all irregularities. BBUUGGSS The effect of specifying multiple display options is indeterminate. EEXXAAMMPPLLEESS QQuueeuuee SSuummmmaarryy DDiissppllaayy The following command displays a summary of all NQS queues at the local host: qqssttaatt The display is divided into batch and pipe queues. Each entry represents the state of one queue. The columns of this display are as follows: CCoolluummnn DDeessccrriippttiioonn QQUUEEUUEE NNAAMMEE Name of the queue. LLIIMM Run limit. TTOOTT Total number of requests in the queue. EENNAA Queue availability. This column indicates whether the queue is enabled to accept requests (yyeess), (nnoo), or (mmaaxx). These values correspond to the states EENNAABBLLEEDD, DDIISSAABBLLEEDD, and LLOOAADDEEDD, respectively. For more information, see the Queue Status subsection. SSTTSS Queue status. This column indicates whether queued requests are permitted to run (oonn) or not run (ooffff). QQUUEE Number of queued requests. RROOUU//RRUUNN Number of routing and running requests. WWAAII//HHLLDD//AARRRR//EEXXII//DDEEPP Number of waiting, holding, arriving, exiting, and departing requests. DDEESSTTIINNAATTIIOONNSS Destinations of a pipe queue (displayed in the order in which NQS scans them when routing a request). For a detailed explanation of queue and request status, see the Detailed Request Display and Detailed Queue Display subsections in the EXAMPLES section. The last line of each display shows the global limit (under the LLIIMM column) and the total number of requests in each category. UUNNIICCOOSS QQuueeuuee aanndd QQuueeuuee CCoommpplleexx LLiimmiittss The following command shows the UNICOS limits that the system administrator defines for each batch queue and the amount of that resource currently being used: qqssttaatt --ll To show a similar display for queue complexes, use the following command: qqssttaatt --LL Some columns in these displays have two entries separated by the // symbol. The first entry is the limit set for the queue; the second entry is the current use. The ---- symbols mean that no limit was explicitly set for the queue; the **** symbols mean that the string uunnlliimmiitteedd was specified. The columns in the displays have the following meanings: CCoolluummnn DDeessccrriippttiioonn QQUUEEUUEE NNAAMMEE Name of the queue RRUUNN Number of requests allowed to execute simultaneously in the queue or queue complex, followed by the number currently executing MMEEMMOORRYY Maximum amount of memory (in kilowords) that all requests in the queue or queue complex are allowed to use at once, followed by the amount of memory (in kilowords) currently being used QQUUIICCKKFFLL The maximum amount of quickfile (SDS) space (in kilowords) that all requests in the queue or queue complex can use, followed by the amount of quickfile space (in kilowords) currently being used UUSSRR The maximum number of requests that one user is allowed to have running in the queue or queue complex at any one time GGRRPP The maximum number of requests that one user group is allowed to have running in the queue or queue complex at any one time CCrraayy MMPPPP QQuueeuuee LLiimmiittss The following command shows the Cray MPP limits that the system administrator defines for each batch queue and the amount of that resource currently being used: qqssttaatt --mm In this display, two entries are separated by the // symbol. The first entry is the limit set for the queue; the second entry is the current use. The ---- symbols mean that no limit was explicitly set for the queue; the **** symbols mean that the maximum was specified. The columns in the displays have the following meanings: CCoolluummnn DDeessccrriippttiioonn QQUUEEUUEE NNAAMMEE Name of the queue RRUUNN Number of requests allowed to execute simultaneously in the queue, followed by the number currently executing PPEE''SS Maximum number of Cray MPP processing elements (PEs) that all requests in the queue are allowed to use at once, followed by the number currently in use RReeqquueesstt SSuummmmaarryy DDiissppllaayy The following command displays a summary of all requests running at the local NQS system: qqssttaatt --aa Each entry represents the current state of a request. Owners and users who have NQS administrator status can display their requests at the local NQS server. Users who have the correct validation can display requests at a remote NQS server. CCoolluummnn DDeessccrriippttiioonn IIDDEENNTTIIFFIIEERR A unique identifier that consists of the original request number and the machine from which the request was submitted. RREEQQUUEESSTT NNAAMMEE The name of the request as specified by the user, using the qqssuubb --rr option (or the request file name if --rr was not used). UUSSEERR The current owner of the request (either the name of the user who submitted the request or the name of the user specified by the qqssuubb --uu option if that option was used). QQUUEEUUEE The name of the NQS queue and the NQS server at which the queue is located. JJIIDD The job identifier for an executing request in a batch queue. PPRRTTYY For a request awaiting execution, its intraqueue priority; for an executing request, its nice value. The priority value is not available until after the NQS scheduler examines the queue (the priority field displays only dashes (---) until it examines the queue). After the scheduler examines the queue, the requests are sorted in order of priority. If the request is in a running state, the priority field displays either NNOOWW (this indicates that the request has been manually scheduled) or the nice value of the parent process. If the request is in any other state, the priority field displays either NNOOWW or the intraqueue priority of the request (a value from 1 through 999). Other values in the priority field denote a priority that is not valid. For an executing request that is scheduled by using the sscchheedduullee rreeqquueesstt ffiirrsstt command, the priority field displays FFRRSSTT. For an executing request that is scheduled by using the sscchheedduullee rreeqquueesstt nneexxtt command, the priority field displays NNEEXXTT. For an executing request that is scheduled by using the sscchheedduullee rreeqquueesstt nnooww command, the priority field displays NNOOWW. RREEQQMMEEMM The per-request memory limit for a request awaiting execution; the current memory usage (expressed in kilowords on UNICOS and UNICOS/mk systems and kilobytes on all other supported systems) for an executing request or **** for a request with unlimited per-request memory. RREEQQTTIIMM The per-request CPU time limit for a request awaiting execution; the remaining CPU time (expressed in seconds) for an executing request or **** for a request with unlimited per-request CPU time. SSTT Request state; see the Request Status subsection in the DESCRIPTION section. QQuueeuuee CCoommpplleexx SSuummmmaarryy DDiissppllaayy The following command displays summary information about all queue complexes: qqssttaatt --cc Each entry in the display summarizes the current state of each queue complex. The columns of the display have the following meanings: CCoolluummnn DDeessccrriippttiioonn QQUUEEUUEE CCOOMMPPLLEEXX Name of the queue complex as specified by the NQS manager MMEEMM Number of queues that belong to the complex LLIIMM The maximum number of requests that can run concurrently in the queues that comprise the queue complex TTOOTT The total number of requests currently residing in the queues that comprise the queue complex QQUUEE The total number of requests currently queued in the complex member queues RRUUNN The total number of requests currently executing in the queues that comprise the queue complex WWAAII//HHLLDD//AARRRR//EEXXII The total number of requests currently waiting, holding, arriving, and departing in the queues that comprise the queue complex DDeettaaiilleedd QQuueeuuee CCoommpplleexx DDiissppllaayy The following command shows details of a particular queue complex: qqssttaatt --CC ccoommpp22 This display provides a summary of all queues in a specific complex. For a detailed explanation of the columns, see the preceding Queue Summary Display subsection. The last line of the display shows the complex run limit under the LLIIMM column and the total number of requests in each of the displayed categories. DDeettaaiilleedd RReeqquueesstt DDiissppllaayy The following command displays full details about a particular request: qqssttaatt --ff 99333344 Owners or users who have NQS administrator status can display their requests at the local host. Users who have proper validation can display requests at a remote host. The various fields in this display have the following meanings: FFiieelldd DDeessccrriippttiioonn Initial header The queue type (BBAATTCCHH or PPIIPPEE) in which the request is currently residing, the name of the request, and the host at which it is currently residing. SSttaattuuss:: Current status of the request. See the Request Status subsection in the DESCRIPTION section. NNQQEE TTaasskk IIDD:: The NQE task identifier (tt_i_d) is included if the request was submitted to the NQE database. Otherwise, the entry is --. NNQQSS IIddeennttiiffiieerr:: The NQS request identifier that consists of its sequence number and the host from which the request was submitted. TTaarrggeett UUsseerr:: Current owner of the request (either the name of the user who submitted the request, or the name of the user specified by the qqssuubb option --uu if that was used). GGrroouupp:: Principal group to which the owner of the request belongs. AAccccoouunntt//PPrroojjeecctt:: (For systems running only UNICOS or IRIX 6.2 or later) Account name (UNICOS) or project name (IRIX) under which the request is running. For a local job submission, the Account/Project field is the account name or project name in use when the request is submitted; otherwise, the Account/Project field is the default account name or project name for the user at the local host. PPrriioorriittyy:: Intraqueue priority of the request, computed based on the scheduler weighting factors. (This priority is used to determine the order in which NQS selects a request from within the queue.) If a request is already running, the intraqueue priority has no meaning and displays only dashes (---). For a request that is scheduled by using the sscchheedduullee rreeqquueesstt ffiirrsstt command, the priority is displayed as SSCCHHEEDDUULLEEDD FFIIRRSSTT. For an executing request that is scheduled by using the sscchheedduullee rreeqquueesstt nneexxtt command, the priority field displays SSCCHHEEDDUULLEEDD NNEEXXTT. For a request that is scheduled by using the sscchheedduullee rreeqquueesstt nnooww command, the priority is displayed as SSCCHHEEDDUULLEEDD NNOOWW. For a request that is scheduled by using the sscchheedduullee rreeqquueesstt nnooww pprriimmee command, the priority is displayed as SSCCHHEEDDUULLEEDD NNOOWW PPRRIIMMEE. UUsseerr PPrriioorriittyy//UURRMM PPrriioorriittyy IInnccrreemmeenntt:: The user-requested priority for all systems or the Unified Resource Manager (URM) priority increment for UNICOS systems running URM. The priority is an integer between 0 and 63; the default is 1. If you are running URM, the priority value is passed to URM during request registration. URM adds this value as an increment value to the priority that it calculates for the request. JJoobb iiddeennttiiffiieerr:: UNICOS job identification number (if the request is executing in a batch queue). LLooccaall SScchheedduulleerr:: The name of the local scheduler that was requested by the user and the name of the local scheduler that is being used to run the request. The following are possible values in the display: MMiisseerr IRIX Miser scheduler OOSS ddeeffaauulltt Normal kernel scheduler NNiiccee VVaalluuee:: Execution nice value (if the request is executing in a batch queue). CCrreeaatteedd:: Time the request was created at local host. QQuueeuueedd:: Time the request was queued, time to retry the request if routing, or (if the qqssuubb --aa command was used) the time the request will be queued. LLOOCCAATTIIOONN//QQUUEEUUEE The name of the queue in which the request currently resides and the interqueue priority of that queue. RREESSOOUURRCCEESS The per-process and per-request resource limits, and the amount of each resource that the request has used. For the limits, a value enclosed by << and >> symbols is an assigned default value. Values that are not enclosed by these symbols are limits specified explicitly with qqssuubb(1) options when the request was submitted. FFIILLEESS The path names for the standard output and standard error files that the request produces. This section of the display also shows the file name of the restart file for the request; this file contains the last checkpoint image taken for the request. If no restart file exists, the <> string is displayed rather than the file name. The MMOODDEE column indicates whether the output files are written directly as the request proceeds (as specified by the qqssuubb options --rroo and/or --rree), or spooled at the completion of the request. If the request has completed processing and a file is being spooled by the UNICOS file transfer agent (FTA), the FTA identifier is included in the file name. MMAAIILL Address to which mail should be sent by the NQS system. Also indicates when mail should be sent (for example, when the request begins and when it ends). PPEERRIIOODDIICC CCHHEECCKKPPOOIINNTT (UNICOS, UNICOS/mk, and IRIX systems only) Checkpointing value. The following are possible values in the display: SSyysstteemm:: indicates whether periodic checkpoint is off or on for your NQS server. The NQS manager controls system values and states by using the qqmmggrr(8) command. RReeqquueesstt:: indicates whether periodic checkpoint is on or off for the request. To control request values and states, use the qqaalltteerr(1) command. CCppuu ttiimmee:: indicates the CPU time status and its periodic checkpoint interval for all requests in the NQS system. WWaallll cclloocckk:: indicates the wall-clock status and its periodic checkpoint interval for all requests in the NQS system. LLaasstt cchheecckkppooiinntt:: indicates the date and time of the last periodic checkpoint. SSEECCUURRIITTYY The job security attributes (level and compartments) for the job submission and job execution labels are displayed. If the request has no security attributes, NN//AA is displayed. MMIISSCC RReerruunnnnaabbllee:: indicates whether the request will be permitted to rerun. RReessttaarrttaabbllee:: indicates whether the request will be permitted to recover after a restart of the system. The value can be yyeess, nnoo, or yyeess,,ffoorrccee. A value of yyeess,,ffoorrccee indicates that the request will be restarted even if the files have been changed since the last checkpoint image was created. SShheellll:: indicates the shell that is used to interpret the request. OOrriigg.. OOwwnneerr:: indicates the user ID under whom the request was originally submitted. UUsseerr MMaasskk:: indicates the file creation mode mask. EExxppoorrtteedd VVaarrss:: indicates the variables that were exported from the submitting user's environment to the request. A value of bbaassiicc means that only basic variables are exported from the submitter's environment; a value of aallll means that all variables are exported from the submitter's environment. (See the --xx option of the qqssuubb(1) command.) AATTTTRRIIBBUUTTEESS The request attributes; these strings are supplied through the qqssttaatt --llaa command. The attributes determine which queues can accept the request. DDeettaaiilleedd QQuueeuuee DDiissppllaayy The following command displays full details about an NQS queue: qqssttaatt --ff nnqqeebbaattcchh The fields in this display have the following meanings: FFiieelldd DDeessccrriippttiioonn Initial header line The queue type (BBAATTCCHH or PPIIPPEE), the name of the queue, and the UNICOS host at which it is located. SSttaattuuss:: See the Queue Status subsection of the DESCRIPTION section. PPrriioorriittyy:: Interqueue priority. Determines the order in which NQS looks at the queues for work. EENNTTRRIIEESS The total number of requests in the queue and the number of requests in each state (running, holding, queued, arriving, waiting, and exiting). RRUUNN LLIIMMIITTSS The maximum number of concurrently executing requests for any of the following: the entire queue, one user, or one group. CCOOMMPPLLEEXX MMEEMMBBEERRSSHHIIPP (Batch queues only) The names of the queue complexes of which this queue is a member. LLOOCCAALL SSCCHHEEDDUULLEERR EEXXTTEENNSSIIOONNSS (Batch queues only) Displays information about any local scheduling extensions that have been enabled for the queue. Typically, the name of a Miser scheduler queue and the defined scheduling window are displayed. RREESSOOUURRCCEE UUSSAAGGEE (Batch queues only) The potential maximum and the cumulative usage of resources by requests currently executing in the queue. RREESSOOUURRCCEE LLIIMMIITTSS (Batch queues only) The maximum per-process and per-request resource values that a request can request to enter the queue. DDEESSTTIINNAATTIIOONNSS (Pipe queues only) A list of the destination queues to which requests in this queue may be sent. The order of the names in this section is the order in which NQS considers the queues for forwarding a request. AATTTTRRIIBBUUTTEESS A list of queue attributes. The system administrator sets these strings by using the qqmmggrr sseett aattttrriibbuuttee command. The attributes determine which requests are accepted into this queue. If a request specifies an attribute that the queue does not have, that request is rejected. If a queue has no attributes, this field is not displayed and the queue will accept requests that have any list of attributes. AACCCCEESSSS Indicates any restrictions on requests entering the queue. The RRoouuttee:: field can take the value PPiippee OOnnllyy, which means that it can accept only a request that was routed from a pipe queue, or UUnnrreessttrriicctteedd, which means that you can submit a request directly to the queue by using the qqssuubb command. The UUsseerrss:: field can take the value UUnnrreessttrriicctteedd, which means that requests owned by any user can enter the queue, or it can display a list of the valid users and/or groups whose requests can enter the queue. CCUUMMUULLAATTIIVVEE TTIIMMEE The system and user time accumulated by all requests in the queue since NQS was initiated. RReeqquueesstt JJoobb LLoogg DDiissppllaayy The following command displays the contents of the request's job log: qqssttaatt --jj 11223344 01/21 13:02:59 Request-id is <1234.abc>. 01/21 13:03:01 Submitted to queue by . 01/21 13:03:03 Command line options: . 01/21 13:03:03 Script file options: <-s /bin/csh>. 01/21 13:03:09 Running in queue . 01/21 13:03:15 Finished. 01/21 13:03:15 Returning stderr output file. 01/21 13:03:18 Returning stdout output file. 01/21 13:03:19 Global array session handle is <3917005776737250589>. SSEEEE AALLSSOO qqaalltteerr(1), qqcchhkkppnntt(1), qqddeell(1), qqlliimmiitt(1), qqmmssgg(1), qqssuubb(1) iiaa__ffaaiilluurree(3C), iiaa__ssuucccceessss(3C), iiaa__uusseerr(3C) for information about the UNICOS and UNICOS/mk identification and authentication feature in the _U_N_I_C_O_S _S_y_s_t_e_m _L_i_b_r_a_r_i_e_s _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, publication SR-2080 and the _U_N_I_C_O_S/_m_k _S_y_s_t_e_m _L_i_b_r_a_r_i_e_s _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, publication SR-2680 pprroojjeecctt(4) and pprroojjiidd(4) on IRIX 6.2 or later systems for information about valid user projects nnqqeeiinnffoo(5) for information on the nnqqeeiinnffoo file _N_Q_E _U_s_e_r'_s _G_u_i_d_e, publication SG-2148 This man page is available only online.