This statement defines the execution parameters for an FDDRL run.
After /START-FDDRL all parameters are either initialized with their default value (see section "FDDRL parameter" in chapter Installation of FDDRL) or with the values in the FDDRL parameter file adjusted on a system-specific basis, if these exist. A value other than *UNCHANGED changes parameter values. The new parameters remain valid until they are changed again. The parameter values are passed on to the entered FDDRL jobs when the job is created (see chapter "CREATE-JOBS Create FDDRL jobs").
The SHOW-FDDRL-PARAMETERS statement enables you to query the values currently set.
MODIFY-FDDRL-PARAMETERS | Alias: MFP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PROCESS-JOBS = *UNCHANGED / *BY-MAINTASK / *BY-SUBTASKS(...)
The task for the FDDRL jobs is defined. Default: *BY-SUBTASKS
PROCESS-JOBS = *BY-MAINTASK
The FDDRL jobs are executed one after the other under the calling task (FDDRL main task).
PROCESS-JOBS = *BY-SUBTASKS(...)
Each FDDRL job is processed under a separate FDDRL subtask. The FDDRL subtasks are executed in the same job class as the FDDRL main task. If this job class does not permit batch jobs, the default batch job class of the user ID is used.
The degree of parallelism is determined by the TASK-LIMIT operand, taking due account of the job class limit.
TASK-LIMIT = *UNCHANGED / *STD / <integer 1..16>
Defines the number of FDDRL subtasks that can be active at the same time. Limiting the number of tasks can be useful in order to avoid too great a reduction in system performance or to occupy only as many tape devices as are available to FDDRL.
TASK-LIMIT = *STD
The default value (4 FDDRL subtasks) is set.
TASK-LIMIT = <integer 1..16>
Maximum number of FDDRL subtasks that can be active at the same time. The job class limit (CLASS-LIMIT) is always observed.
RUN-PRIORITY = *UNCHANGED / *STD / *OWN / <integer 128..255>Defines the priority of the FDDRL subtasks.
The run priority limit of the job class is always observed.
Default: *STD
RUN-PRIORITY = *STD
The default priority of the job class is assumed.
RUN-PRIORITY = *OWN
The FDDRL subtasks are given the same priority as the FDDRL main task.
RUN-PRIORITY = <integer 128..255>
The FDDRL subtasks are given the specified priority.
STATUS-OUTPUT-PERIOD = *UNCHANGED / *STD / <integer 0..60 minutes >
The status of the FDDRL subtasks is output when the specified period (in minutes) has expired. Output is to SYSOUT of the FDDRL main task.
Default: *STD
STATUS-OUTPUT-PERIOD = *STD
The default value (5 minutes) is selected for the status output period.
STATUS-OUTPUT-PERIOD = 0
The status of the FDDRL subtasks is not output.
STATUS-OUTPUT-PERIOD = <integer 1..60 minutes >
The status of the FDDRL subtasks is output when the specified time has expired.
SECURE-WAIT-TIME = *UNCHANGED / *NO / <integer 0..604800>(...)
Determines whether or how long the FDDRL subtasks should wait for successful device reservation before a tape device is reserved. The specified wait time controls the response to unsuccessful device reservation:
In the case of *NO or a wait time < 180 seconds, further processing depends on the response to the console message FBD1256.
In the case of a wait time
>=180 seconds, the subtask is aborted.
Default: *NO
SECURE-WAIT-TIME = *NO
The FDDRL subtasks are not to wait for successful device reservation.
SECURE-WAIT-TIME = <integer 0..604800>(...)
Period which the FDDRL subtasks are to wait for successful device reservation. The maximum wait time is limited to 7 days.
DIMENSION = *SECONDS / *MINUTES
Dimension of the specified period. The default is seconds.
JOB-NAME = *UNCHANGED / *STD / *SAME / <name 1..8>
JOB-NAME controls the job name for the subtask. The job name can, for example, be used by the MAREN location manager MARENLM to control the tape allocation.
JOB-NAME = *STD
The job name of the subtask is derived either from the VSN of the disk or from the name of the disk set. The VSN is preceded by the “$” character. Illegal characters in the job name, such as a period ('.') or hyphen ('-'), are replaced by the '#' character.
JOB-NAME = *SAME
The subtasks get the same job name as the main task.
JOB-NAME = <name 1..8>
The subtasks get the specified job name.
RETENTION-PERIOD = *UNCHANGED / *STD / <integer 0..32767 days >Retention period of the backup volumes in days.
Default: 0 days, i.e. no retention period
RETENTION-PERIOD = *STD
The default value (0 days) is selected for the retention period.
RETENTION-PERIOD = 0
There is no retention period. The backup volumes can be overwritten on the same day, but not in the same save run.
RETENTION-PERIOD = <integer 1..32767 days >
The backup volumes are protected against overwriting until the specified number of days has elapsed.
LOCATION = *UNCHANGED / *STD / <alphanum-name 1..8>
The location specifies the set of devices, from which tape devices for SCRATCH requests are to be selected.
Explicitly stating a location is only possible with the chargeable MAREN subsystem.
LOCATION = *STD
Device management is to determine the set of devices and select a suitable tape device from it. If MAREN is being used, device management obtains the information on the location from MAREN.
LOCATION = <alphanum-name 1..8>
Specifies the device set location from which tape devices for SCRATCH requests are to be selected. The /SHOW-DEVICE-DEPOT command can be used to display the allocations of locations to tape devices. If device management does not recognize the location specified, the device request is rejected.
Please refer to the additional information under chapter "Defining a location".
TAPE-FORMAT = *UNCHANGED / *STD / *V17-FORMAT / *V16-FORMAT / *V15-FORMAT
Determines the tape format and consequently the compatibility of the saves. The tape format set defines the maximum functionality which FDDRL may use for the save. Statements which require the functions of a higher FDDRL version are rejected. The tape format of the save determines the minimum FDDRL version required for restoration. Better performance is achieved with each higher tape format. The default value is *STD.
TAPE-FORMAT = *STD
The default value for the tape format is *V17-FORMAT for disk sets or *V16-FORMAT if FDDRL calculates a maximum multiplexing level of 2. The default value for the single disk save entity is *V15-FORMAT.
TAPE-FORMAT = *V17-FORMAT
The V17 tape format permits a multiplexing level of of 4 for the disk set save entity. Otherwise it corresponds to the V16 tape format.
TAPE-FORMAT = *V16-FORMAT
V16 tape format is used for the disk set save entity. Large tape blocks are created. The block size is approx.160 KB irrespective of the maximum I/O size of the individual disks. Multiple disks are saved to a series of tapes with dual multiplexing between disk and tape.
TAPE-FORMAT = *V15-FORMAT
Large tape blocks (64 - 256 KB) are created for saves in V15 tape format. The block size depends on the maximum I/O size of the disks and is defined for each disk type in such a way that a change of connection type is possible between saving and restoration.
REPORT-FILE = *UNCHANGED / *STD / *NONE Controls the report output.
REPORT-FILE = *STD
Generates a report file with the following default file name for each request:
$TSOS.S.FBD.<tsn>.<Auftragsdatum und -zeit>.<Auftragsname>.
The subtask reports are copied to the report file and then deleted.The name of the report file is displayed with the SHOW-REQUESTS statement.
REPORT-FILE =*NONE
Generates no report file. The subtask reports are not deleted. This corresponds to the behavior of FDDRL versions older than V19.0A.
MONITORING = *UNCHANGED / *STD / *NO
Controls the display of FDDRL requests in the SE Manager.
This entry only has a meaning when FDDRL is running on a Server Unit of an SE server. In other cases there is no SE Manager and thus no monitoring.
MONITORING = *STD
On a Server Unit of an SE server each change to the request status is reported to the
SE Manager.
When a request is completed, a report in PDF format is also created from the report file. This file can be displayed in the SE Manager.
If FDDRL is not running on a Server Unit of an SE server, this entry has the same effect as MONITORING = *NO.
MONITORING = *NO
No monitoring is performed. No FDDRL events are sent to the SE Manager. No report file in PDF format is created. If FDDRL is running on a Server Unit of an SE server, no FDDRL requests for this Server Unit are displayed in the SE Manager.
KEEP-REQUESTS = *UNCHANGED / *STD / <integer 1..32767 days> / *YES
Controls automatic deletion of requests from the request file and deletion of report files in PDF format.
This delete operation is always performed when new requests are created or when the SHOW-FDDRL-REQUESTS statement is executed.
KEEP-REQUESTS = *STD
FDDRL requests and the corresponding report files in PDF format are deleted automatically after 40 days.
KEEP-REQUESTS = <integer 0..32767 days>
FDDRL requests and the corresponding report files in PDF format are deleted automatically after the specified number of days has passed.
KEEP-REQUESTS = *YES
FDDRL requests and the corresponding report files in PDF format are never deleted automatically.