The term FDDRL request was introduced with FDDRL V19.0A.
FDDRL requests are created by executing the FDDRL statements for the FDDRL functions (COPY, DUMP, RELOAD).
One request is created per statement and object name (pubset, disk or disk set). A request can have three statuses: accepted, started or completed. Intermediate statuses are not managed.
A request is defined by the following parameters:
REQUEST-NAME | A request name comprises the '3-character alias name (ALIAS-NAME) of the statement and the object name, |
REQUEST-DATE | Date and time the request was accepted (entry of the START-JOBS statement) |
| STATUS | ACCEPTED, STARTED, COMPLETED |
| SUB-STATUS | This is only defined for the COMPLETED status: OK or WITH-ERRORS |
REPORT-FILE | Name of the report file (for the COMPLETED status only). |
| TSN | TSN of the main task; used internally to check aborted runs. |
| TERM-DATE/ TERM-TIME | Termination time (end of an FDDRL request) The duration of a request can be determined from the difference between the termination time and the start time. |
You can display running and completed FDDRL requests using the
//SHOW-REQUESTS statement. Here you can filter the requests which are to be displayed according to attributes and also define the required output medium (SYSOUT, SYSLST and/or S variable).
When FDDRL is running on a Server Unit of an SE server, the requests and your status changes are reported to the SE Manager.
When an FDDRL request ends, a report file is created by default (REPORT-FILE=*STD). When it is running on a Server Unit of an SE server, by default (MONITORING=*STD) a report file in PDF format is also created which can be displayed in the SE Manager.
Request file
The FDDRL requests are stored in a system-wide request file with the name SYSDAT.FDDRL.210.REQUESTS. If the file does not yet exist when a request is created, it is created automatically. The request file is specific to the FDDRL version. When you change the FDDRL version, it is not envisaged that the requests from other FDDRL versions should be taken over.
By default, in each FDDRL run all FDDRL requests which are older than 40 days are deleted from the request file. When required, you can adjust this age limit using the KEEP-REQUESTS parameter in the FDDRL parameter file.
However, the
//DELETE-REQUESTS statement also enables you to delete completed requests manually from the request file.