1QSTAT(1) Grid Engine User Commands QSTAT(1)
2
6 qstat - show the status of Grid Engine jobs and queues
7
9 qstat [ -ext ] [ -cb ] [ -f ] [ -F [resource_name,...] ] [ -g
10 {c|d|t}[+] ] [ -help ] [ -j [job_list] ] [ -l resource=val,... ] [ -ne
11 ] [ -pe pe_name,... ] [ -pri ] [ -q wc_queue_list ] [ -qs
12 {a|c|d|o|s|u|A|C|D|E|S} ] [ -r ] [ -s
13 {r|p|s|z|hu|ho|hs|hd|hj|ha|h|a}[+] ] [ -t ] [ -U user,... ] [ -u
14 user,... ] [ -urg ] [ -xml ]
15
17 qstat shows the current status of the available Grid Engine queues and
18 the jobs associated with the queues. Selection options allow you to get
19 information about specific jobs, queues or users. If multiple selec‐
20 tions are done a queue is only displayed if all selection criteria for
21 a queue instance are met. Without any option qstat will display only a
22 list of jobs with no queue status information.
23 The administrator and the user may define files (see sge_qstat(5)),
25 which can contain any of the options described below. A cluster-wide
26 sge_qstat file may be placed under $GE_ROOT/$GE_CELL/common/sge_qstat
27 The user private file is searched at the location $HOME/.sge_qstat.
28 The home directory request file has the highest precedence over the
29 cluster global file. Command line can be used to override the flags
30 contained in the files.
31
33 -cb In combination with -cb the output of this command will addi‐
34 tionally contain the information of a requested binding and the
35 changes that have been applied to the topology string (real
36 binding) for the host where this job is running. This additional
37 information will appear in combination with the parameters -r
38 and -j.
39 Please note that this command line switch will be removed with
41 the next major release.
42 -explain a|A|c|E
44 ´c' displays the reason for the c(onfiguration ambiguous) state
45 of a queue instance. 'a' shows the reason for the alarm state.
46 Suspend alarm state reasons will be displayed by 'A'. 'E' dis‐
47 plays the reason for a queue instance error state.
48 The output format for the alarm reasons is one line per reason
50 containing the resource value and threshold. For details about
51 the resource value please refer to the description of the Full
52 Format in section OUTPUT FORMATS below.
53 -ext Displays additional information for each job related to the job
55 ticket policy scheme (see OUTPUT FORMATS below).
56 -f Specifies a "full" format display of information. The -f option
58 causes summary information on all queues to be displayed along
59 with the queued job list.
60 -F [ resource_name,... ]
62 Like in the case of -f information is displayed on all jobs as
63 well as queues. In addition, qstat will present a detailed list‐
64 ing of the current resource availability per queue with respect
65 to all resources (if the option argument is omitted) or with
66 respect to those resources contained in the resource_name list.
67 Please refer to the description of the Full Format in section
68 OUTPUT FORMATS below for further detail.
69 -g {c|d|t}[+]
71 The -g option allows for controlling grouping of displayed
72 objects.
73 With -g c a cluster queue summary is displayed. Find more
75 information in the section OUTPUT FORMATS.
76 With -g d array jobs are displayed verbosely in a one line per
78 job task fashion. By default, array jobs are grouped and all
79 tasks with the same status (for pending tasks only) are dis‐
80 played in a single line. The array job task id range field in
81 the output (see section OUTPUT FORMATS) specifies the corre‐
82 sponding set of tasks.
83 With -g t parallel jobs are displayed verbosely in a one line
85 per parallel job task fashion. By default, parallel job tasks
86 are displayed in a single line. Also with -g t option the func‐
87 tion of each parallel task is displayed rather than the jobs
88 slot amount (see section OUTPUT FORMATS).
89 -help Prints a listing of all options.
92 -j [job_list]
94 Prints either for all pending jobs or the jobs contained in
95 job_list various information. The job_list can contain job_ids,
96 job_names, or wildcard expression sge_types(1).
97 For jobs in E(rror) state the error reason is displayed. For
99 jobs that could not be dispatched during in the last scheduling
100 interval the obstacles are shown, if 'schedd_job_info' in
101 sched_conf(5) is configured accordingly.
102 For running jobs available information on resource utilization
104 is shown about consumed cpu time in seconds, integral memory
105 usage in Gbytes seconds, amount of data transferred in io opera‐
106 tions, current virtual memory utilization in Mbytes, and maximum
107 virtual memory utilization in Mbytes. This information is not
108 available if resource utilization retrieval is not supported for
109 the OS platform where the job is hosted.
110 In combination with -cp the output of this command will addi‐
112 tionally contain the information of a requested binding (see
113 -binding of qsub(1)) and the changes that have been applied to
114 the topology string (real binding) for the host where this job
115 is running.
116 The topology string will contain capital letters for all those
118 cores that were not bound to the displayed job. Bound cores will
119 be shown lowercase (E.g "SCCcCSCCcC" means that core 2 on the
120 two available sockets where bound to this job).
121 Please refer to the file <ge_root>/doc/load_parameters.asc for
123 detailed information on the standard set of load values.
124 -l resource[=value],...
126 Defines the resources required by the jobs or granted by the
127 queues on which information is requested. Matching is performed
128 on queues based on non-mutable resource availability information
129 only. That means load values are always ignored except the so-
130 called static load values (i.e. "arch", "num_proc", "mem_total",
131 "swap_total" and "virtual_total"). Consumable utilization is
132 also ignored. The pending jobs are restricted to jobs that
133 might run in one of the above queues. In a similar fashion also
134 the queue-job matching bases only on non-mutable resource avail‐
135 ability information. If there are multiple -l resource requests
136 they will be concatenated by a logical AND: a queue needs to
137 match all resources to be displayed.
138 -ne In combination with -f the option suppresses the display of
140 empty queues. This means all queues where actually no jobs are
141 running are not displayed.
142 -pe pe_name,...
144 Displays status information with respect to queues which are
145 attached to at least one of the parallel environments enlisted
146 in the comma separated option argument. Status information for
147 jobs is displayed either for those which execute in one of the
148 selected queues or which are pending and might get scheduled to
149 those queues in principle.
150 -pri Displays additional information for each job related to the job
153 priorities in general. (see OUTPUT FORMATS below).
154 -q wc_queue_list
156 Specifies a wildcard expression queue list to which job informa‐
157 tion is to be displayed. Find the definition of wc_queue_list in
158 sge_types(1).
159 -qs {a|c|d|o|s|u|A|C|D|E|S}
161 Allows for the filtering of queue instances according to state.
162 -r Prints extended information about the resource requirements of
164 the displayed jobs.
165 In combination with -cb the output of this command will contain
167 additional information concerning the requested binding for a
168 job. (see -binding of qsub(1)).
169 Please refer to the OUTPUT FORMATS sub-section Expanded Format
171 below for detailed information.
172 -s {p|r|s|z|hu|ho|hs|hd|hj|ha|h|a}[+]
174 Prints only jobs in the specified state, any combination of
176 states is possible. -s prs corresponds to the regular qstat out‐
177 put without -s at all. To show recently finished jobs, use -s z.
178 To display jobs in user/operator/system/array-dependency hold,
179 use the -s hu/ho/hs/hd option. The -s ha option shows jobs which
180 where submitted with the qsub -a command. qstat -s hj displays
181 all jobs which are not eligible for execution unless the job has
182 entries in the job dependency list. qstat -s h is an abbrevia‐
183 tion for qstat -s huhohshdhjha and qstat -s a is an abbreviation
184 for qstat -s psr (see -a, -hold_jid and -hold_jid_ad options to
185 qsub(1)).
186 -t Prints extended information about the controlled sub-tasks of
188 the displayed parallel jobs. Please refer to the OUTPUT FORMATS
189 sub-section Reduced Format below for detailed information. Sub-
190 tasks of parallel jobs should not be confused with array job
191 tasks (see -g option above and -t option to qsub(1)).
192 -U user,...
194 Displays status information with respect to queues to which the
195 specified users have access. Status information for jobs is dis‐
196 played either for those which execute in one of the selected
197 queues or which are pending and might get scheduled to those
198 queues in principle.
199 -u user,...
201 Display information only on those jobs and queues being associ‐
202 ated with the users from the given user list. Queue status
203 information is displayed if the -f or -F options are specified
204 additionally and if the user runs jobs in those queues.
205 The string $user is a placeholder for the current username. An
207 asterisk "*" can be used as username wildcard to request any
208 users' jobs be displayed. The default value for this switch is
209 -u $user.
210 -urg Displays additional information for each job related to the job
213 urgency policy scheme (see OUTPUT FORMATS below).
214 -xml This option can be used with all other options and changes the
216 output to XML. The used schemas are referenced in the XML out‐
217 put. The output is printed to stdout. For more detailed infor‐
218 mation, the schemas for the qstat command can be found in
219 $SGE_ROOT/util/resources/schemas/qstat.
220 If the -xml parameter is combined with -cb then the XML output
222 will contain additional tags containing information about job to
223 core binding. You can also find schema files with the suffix
224 "_cb" in the directory $SGE_ROOT/util/resources/schemas/qstat
225 that describe that changes.
226
228 Depending on the presence or absence of the -explain, -f, -F, or -qs
229 and -r and -t option three output formats need to be differentiated.
230 The -ext and -urg options may be used to display additional information
232 for each job.
233 Cluster Queue Format (with -g c)
235 Following the header line a section for each cluster queue is provided.
236 When queue instances selection are applied (-l -pe, -q, -U) the cluster
237 format contains only cluster queues of the corresponding queue
238 instances.
239 · the cluster queue name.
241 · an average of the normalized load average of all queue hosts. In
243 order to reflect each hosts different significance the number of
244 configured slots is used as a weighting factor when determining
245 cluster queue load. Please note that only hosts with a
246 np_load_value are considered for this value. When queue selection is
247 applied only data about selected queues is considered in this for‐
248 mula. If the load value is not available at any of the hosts '-NA-'
249 is printed instead of the value from the complex attribute defini‐
250 tion.
251 · the number of currently used slots.
253 · the number of slots reserved in advance.
255 · the number of currently available slots.
257 · the total number of slots.
259 · the number of slots which is in at least one of the states 'aoACDS'
261 and in none of the states 'cdsuE'
262 · the number of slots which are in one of these states or in any com‐
264 bination of them: 'cdsuE'
265 · the -g c option can be used in combination with -ext. In this case,
267 additional columns are added to the output. Each column contains the
268 slot count for one of the available queue states.
269 Reduced Format (without -f, -F, and -qs)
271 Following the header line a line is printed for each job consisting of
272 · the job ID.
274 · the priority of the job determining its position in the pending jobs
276 list. The priority value is determined dynamically based on ticket
277 and urgency policy set-up (see also sge_priority(5) ).
278 · the name of the job.
280 · the user name of the job owner.
282 · the status of the job - one of d(eletion), E(rror), h(old),
284 r(unning), R(estarted), s(uspended), S(uspended), t(ransfering),
285 T(hreshold) or w(aiting).
286 The state d(eletion) indicates that a qdel(1) has been used to ini‐
288 tiate job deletion. The states t(ransfering) and r(unning) indicate
289 that a job is about to be executed or is already executing, whereas
290 the states s(uspended), S(uspended) and T(hreshold) show that an
291 already running jobs has been suspended. The s(uspended) state is
292 caused by suspending the job via the qmod(1) command, the
293 S(uspended) state indicates that the queue containing the job is
294 suspended and therefore the job is also suspended and the T(hresh‐
295 old) state shows that at least one suspend threshold of the corre‐
296 sponding queue was exceeded (see queue_conf(5)) and that the job has
297 been suspended as a consequence. The state R(estarted) indicates
298 that the job was restarted. This can be caused by a job migration or
299 because of one of the reasons described in the -r section of the
300 qsub(1) command.
301 The states w(aiting) and h(old) only appear for pending jobs. The
303 h(old) state indicates that a job currently is not eligible for exe‐
304 cution due to a hold state assigned to it via qhold(1), qalter(1) or
305 the qsub(1) -h option or that the job is waiting for completion of
306 the jobs to which job dependencies have been assigned to the job via
307 the -hold_jid or -hold_jid-ad options of qsub(1) or qalter(1).
308 The state E(rror) appears for pending jobs that couldn't be started
310 due to job properties. The reason for the job error is shown by the
311 qstat(1) -j job_list option.
312 · the submission or start time and date of the job.
314 · the queue the job is assigned to (for running or suspended jobs
316 only).
317 · the number of job slots or the function of parallel job tasks if -g
319 t is specified.
320 Without -g t option the total number of slots occupied resp.
322 requested by the job is displayed. For pending parallel jobs with a
323 PE slot range request, the assumed future slot allocation is dis‐
324 played. With -g t option the function of the running jobs (MASTER
325 or SLAVE - the latter for parallel jobs only) is displayed.
326 · the array job task id. Will be empty for non-array jobs. See the -t
328 option to qsub(1) and the -g above for additional information.
329 If the -t option is supplied, each status line always contains parallel
331 job task information as if -g t were specified and each line contains
332 the following parallel job subtask information:
333 · the parallel task ID (do not confuse parallel tasks with array job
335 tasks),
336 · the status of the parallel task - one of r(unning), R(estarted),
338 s(uspended), S(uspended), T(hreshold), w(aiting), h(old), or
339 x(exited).
340 · the cpu, memory, and I/O usage,
342 · the exit status of the parallel task,
344 · and the failure code and message for the parallel task.
346 Full Format (with -f and -F)
348 Following the header line a section for each queue separated by a hori‐
349 zontal line is provided. For each queue the information printed con‐
350 sists of
351 · the queue name,
353 · the queue type - one of B(atch), I(nteractive), C(heckpointing),
355 P(arallel), T(ransfer) or combinations thereof or N(one),
356 · the number of used and available job slots,
358 · the load average of the queue host,
360 · the architecture of the queue host and
362 · the state of the queue - one of u(nknown) if the corresponding
364 ge_execd(8) cannot be contacted, a(larm), A(larm), C(alendar sus‐
365 pended), s(uspended), S(ubordinate), d(isabled), D(isabled), E(rror)
366 or combinations thereof.
367 If the state is a(larm) at least on of the load thresholds defined in
369 the load_thresholds list of the queue configuration (see queue_conf(5))
370 is currently exceeded, which prevents from scheduling further jobs to
371 that queue.
372 As opposed to this, the state A(larm) indicates that at least one of
374 the suspend thresholds of the queue (see queue_conf(5)) is currently
375 exceeded. This will result in jobs running in that queue being succes‐
376 sively suspended until no threshold is violated.
377 The states s(uspended) and d(isabled) can be assigned to queues and
379 released via the qmod(1) command. Suspending a queue will cause all
380 jobs executing in that queue to be suspended.
381 The states D(isabled) and C(alendar suspended) indicate that the queue
383 has been disabled or suspended automatically via the calendar facility
384 of Grid Engine (see calendar_conf(5)), while the S(ubordinate) state
385 indicates, that the queue has been suspend via subordination to another
386 queue (see queue_conf(5) for details). When suspending a queue (regard‐
387 less of the cause) all jobs executing in that queue are suspended too.
388 If an E(rror) state is displayed for a queue, ge_execd(8) on that host
390 was unable to locate the ge_shepherd(8) executable on that host in
391 order to start a job. Please check the error logfile of that
392 ge_execd(8) for leads on how to resolve the problem. Please enable the
393 queue afterwards via the -c option of the qmod(1) command manually.
394 If the c(onfiguration ambiguous) state is displayed for a queue
396 instance this indicates that the configuration specified for this queue
397 instance in sge_conf(5) is ambiguous. This state is cleared when the
398 configuration becomes unambiguous again. This state prevents further
399 jobs from being scheduled to that queue instance. Detailed reasons why
400 a queue instance entered the c(onfiguration ambiguous) state can be
401 found in the sge_qmaster(8) messages file and are shown by the qstat
402 -explain switch. For queue instances in this state the cluster queue's
403 default settings are used for the ambiguous attribute.
404 If an o(rphaned) state is displayed for a queue instance, it indicates
406 that the queue instance is no longer demanded by the current cluster
407 queue's configuration or the host group configuration. The queue
408 instance is kept because jobs which not yet finished jobs are still
409 associated with it, and it will vanish from qstat output when these
410 jobs have finished. To quicken vanishing of an orphaned queue instance
411 associated job(s) can be deleted using qdel(1). A queue instance in
412 (o)rphaned state can be revived by changing the cluster queue configu‐
413 ration accordingly to cover that queue instance. This state prevents
414 from scheduling further jobs to that queue instance.
415 If the -F option was used, resource availability information is printed
417 following the queue status line. For each resource (as selected in an
418 option argument to -F or for all resources if the option argument was
419 omitted) a single line is displayed with the following format:
420 · a one letter specifier indicating whether the current resource
422 availability value was dominated by either
423 `g' - a cluster global,
424 `h' - a host total or
425 `q' - a queue related resource consumption.
426 · a second one letter specifier indicating the source for the current
428 resource availability value, being one of
429 `l' - a load value reported for the resource,
430 `L' - a load value for the resource after administrator defined load
431 scaling has been applied,
432 `c' - availability derived from the consumable resources facility
433 (see complexes(5)),
434 `f' - a fixed availability definition derived from a non-consumable
435 complex attribute or a fixed resource limit.
436 · after a colon the name of the resource on which information is dis‐
438 played.
439 · after an equal sign the current resource availability value.
441 The displayed availability values and the sources from which they
443 derive are always the minimum values of all possible combinations.
444 Hence, for example, a line of the form "qf:h_vmem=4G" indicates that a
445 queue currently has a maximum availability in virtual memory of 4 Giga‐
446 byte, where this value is a fixed value (e.g. a resource limit in the
447 queue configuration) and it is queue dominated, i.e. the host in total
448 may have more virtual memory available than this, but the queue doesn't
449 allow for more. Contrarily a line "hl:h_vmem=4G" would also indicate an
450 upper bound of 4 Gigabyte virtual memory availability, but the limit
451 would be derived from a load value currently reported for the host. So
452 while the queue might allow for jobs with higher virtual memory
453 requirements, the host on which this particular queue resides currently
454 only has 4 Gigabyte available.
455 If the -explain option was used with the character 'a' or 'A', informa‐
457 tion about resources is displayed, that violate load or suspend thresh‐
458 olds.
459 The same format as with the -F option is used with following exten‐
460 sions:
461 · the line starts with the keyword `alarm'
463 · appended to the resource value is the type and value of the appro‐
465 priate threshold
466 After the queue status line (in case of -f) or the resource availabil‐
468 ity information (in case of -F) a single line is printed for each job
469 running currently in this queue. Each job status line contains
470 · the job ID,
472 · the priority of the job determining its position in the pending jobs
474 list. The priority value is determined dynamically based on ticket
475 and urgency policy set-up (see also sge_priority(5) ).
476 · the job name,
478 · the job owner name,
480 · the status of the job - one of t(ransfering), r(unning),
482 R(estarted), s(uspended), S(uspended) or T(hreshold) (see the
483 Reduced Format section for detailed information),
484 · the submission or start time and date of the job.
486 · the number of job slots or the function of parallel job tasks if -g
488 t is specified.
489 Without -g t option the number of slots occupied per queue resp.
491 requested by the job is displayed. For pending parallel jobs with a
492 PE slot range request, the assumed future slot allocation is dis‐
493 played. With -g t option the function of the running jobs (MASTER
494 or SLAVE - the latter for parallel jobs only) is displayed.
495 If the -t option is supplied, each job status line also contains
497 · the task ID,
499 · the status of the task - one of r(unning), R(estarted), s(uspended),
501 S(uspended), T(hreshold), w(aiting), h(old), or x(exited) (see the
502 Reduced Format section for detailed information),
503 · the cpu, memory, and I/O usage,
505 · the exit status of the task,
507 · and the failure code and message for the task.
509 Following the list of queue sections a PENDING JOBS list may be printed
511 in case jobs are waiting for being assigned to a queue. A status line
512 for each waiting job is displayed being similar to the one for the run‐
513 ning jobs. The differences are that the status for the jobs is w(ait‐
514 ing) or h(old), that the submit time and date is shown instead of the
515 start time and that no function is displayed for the jobs.
516 In very rare cases, e.g. if ge_qmaster(8) starts up from an inconsis‐
518 tent state in the job or queue spool files or if the clean queue (-cq)
519 option of qconf(1) is used, qstat cannot assign jobs to either the run‐
520 ning or pending jobs section of the output. In this case as job status
521 inconsistency (e.g. a job has a running status but is not assigned to a
522 queue) has been detected. Such jobs are printed in an ERROR JOBS sec‐
523 tion at the very end of the output. The ERROR JOBS section should dis‐
524 appear upon restart of ge_qmaster(8). Please contact your Grid Engine
525 support representative if you feel uncertain about the cause or effects
526 of such jobs.
527 Expanded Format (with -r)
529 If the -r option was specified together with qstat, the following
530 information for each displayed job is printed (a single line for each
531 of the following job characteristics):
532 · The job and master queue name.
534 · The hard and soft resource requirements of the job as specified with
536 the qsub(1) -l option. The per resource addend when determining the
537 jobs urgency contribution value is printed (see also sge_prior‐
538 ity(5)).
539 · The requested parallel environment including the desired queue slot
541 range (see -pe option of qsub(1)).
542 · The requested checkpointing environment of the job (see the qsub(1)
544 -ckpt option).
545 · In case of running jobs, the granted parallel environment with the
547 granted number of queue slots.
548 · If -cb was specified the requested job binding parameters.
550 Enhanced Output (with -ext)
552 For each job the following additional items are displayed:
553 ntckts The total number of tickets in normalized fashion.
555 project
557 The project to which the job is assigned as specified in the
558 qsub(1) -P option.
559 department
561 The department, to which the user belongs (use the -sul and -su
562 options of qconf(1) to display the current department defini‐
563 tions).
564 cpu The current accumulated CPU usage of the job in seconds.
566 mem The current accumulated memory usage of the job in Gbytes sec‐
568 onds.
569 io The current accumulated IO usage of the job.
571 tckts The total number of tickets assigned to the job currently
573 ovrts The override tickets as assigned by the -ot option of qalter(1).
575 otckt The override portion of the total number of tickets assigned to
577 the job currently
578 ftckt The functional portion of the total number of tickets assigned
580 to the job currently
581 stckt The share portion of the total number of tickets assigned to the
583 job currently
584 share The share of the total system to which the job is entitled cur‐
586 rently.
587 Enhanced Output (with -urg)
589 For each job the following additional urgency policy related items are
590 displayed (see also sge_priority(5)):
591 nurg The jobs total urgency value in normalized fashion.
593 urg The jobs total urgency value.
595 rrcontr
597 The urgency value contribution that reflects the urgency that is
598 related to the jobs overall resource requirement.
599 wtcontr
601 The urgency value contribution that reflects the urgency related
602 to the jobs waiting time.
603 dlcontr
605 The urgency value contribution that reflects the urgency related
606 to the jobs deadline initiation time.
607 deadline
609 The deadline initiation time of the job as specified with the
610 qsub(1) -dl option.
611 Enhanced Output (with -pri)
613 For each job, the following additional job priority related items are
614 displayed (see also sge_priority(5)):
615 nurg The job's total urgency value in normalized fashion.
617 npprior
619 The job's -p priority in normalized fashion.
620 ntckts The job's ticket amount in normalized fashion.
622 ppri The job's -p priority as specified by the user.
624
626 GE_ROOT Specifies the location of the Grid Engine standard con‐
627 figuration files.
628 GE_CELL If set, specifies the default Grid Engine cell. To
630 address a Grid Engine cell qstat uses (in the order of
631 precedence):
632 The name of the cell specified in the environment
634 variable GE_CELL, if it is set.
635 The name of the default cell, i.e. default.
637 GE_DEBUG_LEVEL If set, specifies that debug information should be writ‐
640 ten to stderr. In addition the level of detail in which
641 debug information is generated is defined.
642 GE_QMASTER_PORT
644 If set, specifies the tcp port on which ge_qmaster(8) is
645 expected to listen for communication requests. Most
646 installations will use a services map entry for the ser‐
647 vice "sge_qmaster" instead to define that port.
648 SGE_LONG_QNAMES
650 Qstat does display queue names up to 30 characters. If
651 that is to much or not enough, one can set a custom
652 length with this variable. The minimum display length is
653 10 characters. If one does not know the best display
654 length, one can set SGE_LONG_QNAMES to -1 and qstat will
655 figure out the best length.
656
658 <ge_root>/<cell>/common/act_qmaster
659 Grid Engine master host file
660 <ge_root>/<cell>/common/ge_qstat
661 cluster qstat default options
662 $HOME/.ge_qstat
663 user qstat default options
664
666 ge_intro(1), qalter(1), qconf(1), qhold(1), qhost(1), qmod(1), qsub(1),
667 queue_conf(5), ge_execd(8), ge_qmaster(8), ge_shepherd(8).
668
670 See ge_intro(1) for a full statement of rights and permissions.
671GE 6.2u5 $Date: 2009/11/05 13:18:36 $ QSTAT(1)