With the RESTORE command, you can restore data to DASD volumes from DFSMSdss-produced dump volumes, which are identified with the INDDNAME keyword.

The restore function is logical or physical, depending upon the dump volume. If the dump volume was made physically, a physical restore is made. If it was made logically, a logical restore is made. If the data was compressed when it was dumped, it is automatically expanded to its original form during the restore operation.

Using the ALLDATA or ALLEXCP keyword during a dump affects target data set allocation during a restore. Only used space is dumped for both a physical and logical data set dump unless the ALLDATA or ALLEXCP keyword is specified as part of the DUMP command.

When ALLDATA or ALLEXCP is specified, the total allocated space is dumped. During a physical data set restore, the target data set is allocated with the same amount of space as the source data set. During a logical data set restore (without the ALLDATA or ALLEXCP keyword), the target data set is allocated according to the amount of space used in the data set, thereby releasing unused space. If logical data set processing is used and the target data set must preserve the total allocation of the source, the ALLDATA or ALLEXCP keyword should be specified during the dump.

When ALLDATA or ALLEXCP is specified for an extended-format sequential data set, data beyond the last-used-block pointer is not retained. The target data set is allocated with the same amount of space as the source data set during a logical restore or copy operation.

As with a data set DUMP command, you can use filtering to select data sets for restore processing. DFSMSdss reads the entire dump data set once during a restore regardless of how much data is actually being restored. This will result in multiple tape mounts if the dump data set is on multiple tapes.

Attention: You should restore a dumped data set that has extended attributes in an F9 DSCB to a volume that supports F8/F9 DSCBs. Otherwise, these extended attributes are lost. DFSMSdss propagates the vendor attributes if they exist in the F9 DSCB of the primary volume when DFSMSdss performs catalog processing or if they exist in the first volume that DFSMSdss processes when you specify input volumes. To prevent losing extended attributes, all volumes that contain data sets with vendor attributes in the F9 DSCB must be extended address volumes.

For more information about filtering, refer to DFSMSdss filtering—choosing the data sets you want processed.

For information about using automatic class selection (ACS) routines during DFSMSdss restore operations, refer to ACS routine information.