3.3 - Request Process Actions
Request processes can be started by the centralized daemon dscheck or manually by a DECS specialist who supplies request indices when running Action -BR (-BuildRequest). A request can only be processed manually by the specialist who controls it.
Data files for a processed request are staged on the GDEX Server temporarily for online download or for access from NCAR internal computers. A DECS specialist can also purge a request manually at its due time by supplying the request index to dsrqst with Action -PR (-PurgeRequest).
Requests are processed and purged through the actions in this section:
run dsrqst to process one or more queued requests |
|
Process Partitions |
run dsrqst to process one or more queued partitions |
run dsrqst to purge one or more due requests |
|
change the purge time of online requests so they are purged later or sooner |
|
clean one or more requests by deleting the files that have been built and the file records created in GDEXDB |
|
unlock one or more request records so they can be rebuilt on a different host |
|
interrupt queued requests by setting their status to ‘I’ and killing all running processes that are building them |
|
Unlock Partitions |
unlock one or more partition records so they can be reprocessed on a different host |
interrupt queued partitions by setting their status to ‘I’ and killing all running partition processes |
|
restore an already-purged request by re-creating the request and its file information from the saved purge records |
Table of Contents