dcsq — Display the current DCS queue(s) contents.
dcsq [-project proj] [-all] [-cols n] [-host] [-owner str] [-qtype type] [-qver version]
The DCS Server manages several queues, segregated by the request type (metadata, file transfer, etc). The dcsq command prints a report about the current state of the specified queue or queues. By default, dcsq limits its display to only your jobs.
proj
Supply proj as the project number for
charging. Currently, no charging is done for DCS operations, so
this option is a placeholder for when charging might be imposed.
Display all jobs for all users that are currently active or queued.
n
Supply n as the number of
columns to limit each output line. The default is 132,
and the maximum is 256.
Include the DCS Client host name for each job.
str
Supply str to limit
the search based on the job's owner. The
str value can either
be the UCAS account name or the scientist number.
The default is to limit the search to requests
you have submitted.
type
Supply type to limit the search
based on the DCS queue type. The default is all queue types.
Values for type can be
FT for file transfer requests,
MD for metadata requests, or
QC for queue control requests.
version
Supply version to limit
the search based on the DCS queue version.
The default is queue version 1. Any other queue
versions are typically used for testing. All
queue versions may be selected with the value
all.
The output for each queue type is preceeded by a heading line describing for which queue the following output describes, and the column header titles.
Table 6. Dcsq output description.
| Column Name | Description |
|---|---|
| JID | DCS job id (request id) |
| S | The request status. A blank indicates a queued request, 'A' an active request and an 'H' a (administratively) held request. |
| Enq/Start Time | For active requests, the time that request processing started. For queued or held requests, the time the DCS server received the request from the DCS client program. Note that this may be different from when the DCS client was actually started if the client has to retry the submission process for any reason. All times are MST/MDT. |
| User | The user's name. |
| Host | (Optional) The host on which the DCS client is running. |
| Command | The command name. The request's owner and select CISL personnel will also see the first few command arguments. Read and write passwords are replaced with a hash '#' character. |
Example 3. Display your active or queued jobs.
dcsqTypical output:
Queue Type: FT Version: 1 JID S Pri Enq/Start Time User Command ------ - --- -------------- -------- ------- Queue Type: MD Version: 1 JID S Pri Enq/Start Time User Command ------ - --- -------------- -------- ------- 1157 1 07/13 09:10:01 JDOE msls -l /some/path Queue Type: QC Version: 1 JID S Pri Enq/Start Time User Command ------ - --- -------------- -------- ------- 1158 A 1 07/13 09:10:02 JDOE dcsq
See Environment Variables section of the Command Behavior and Envrionment chapter for details.
See Exit Status Codes section of the Command Behavior and Environment chapter for details.