You can recover a volume or ranges of tracks from a full-volume dump operation. If the dump volumes resulted from a full dump operation, you can do a full or a tracks restore (that is, ranges of tracks) or a data set restore operation. If the dump volumes resulted from a tracks dump operation (that is, ranges of tracks), you must do a tracks RESTORE command, which can consist of a subset of the dump data.

An example of a full-volume restore operation is:

RESTORE  -
        INDDNAME(TAPE)  -
        OUTDDNAME(DASD1)  -
        PURGE

With the restore operation, you can copy the volume serial number to the output DASD with the COPYVOLID keyword. For example:

RESTORE  -
        INDDNAME(TAPE)  -
        OUTDDNAME(DASD1)  -
        COPYVOLID  -
        PURGE

For information about using DFSMSdss to restore Linux for System z® partitions and volumes, see Dumping and restoring Linux for System z partitions and volumes.

You must consider several factors when restoring volumes in an SMS environment. Before you start to restore a full volume, you must ensure that the status of the target volume is synchronized with its environment. For example, if the target volume is a non-SMS-managed volume, the volume must not be defined in a storage group. Conversely, if the target volume is an SMS-managed volume, the volume must be defined in a storage group. Finally, if the target volume is SMS-managed, then SMS must be active for the full-volume restore operation.

If you are using Record Level Sharing (RLS), be careful when restoring volumes with the FULL or TRACKS keywords. If the target volume has data sets associated with retained locks or data in the coupling facility, a full-volume or tracks restore can result in data integrity problems.

When restoring data in a full volume or tracks operation, DFSMSdss resets the data-set-changed indicator in the VTOC for each restored data set. This action indicates that the data set has not changed since the previous backup.