3.2.2 - Set Request Information
Action Option -SR (-SetRequest) :
creates or modifies request information in GDEXDB for the given dataset number and groups. One or more records can be processed per call.
Although a specialist can add a new request record, this is rarely needed. Request records are normally generated by the web interface that accepts data request submissions. This action is more commonly used to modify requests, for example to change request status from Wait to Queue, or to change the purge date/time so that a request is purged sooner or later.
Available mode options:
gets usage information for the given requests and records it for order metrics |
|
writes information to GDEXDB regardless of whether the specialist running dsrqst owns the dataset |
|
adds a new request record to GDEXDB for the given dataset, group index, and request type |
If a request record for the given request index or request name already exists in GDEXDB, it is modified; otherwise, a new request record is added when the request index is 0 and Mode option -NR (-NewRequest) is present.
The request name is generated automatically as the user’s uppercased last name combined with the request index. It cannot be reset.
The default request processing priority is 10, and can be set between 1 and 10, where 1 is the highest priority. A specialist can promote a request to be processed sooner by raising its priority via option -PO (-Priority) when many requests are queued for processing.
EXAMPLE 4. Set the request status to ‘Q’ (Queued) for request index 42:
A customized request can be created to stage existing data prepared for a specific user.
EXAMPLE 5. When pre-processed data are ready in a directory, create a new customized request as:
then change to the directory containing the data files and build the request by running: