CQSTATL(1) Network Queuing Env. 3.3 Last changed: 4-13-98 NNAAMMEE ccqqssttaattll - Displays the status of batch requests and queues from a Network Queuing Environment (NQE) client SSYYNNOOPPSSIISS ccqqssttaattll [--aa] [--bb] [--dd _d_e_s_t__t_y_p_e] [--ff] [--hh _t_a_r_g_e_t__h_o_s_t] [--ii] [--jj] [--ll] [--mm] [--PP] [--pp] [--rr] [--ss] [--uu ddbbuusseerr = _d_b_u_s_e_r_n_a_m_e,_u_s_e_r_n_a_m_e] [_q_u_e_u_e_s] [_r_e_q_u_e_s_t_i_d_s | tt_i_d_s] IIMMPPLLEEMMEENNTTAATTIIOONN IRIX systems UNICOS/mk systems UNICOS systems AIX systems Digital UNIX systems HP-UX systems Solaris systems DDEESSCCRRIIPPTTIIOONN The ccqqssttaattll command requests status information from NQE. You may request job status or NQS queue status. The type of status information that you may request is determined by the command options. The NQE server of which you request status information is determined by the --dd _d_e_s_t__t_y_p_e option or the environment variable NNQQSS__SSEERRVVEERR. For more information about the NNQQSS__SSEERRVVEERR and the NNQQEE__DDEESSTT__TTYYPPEE environment variables, see the ENVIRONMENT VARIABLES section. By default, if you omit all options and arguments, a summary of each NQS queue on the NQS server is displayed. Options let you select the queue type, display content, and display format. You can limit the display content to a particular queue or request. By default, if you submit requests to the NQE database, you get a summary of active tasks only; completed or terminated tasks are not displayed. For an explanation of the various items in the displays, see the EXAMPLES section. The status display header indicates the type and/or location of your requests (see the EXAMPLES section). To display requests, the user executing the ccqqssttaattll command must have proper validation. For more information on user validation, see the NOTES section on the ccqqssuubb(1) man page. The ccqqssttaattll command supports the following options: OOppttiioonn DDeessccrriippttiioonn --aa Displays summary information about all of your requests. (Your system administrator may change the summary information to display requests of others in addition to your requests.) --bb Displays information about batch queues. This option does not apply if you are sending the ccqqssttaattll request to the NQE database. --dd _d_e_s_t__t_y_p_e Specifies the destination type for the request; _d_e_s_t__t_y_p_e can be either nnqqeeddbb or nnqqss. If _d_e_s_t__t_y_p_e is nnqqeeddbb, the request is sent to the NQE database. If _d_e_s_t__t_y_p_e is nnqqss, the request is sent to your NQS server, which is defined in the NNQQSS__SSEERRVVEERR environment variable or in the nnqqeeiinnffoo file. If you do not specify a destination type, the value of NNQQEE__DDEESSTT__TTYYPPEE is used; this value may exist in your environment or in the nnqqeeiinnffoo file. The command line option overrides an environment or nnqqeeiinnffoo file variable setting. The default value of _d_e_s_t__t_y_p_e is nnqqss. For more information about the NNQQSS__SSEERRVVEERR and the NNQQEE__DDEESSTT__TTYYPPEE environment variables, see the ENVIRONMENT VARIABLES section. --ff Displays full details about the specified queues or requests. Detailed queue information can be obtained only if the request is issued directly to the NNQQSS__SSEERRVVEERR (NNQQEE__DDEESSTT__TTYYPPEE=nnqqss). --hh _t_a_r_g_e_t__h_o_s_t Specifies the target NQS host from which display information will be obtained. This option does not apply if you are sending the ccqqssttaattll request to the NQE database. For sites that have enabled either the UNICOS MLS feature or the UNICOS/mk security enhancements, 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 access to NQS services. --ii Displays a summary of requests that are awaiting processing in batch and pipe queues. This option does not apply if you are sending the ccqqssttaattll request to the NQE database. --jj For a request sent to NQS, this option displays the contents of the request's job log file. For a request in the NQE database, this option displays a current history of events. For systems running the IRIX 6.2 release or later that use Array Services, this option displays the global array session handle (ASH) associated with a job. --ll Displays a summary of the resource limits defined for NQS queues. This option does not apply if you are sending the ccqqssttaattll request to the NQE database. --mm (Cray MPP systems only) Displays information about NQS queue limits on Cray MPP systems. This option does not apply if you are sending a ccqqssttaattll request to the NQE database. For CRAY T3E systems, this display shows the CPU time only for application processing elements (PEs). --PP Prompts you for a password. The NQS server may require a password. If this is true, the --PP option ensures that you are prompted. When you are prompted for a password, enter the password that is associated with the user name of the request. This password is not used by the NQE database server. --pp Displays information about pipe queues. This option does not apply if you are sending the ccqqssttaattll request to the NQE database. --rr Displays a summary of requests that are being processed in batch and pipe queues. This option does not apply if you are sending the ccqqssttaattll request to the NQE database. --ss Specifies a 40-column display (contains less information than the 80-column display). --uu _u_s_e_r_n_a_m_e --uu ddbbuusseerr=_d_b_u_s_e_r_n_a_m_e --uu ddbbuusseerr = _d_b_u_s_e_r_n_a_m_e,_u_s_e_r_n_a_m_e For status requests sent to the NQS server, the --uu _u_s_e_r_n_a_m_e argument is optional and restricts the requests displayed to those owned by _u_s_e_r_n_a_m_e. For status requests sent to the NQE database, _d_b_u_s_e_r_n_a_m_e is the name to be used to connect to the NQE database. The ddbbuusseerr argument is optional and defaults to the client user name if not specified. The ddbbuusseerr argument value also may be set in the NNQQEEDDBB__UUSSEERR environment variable. Although the summary status may display all requests, the detailed status display (--ff option) is restricted to status of requests in the NQE database that were submitted by the same database user (ddbbuusseerr). If you use the ddbbuusseerr=_d_b_u_s_e_r_n_a_m_e argument with the _u_s_e_r_n_a_m_e argument, no space is allowed between the comma and the _u_s_e_r_n_a_m_e argument. You cannot use --uu with options that display queue summaries. To issue the ccqqssttaattll 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 systems with the UNICOS MLS feature or the UNICOS/mk 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 This option does not apply if you are sending the ccqqssttaattll request to the NQE database. 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 NNQQSS__SSEERRVVEERR environment variable (if you omit the --hh option). [_r_e_q_u_e_s_t_i_d_s | tt_i_d_s] Displays information about the specified requests. _r_e_q_u_e_s_t_i_d is the request ID assigned by NQS to a request. _r_e_q_u_e_s_t_i_d has the following format: _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 argument is the original host of submission. If you omit it, NQS uses the server identified by the NNQQSS__SSEERRVVEERR environment variable. The _c_u_r_r__h_o_s_t argument 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 server identified by the NNQQSS__SSEERRVVEERR environment variable. The tt_i_d operand specifies a request belonging to the NQE database; tt identifies this as a user task, and _i_d is a unique number assigned to the request at the time it was inserted into the NQE database. QQuueeuuee SSttaattuuss The queue status does not apply for requests that were sent to the NQE database. 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: PPrrooppeerrttyy DDeessccrriippttiioonn EENNAABBLLEEDD Requests can be accepted into the queue. DDIISSAABBLLEEDD Requests cannot be accepted (although NQS is running at the NQS server). The operator has disabled the queue. LLOOAADDEEDD Requests temporarily cannot be accepted (although NQS is running at the NQS server). 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, this queue's status will return to EENNAABBLLEEDD. CCLLOOSSEEDD Requests cannot be accepted because NQS is not running at the NQS server. The second property indicates how the queue is currently executing requests. It can be one of the following: PPrrooppeerrttyy DDeessccrriippttiioonn 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 NQS server on which the queue resides. RReeqquueesstt SSttaattuuss The request status is shown after the word SSttaattuuss:: or SSttaattee:: 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 if the request was sent to NQS; or state and substate if the request was sent to the NQE database. The major status or state of a request can be one of the following: SSttaattuuss//SSttaattee DDeessccrriippttiioonn 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. NN NNQQEE DDaattaabbaassee. The request is in the NQE database. PP PPRREEEEMMPPTTEEDD. The request was preempted for SDS usage. When a request is preempted, a restart file is created. QQ QQUUEEUUEEDD. The request is in a queue and is eligible for routing or running. 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 by a date and/or time constraint imposed at the time of submission (by the ccqqssuubb --aa command), by the inaccessibility of a pipe queue destination, or because a license cannot be obtained. no entry <>. The status of the request is changing. You also can display this request status if the request was moved into the running subqueue but the associated session has not yet been created, if the NQS daemon aborted or hung while the request was running, or if the shepherd process is taking a long time to process the request exit. The minor status or substate of a request can be one of the following (your system administrator may define additional minor status definitions): SSttaattuuss//SSuubbssttaattee DDeessccrriippttiioonn _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. CCoommpp The request that was submitted to the NQE database has completed processing. 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. NNeeww The request is in the NQE database. nnuu The Network Load Balancer (NLB) server is unavailable. oopp The current major status of the request occurred through operator action. PPeenndd The request in the NQE database is awaiting scheduling (pending). 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. SScchhee The request is in the NQE database and has been scheduled by the NQE scheduler. sshh The system was shut down. SSuubbmm A copy of the request has been submitted from the NQE database for processing. ttdd (UNICOS systems only) The UNICOS tape daemon is unavailable, and the request asks for tape resources. TTeerrmm The copy of the request that was submitted from the NQE database for processing has terminated. TP 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 request submitted to the NQE database typically progresses through the following substates; the first four characters of a substate are displayed in the SSTT column of a database request summary (shown by using the ccqqssttaattll --aa command): SSuubbssttaattee DDeessccrriippttiioonn NNeeww The request is in the NQE database. PPeenndding The request is in the NQE database and is awaiting scheduling. SScchheeduled The request is in the NQE database and has been scheduled by the NQE scheduler. SSuubbmmitted A copy of the request has been submitted from the NQE database for processing. CCoommppleted The copy of the request submitted from the NQE database for processing has completed processing. TTeerrmminated The copy of the request that was submitted from the NQE database for processing has terminated. A batch request submitted from an interactive session to a pipe queue for routing to a batch queue typically progresses through the following states at a 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 (UNICOS systems only) Preempted by operator. cchheecckkppooiinntteedd (UNICOS, UNICOS/mk, and IRIX systems only) Saved for later processing at an NQS restart. ssuussppeennddeedd An operator or 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 NQS manager 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. If the UNICOS multilevel security (MLS) feature or the UNICOS/mk security enhancements are enabled on the NQS server and NQS is configured to enforce mandatory access controls (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 ccqqssttaattll --ff command. NQS managers and operators bypass the MAC checks. EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS The NNQQSS__SSEERRVVEERR environment variable specifies the NQS server with which you want to communicate. You must specify the TCP/IP name of the host running the NQS server; you can optionally specify a TCP/IP port number. You must precede the port number by a colon. The following is the C shell syntax: setenv NQS_SERVER _s_e_r_v_e_r The following is the standard and Korn shell syntax: NQS_SERVER=_s_e_r_v_e_r;; eexxppoorrtt NNQQSS__SSEERRVVEERR The NNQQSS__PPAASSSSWWOORRDD__NNEEEEDDEEDD environment variable, if defined, specifies that users are prompted for a password for all NQE client commands. This is an alternative to using the --PP option. The NNQQEE__DDEESSTT__TTYYPPEE environment variable, if defined, specifies the destination of your request, which can be the NQS server (nnqqss) or the NQE database (nnqqeeddbb). The following is the C shell syntax: setenv NQE_DEST_TYPE _v_a_l_u_e The NNQQEEDDBB__UUSSEERR environment variable, if defined, specifies the name to be used to connect to the NQE database. The following is the C shell syntax: setenv NQEDB_USER _d_b_u_s_e_r_n_a_m_e The MMSSQQLL__SSEERRVVEERR and MMSSQQLL__TTCC--PPOORRTT environment variables, if defined, specify an NQE database server and its port number instead of using the default (MSQL is the NQE database). The following is the C shell syntax: setenv MSQL_SERVER _s_e_r_v_e_r__n_a_m_e sseetteennvv MMSSQQLL__TTCCPP__PPOORRTT _p_o_r_t__n_u_m_b_e_r EEXXIITT SSTTAATTUUSS An exit status of 0 indicates success. A nonzero exit status indicates an 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 If you sent requests to the NQE database, entering the ccqqssttaattll command gives you a summary display of your requests in the NQE database (as described in the Request Summary Display subsection of this man page). For requests in NQS, the following command displays a summary of all NQS queues at the NQS server: ccqqssttaattll 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. The values can be (oonn) or (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 later in the EXAMPLES section. The last line of each display shows the global limit for each category (under the LLIIMM column) and the total number of requests in each category. 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: ccqqssttaattll --aa Each entry represents the current state of a request. Owners and users who have NQS manager or operator status can display their requests at the NQS server. Users who have the correct validation can display requests at a remote NQS server. CCoolluummnn DDeessccrriippttiioonn IIDDEENNTTIIFFIIEERR This is the NQS request identifier (_r_e_q_u_e_s_t_i_d) or the NQE database identifier (tt_i_d). If a request that was sent to the NQE database is in NQS, the IIDDEENNTTIIFFIIEERR will include a tt_i_d (_r_e_q_u_e_s_t_i_d) combination. NNAAMMEE The name of the request as specified by the user, using the ccqqssuubb --rr option (or the request file name if --rr was not used). SSYYSSTTEEMM--OOWWNNEERR (NQE database requests only) The NQE database component that currently owns the request. OOWWNNEERR (Pipe queue displays only) The user ID under which you were logged in when you submitted the request. Appears only on pipe queue displays. UUSSEERR The user name under which the request will be executed at the NQS system (either the name of the user who submitted the request or the name of the user specified by the ccqqssuubb --uu option, if that was used). LLOOCCAATTIIOONN//QQUUEEUUEE The current location of the request. The value may be either NNQQEE DDaattaabbaassee or the name of the NQS queue in which the request resides (for example, ssmmaallll@@ggrreeeenn11). JJIIDD The job identifier for an executing request in a batch queue; this entry is not included on a request summary of requests in the NQE database. PPRRTTYY Information in this field is valid only if the request is currently running under NQS. For a request awaiting execution, this specifies its intraqueue priority; for an executing request, this is its nice value. This entry is not included on a request summary of requests in the NQE database. The priority value is not available until after the NQS scheduler examines the queue (the priority field displays only dashes (---) while the queue is examined). 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; this entry indicates 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; it is not included on a request summary of requests in the NQE database. RREEQQTTIIMM The per-request CPU time limit for a request awaiting execution; this entry indicates the remaining CPU time (expressed in seconds) for an executing request or **** for a request with unlimited per-request CPU time; it is not included on a request summary of requests in the NQE database. SSTT Request state; see the Request Status subsection, which is part of the DESCRIPTION section. DDeettaaiilleedd RReeqquueesstt DDiissppllaayy The following command displays full details about a particular request: ccqqssttaattll --ff 99333344 Owners or users who have NQS manager or operator status can display their requests at the NQS server. 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; or for an NQE database request, name of the task identifier. SSttaattee:: For NQE database requests only. Current state of the request. For possible states, see the Request Status subsection of this man page. SSuubbssttaattee:: For NQE database requests only. Current substate of the request. For possible substates, see the Request Status subsection of this man page. SSyysstteemm OOwwnneerr:: For NQE database requests only. The NQE database component that currently owns the request. NNQQEE TTaasskk IIDD:: For NQE database requests only. The task identifier of the request in the NQE database; consists of the letter tt (specifying that it is a task) and a unique number assigned to the request at the time it was inserted into the NQE database. SSttaattee or SSttaattuuss:: Current status of the request. See the Request Status subsection of this man page. NNQQSS IIddeennttiiffiieerr:: The NQS request identifier that consists of the request's 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 ccqqssuubb --uu option, if that was used). For status of an NQE database request, this entry is displayed under the MMIISSCC field. GGrroouupp:: Principal group to which the owner of the request belongs. AAccccoouunntt//PPrroojjeecctt:: (For systems running UNICOS or IRIX 6.2 or later only) 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:: The NQS request 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 entered into the NQE database or created at the NQS server. QQuueeuueedd:: For a request sent to NQS, this is the time the request was queued, the time to retry the request if routing, or (if the ccqqssuubb --aa command was used) the time the request will be queued. RRuunn AAfftteerr:: For a request sent to the NQE database, this indicates the time after which the request will run. LLOOCCAATTIIOONN//QQUUEEUUEE For requests sent to NQS, this is the name of the queue in which the request currently resides and its interqueue priority. For requests sent to the NQE database, this is the task identifier (tt_i_d) of the request in the NQE database. 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 ccqqssuubb(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 ccqqssuubb(1) 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 File Transfer Agent (FTA), the FTA identifier is included in the file name. MMAAIILL Address to which NQS should send mail. 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. UUsseerr MMaasskk:: indicates the file creation mode mask. 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. 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 were exported from the submitter's environment; a value of aallll means that all variables were exported from the submitter's environment (see the --xx option of the ccqqssuubb(1) command.) SShheellll:: indicates the shell that is used to interpret the request. OOrriigg.. OOwwnneerr:: indicates the user ID under which the request was originally submitted. DDBB UUsseerr:: For NQE database requests only. The NQE database component that currently owns the request. JJoobb MMeessssaaggee:: For NQE database requests only. Log message stating the current state of the request. NNQQEE AATTTTRRIIBBUUTTEESS For NQE database requests only. List of attributes being used by the request; these strings are supplied through the --llaa option of the ccqqssuubb command. NNQQSS AATTTTRRIIBBUUTTEESS The request attributes; these strings are supplied through the --llaa option of the ccqqssuubb(1) command. The attributes determine which queues can accept the request. You should submit a request to a pipe queue when you use request attributes. For more information, see the BUGS section of the ccqqssuubb(1) man page. DDeettaaiilleedd QQuueeuuee DDiissppllaayy If you submitted a request to NQS, the following command displays full details about an NQS queue (this display does not apply to requests sent to the NQE database): ccqqssttaattll --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 NQS server 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 limit on the maximum number of concurrently executing requests for the entire queue, for one user, and for one user 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 can be requested by a 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 with 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 ccqqssuubb 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 For requests submitted to NQS, the following command displays the contents of the request's job log: ccqqssttaattll --jj 11223344 0011//2211 1133::0022::5599 RReeqquueesstt--iidd iiss <<11223344..aabbcc>>.. 0011//2211 1133::0033::0011 SSuubbmmiitttteedd ttoo qquueeuuee <> bbyy <>.. 0011//2211 1133::0033::0033 CCoommmmaanndd lliinnee ooppttiioonnss:: <>.. 0011//2211 1133::0033::0033 SSccrriipptt ffiillee ooppttiioonnss:: <<--ss //bbiinn//ccsshh>>.. 0011//2211 1133::0033::0099 RRuunnnniinngg iinn qquueeuuee <>.. 0011//2211 1133::0033::1155 FFiinniisshheedd.. 0011//2211 1133::0033::1155 RReettuurrnniinngg ssttddeerrrr oouuttppuutt ffiillee.. 0011//2211 1133::0033::1188 RReettuurrnniinngg ssttddoouutt oouuttppuutt ffiillee.. 0011//2211 1133::0033::1199 GGlloobbaall aarrrraayy sseessssiioonn hhaannddllee iiss <<33991177000055777766773377225500558899>>.. For requests submitted to the NQE database, the following command displays the contents of the request's job log: Event History for NQE Task: t4 10/25/95 10:41:24 t4 NEW_STATE state=Pending (ack=1) 10/25/95 12:01:31 t4 SIGDEL Acknoledged (ack=1) 10/25/95 12:01:31 t4 NEW_STATE state=Terminated owner=monitor.main (ack=1) SSEEEE AALLSSOO ccqqddeell(1), ccqqssuubb(1), nnqqee(1) for information about batch requests submitted from an NQE client qqddeell(1), qqssttaatt(1), qqssuubb(1) for information about batch requests submitted locally qqlliimmiitt(1) for information about queue limits enforced on your NQS server 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, for NQE and NQS user information This man page is available only online.