DSF RESTORE Job Control Requirements
To execute DSF for a RESTORE operation, the following JCL statements are required.
STEPLIB or JOBLIB DD statement
If FDR is not in the system link list (LNKLST), specifies the program library where FDRDSF resides. The library must be APF authorized.
EXEC statement
Specifies the program name (PGM=FDRDSF), region requirement (REGION=, see EXEC Statement), and optional PARM= operand.
If a parameter (PARM) field is specified, DSF uses data specified as the first control statement, which must be a valid DUMP or PRINT statement; if the PARM data contains a slash “/”, the data after the slash is used as the second control statement (usually a SELECT). For example,
//FDR EXEC PGM=FDRDSF,PARM='RESTORE TYPE=DSF' //FDR EXEC PGM=FDRDSF,PARM='RESTORE TYPE=DSF/ SELECT DSN=A.B.C'
If FDRDSF is invoked from a user program, Register 1 must follow IBM’s convention for passing data from the PARM field.
DISKx DD statement
Specifies an output DASD volume. The format is:
//DISK1 DD UNIT=unit,VOL=SER=vol,DISP=OLD
unit
A generic name, such as 3390, or an esoteric name assigned during your I/O configuration, such as DISK or SYSALLDA.
vol
The volume serial assigned of the DASD volume (if an esoteric unit name is used, the volume serial must be mounted on a DASD unit that is part of that esoteric). Only a single DASD volume serial may be specified. You may use either DISP=OLD or DISP=SHR; it makes no difference.
x
May specify any single alphanumeric (A-Z, 0-9) or national (@, #, and $ in the US) character and must have a corresponding TAPEx statement. If DUMMY is specified, this DD statement is ignored.
The DISKx DD statement is optional; DSF dynamically allocates required output volumes if necessary. If present, the volume pointed to by the DISKx DD statement is used to as the default target volume for restoring data sets selected from the TAPEx backup file, although this target volume may be overridden by SMS or the NVOL= operand. Complete rules for output volume selection are in Target DASD Volume Selection Rules.
FDREMAIL DD statement
Specifies input control statements for the FDR e-mail facility. If present, e-mail messages can be sent for unsuccessful or successful FDR operations. See FDR-E-mail-Notification-Facility for requirements and details.
SYSIN DD statement
Specifies a data set containing the control statements for DSF. Usually a DD * data set. It is required, but if control statements were provided in the EXEC PARM=, it can be DUMMY.
SYSPRINT DD statement
Specifies the output message data set; it is required. It is usually a SYSOUT data set but if is it assigned to a data set on tape or DASD, this DD statement must specify DISP=MOD.
SYSUDUMP DD statement
Specifies the abend dump data set. Usually specifies a SYSOUT data set. Although not required, we strongly urge you to always include this DD statement, so that we can help you diagnose error conditions. If you have a debugging aid product on your system that would prevent the desired dump, please add the appropriate one of these statements to the JCL so that a fully-formatted dump is produced.
//ABNLDUMP DD DUMMY Print normal IBM dump in addition to the Abend-AID Report //CAOESTOP DD DUMMY Turn off CA OPT II & CA SYSMDUMP //DMBENAN DD DUMMY Turn off DumpMaster //ESPYIBM DD DUMMY Turn off Eye-Spy //IDIOFF DD DUMMY Turn off IBM Fault Analyzer
TAPEx DD statement
Specifies an input backup data set on tape or DASD, from which data is to be restored. “x” may be single alphanumeric (A-Z, 0-9) or national (@, #, an $ in the US) character. There may be up to 39 such TAPEx DD statements; DSF restores from each in turn in the order they appear in the JCL. Restores are always done one backup at a time, there is no option for concurrent data set restores.
Each TAPEx DD statement must point to an FDR, DSF, ABR, or SAR backup on tape or DASD. Backups may not be concatenated on a single TAPEx DD statement; use multiple TAPEx DD statements if multiple backups are to be restored.
For RESTORE operations from cloud storage
The TAPEx DD statement points to the backup control file that was created during the backup. If you are restoring the backup control file itself, then the TAPEx DD statement allocates space for the backup control file; see Restoring-a-TCT-Backup-Control-File-From-the-Cloud for details.