DSF Non SMS-Managed RESTORE Examples

The following are example of DSF restores of data sets that are not System Managed Storage (SMS) managed. All examples in this section are found in the JCL library installed with FDR. The member names are EX2012x.

Restore one data set example

Restore one data set from a backup data set. The data set is restored, under its original name. If the data set is currently cataloged, it is restored to the volume to which it is cataloged; otherwise, it is restored to the volume it was originally dumped from. In either case, if it is not in the VTOC of the DASD volume, it is allocated and cataloged. If it is a PS or PO data set, only its used tracks are restored.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=BACKUP.VOLUMEA,DISP=SHR
//SYSIN    DD *
RESTORE TYPE=DSF
SELECT   DSN=MY.TEST.DATASET
/*

Restore data sets by group example

Restore all the data sets that were dumped on the backup file specified by the TAPE1 DD statement, except for those data sets that start with “SYS1.”. Active data sets are not restored, but data sets being restored are not enqueued. The data sets are all restored to the volume specified by DISKx. All tracks of each data set are to be restored (the dump must also have been done with DATA=ALL). DSF preallocates any data set not currently on the DASD volume.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=SYSRES.BACKUP,DISP=OLD
//DISK1    DD UNIT=SYSALLDA,VOL=SER=XXXRES,DISP=SHR
//SYSIN    DD *
RESTORE TYPE=DSF,DATA=ALL,DSNENQ=TEST
EXCLUDE DSN=SYS1.**
SELECT   ALLDSN
/*

Restore to new name example

Restore two data sets to new names. A data set named “LEDGER.OLDFILE” is renamed to “LEDGER.NEWFILE”. A data set named “LEDGER.TRANSACT” is restored as “LEDGER.JULY.TRANSACT(+1)”. Both are restored to DASD volume LED123. If necessary, they are allocated and cataloged.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD UNIT=TAPE,DSN=BACKUP,DISP=OLD,VOL=SER=12155
//SYSIN    DD *
RESTORE TYPE=DSF,RECAT
SELECT   DSN=LEDGER.OLDFILE,NEWNAME=LEDGER.NEWFILE,NVOL=LED123
SELECT   DSN=LEDGER.TRANSACT,NEWINDEX=.+JULY(+1),NVOL=LED123
/*

Restore VSAM cluster example

Restore an existing VSAM cluster from an FDR or DSF backup data set. The cluster is restored to the volume on which it is cataloged, overlaying the existing cluster, and refreshing all associated VVDS information.

//RESTOREV EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPEA    DD DSN=FDR.BACKUP.VSAM01,DISP=OLD
//SYSIN    DD *
RESTORE TYPE=DSF
SELECT   DSN=ICF.VSAM.CLUSTER1
/*

Restore clusters to new names example

Restore two VSAM clusters from an ABR-created volume backup tape. Restore “VSAM.OLD.HISTORY” to cluster “VSAM.NEW.HISTORY” that has been preallocated; DSF does a LOCATE to get the component names of the new cluster, and restores the equivalent original components to it. Restore cluster “PAY.MASTER”to “PAY2.MASTER” that is allocated on one of the online volume whose volume serial number starts with “PAY”; DSF modifies all of the cluster's component names so that their first index is also “PAY2”.

//RESTOREV EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPEA    DD DSN=FDRABR.VXYZ010.C1002012,DISP=OLD,
//            UNIT=TAPE,VOL=SER=121777,LABEL=3
//SYSIN    DD *
RESTORE TYPE=DSF
SELECT   DSN=VSAM.OLD.HISTORY,
          NEWNAME=VSAM.NEW.HISTORY
SELECT   DSN=PAY.MASTER,NEWI=PAY2,NVOL=PAY*
/*

Restore multiple backups example

Restore all the data sets that were backed up on three backup files in one execution of DSF. By default, each data set is restored to its original DASD volume; they are allocated and cataloged if they do not currently exist. The backups were created as three consecutive files on the same backup tape (see Dump from Multiple DASD Volumes to One Tape Example for an example). The backup data sets are cataloged, so no tape volume serials or file sequence numbers are required; since they are all on the same tape volume, only one tape drive is allocated by z/OS.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=BILL.BACKUP1(0),DISP=OLD,VOL=(,RETAIN)
//TAPE2    DD DSN=BILL.BACKUP2(0),DISP=OLD,VOL=(,RETAIN)
//TAPE3    DD DSN=BILL.BACKUP3(0),DISP=OLD,VOL=(,RETAIN)
//SYSIN    DD *
RESTORE TYPE=DSF
SELECT   ALLDSN
/*

Restore Multi-Volume data sets and clusters example

Restore several multi-volume data sets, including non-VSAM data sets and VSAM clusters. The backups pointed to by the TAPEx DD statements each contain parts of these multi-volume data sets as dumped from their original volumes; the UNIT=AFF parameter insures that only one tape drive is used for all three backups. As DSF processes each backup, it restores the pieces of each multi-volume data set it finds on that backup, allocating and cataloging them if necessary. Multi-volume data sets must be restored to as many different volumes as they were dumped from. If NVOL= is used, it must specify a sufficient number of volumes. A multi-volume data set is not be usable until all pieces of the data set have been restored by DSF. See Multi-Volume VSAM Considerations ; there are some restrictions.

//RESMULTI EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=BACKUP.VPROD01,DISP=OLD
//TAPE2    DD DSN=BACKUP.VPROD02,DISP=OLD,UNIT=AFF=TAPE1
//TAPE3    DD DSN=BACKUP.VPROD03,DISP=OLD,UNIT=AFF=TAPE1
//SYSIN    DD *
RESTORE TYPE=DSF
SELECT   DSN=NON.VSAM.MULTI01
SELECT   DSN=NON.VSAM.MULTI02,NVOL=(TEST01,TEST02,TEST03)
SELECT   DSN=VSAM.MULTI03
SELECT   DSN=VSAM.MULTI04,NVOL=TEST*
/*

Restore to 3390-9 example

Add data sets to a 3390-9 with DSF, in order to merge several lower density DASD into one. An FDRdisk-to-disk copy or a full volume restore (see Working-with-FDR) or FDRPAS SWAP was done to move one 3390-3 to this 3390-9. Now the contents of a 3390-3 volume can be added to the 3390-9 from an FDR or DSF backup of the smaller 3390. DSF allocates space for all restored data sets and recatalogs them to the new volume (RECAT recatalogs non-VSAM data sets, and VRECAT scratches and uncatalogs any VSAM clusters before allocating them on the new volume).

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//DISK1    DD UNIT=SYSALLDA,DISP=OLD,VOL=SER=D3390A <---3390-9
//TAPE1    DD DSN=BACKUP.D3390C,DISP=OLD       <---3390-3 Backup
//SYSIN    DD *
RESTORE TYPE=DSF,RECAT,VRECAT
EXCLUDE DSN=**CATALOG**                    (See "Note" 1 below)
  SELECT   ALLDSN                           (See "Note" 2 below)
/*

Important

FDRMOVE, a separate product, performs the consolidation of multiple lower density DASD to larger DASD with less effort. FDRMOVE is documented in the FDRPAS manual.

Restore from 3390-9 to 3390-3 example

Restore data sets from a backup of a 3390-9 to three 3390-3 volumes. DSF allocates as many data sets as it can on the first volume specified, and the same on the second volume, and the remainder on the third volume. The data sets are restored to the three DASD volumes in one pass of the backup tape. DSF allocates space for all restored data sets and recatalogs them to the new volume (RECAT recatalogs non-VSAM data sets, and VRECAT scratches and uncatalogs any VSAM clusters before allocating them on the new volume). This is especially useful at a disaster recovery site, if there are not enough high-density volumes on which to do full-volume restores.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=BACKUP.D3390A,DISP=OLD
//SYSIN    DD *
RESTORE TYPE=DSF,RECAT,VRECAT
SELECT   ALLDSN,NVOL=(D3390B,D3390C,D3390D)    (See "Note" 2 below)
/*

Important

A catalog should not be restored in the same execution as any data sets cataloged in that catalog. The catalog should be restored in a separate step.
DSF automatically excludes the SYS1.VTOCIX, SYS1.VVDS, and the ABR Model DSCB from the restore, giving the warning message FDR159 REASON=3, which may be ignored. (For the VVDS, this message is issued even if the VVDS was not selected during the backup). If you want to avoid receiving these messages and get a cleaner listing, you should specifically exclude them, for example:

EXCLUDE DSN=SYS1.VTOCIX.*

EXCLUDE DSN=SYS1.VVDS.*

EXCLUDE DSN=FDRABR.V*

Absolute track restore example

Restore by absolute track. One track is restored from a backup on a 3590 tape drive to a 3390 DASD volume, replacing that track on the output DASD volume. A DISKx DD statement or NVOL= operand must be provided to identify the output volume.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//DISK1    DD UNIT=3390,DISP=OLD,VOL=SER=M33901
//TAPE1    DD UNIT=3590,DSN=BACKUP.M33901,
//            VOL=SER=123456,DISP=OLD
//SYSIN    DD *
RESTORE    TYPE=DSF
SELECT     FROM(CYL=10,TRK=5),TO(CYL=10,TRK=5)
/*

Restore data sets to a new name ensuring no data sets overlaid

Restore a group of data sets with a specific HLQ replacing the 2nd qualifier with a new qualifier. Ensure that the data set being restored does not overlay an existing data set. The PRESTAGE operand is used to ensure an existing data set is not overwritten.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DISP=OLD,DISP=SYSTEM.CPUA.BACKUP
//SYSIN    DD *
RESTORE TYPE=DSF,PRESTAGE
SELECT   DSG=SYS1.CPUA.**,NEWI=.CPUB
/*

Restore all data sets from the cloud to a DASD volume

Restore all the data sets from a backup on a cloud to a DASD volume. This example uses the cloud backup from the previous DUMP example.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//FDRSUMM DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//DISK1    DD UNIT=SYSALLDA,DISP=OLD,VOL=SER=SH20CC
//TAPE1    DD DISP=OLD,DSN=CLOUDVOL.BKUP1
//SYSIN    DD *
RESTORE TYPE=DSF
SELECT   ALLDSN
/*

Restore all data sets from the cloud with backup control file missing

Restore all the data sets from a backup on a cloud to a DASD volume when the backup control file that was created during the DUMP is missing. When the backup control file is missing, the CLOUD=, CLOUDUSER, and CONTAINER= operands must be specified if the defaults are not being used. This example uses the cloud backup from the previous DUMP example.

//RESTORE EXEC PGM=FDRDSF,REGION=0M
//FDRSUMM DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//DISK1    DD UNIT=SYSALLDA,DISP=OLD,VOL=SER=SH20CC
//SYSIN    DD *
RESTORE TYPE=DSF,CLOUD=TS7700CD01, CLOUDUSER=CLOUDUSER,
          CONTAINER=FDR.MY.CONTAINER
SELECT   ALLDSN
/*