FROMDUMP: Specifying which dump copy is used for restoring data sets

Explanation: FROMDUMP is an optional parameter specifying which dump copy should be used for the restore.

FROMDUMP specifies the recovery should use a dump copy from dump volumes.

DUMPCLASS(class) | DUMPVOLUME(volser) | DUMPGENERATION(dgennum) are mutually exclusive, optional subparameters of FROMDUMP specifying a particular class, volume, or generation from which the restore should be made. Neither DUMPGENERATION nor DUMPVOLUME should be specified if the DATE parameter is specified.

Subparameter	Explanation
DUMPCLASS(class)	The dump copy to be used to restore a data set or volume should come from a particular class. This subparameter is needed only if the source volume was dumped to more than one dump class. For class, substitute from 1 to 8 alphanumeric characters for the class of the volume from which the data set or volume is to be restored.
DUMPVOLUME(volser)	A particular dump volume is used for restoring a data set or a volume. For volser, substitute the volume serial number of one of the dump volumes that contains part of the wanted dump copy of the source volume to be restored. DUMPVOLUME is not valid when GENERATION, VERSION, DATE, DUMPCLASS, or DUMPGENERATION are specified.
SOURCEVOLUME(volser)	The identified dump copy is used when the data set to be recovered from a dump is not cataloged or is migrated, and has no backup copy, and more than one valid dump copy is stacked on the volume specified with DUMPVOLUME.

If a multivolume, cataloged data set is to be recovered, the RECOVER command must be issued with the FROMDUMP parameter and the DUMPVOLUME subparameter to ensure that DFSMShsm directs each part of the data set to the correct volume. In this case, the TOVOLUME parameter is optional but, if used, must be the name of the volume as identified in the catalog entry.

There must be similar device types between the original DASD and the target DASD, with the exception that you may recover data dumped from a 3380 DASD to a 3390 DASD that is in 3380 emulation mode. The following is a scenario example:

The volume serial number PRIM01 is a 3380 DASD dumped to tape cartridge DUMP05.
All 3380 DASD devices have been replaced by 3390 DASD.
The 3390 DASD runs in a 3380 emulation mode and initializes with the volume serial number PRIM01.

The command to recover PRIM01 is as follows:

   RECOVER * TOVOLUME(PRIM01) UNIT(3380) FROMDUMP(DUMPVOL(DUMP05))

DUMPGENERATION(dgennum) specifies that a particular dump generation should be used as a source for restoring a volume. The dgennum, can be up to three digits long, but its value must be between zero and 99. Zero is the most-recent generation. Use the LIST command to determine what generation numbers exist. DUMPGENERATION should not be specified if you are restoring a single data set.

APPLYINCREMENTAL specifies that an incremental volume recovery process is to follow immediately after the volume restore and is to be a part of the single request to recover a specific volume. APPLYINCREMENTAL has meaning only when a volume is being restored. The volume does not have to have been processed by the DFSMShsm volume backup function. If the volume was not backed up with the DFSMShsm function, DFSMShsm still tries to find more recent backup versions created from individual data set backup requests after the dump copy was created. It is not applicable if a data set request is entered.

Note:

The APPLYINCREMENTAL parameter is not honored if DFSMShsm determines that the target volume is owned by a ICF catalog that resides on the target volume. This is to avoid conflicts in the way DFSMShsm supports ICF catalogs and the data sets cataloged in them.
If Data Facility Product Version 2 Release 3.0 or higher is not installed, you cannot use the APPLYINCREMENTAL parameter during backup and recovery when the target volume has an Integrated Catalog Facility catalog.
The APPLYINCREMENTAL parameter is not allowed when the target volume is a DFSMShsm-owned volume.
The SOURCEVOLUME subparameter is only used to identify which dump copy on a dump volume should be used to restore a data set. It does not have all the implications of the FROMVOLUME parameter.
If you use DUMPVOLUME to specify a dump tape, and that dump volume has more than one valid dump copy stacked on it, each dump copy is for a different source volume. For DFSMShsm to restore the data set, it must be told which source volume (which dump copy) is needed. It uses information in the following order: FROMVOLUME (if specified); SOURCEVOLUME (if specified); the volser where the data set is cataloged; if not cataloged, the volume from which the data set was last backed up. If none of these is specified or available, the RECOVER command fails.
The VTOC and the volume serial on the target volume may have changed as a result of this operation. Before the volume can be accessed on any remote system, the UCB must be refreshed. The refresh occurs automatically if the volume is online and the device manager REFUCB function is enabled. You enable the REFUCB function through PARMLIB member DEVSUPxx or the MODIFY DEVMAN command. For more information, refer to the description of the REFUCB keyword in z/OS MVS Initialization and Tuning Reference or z/OS MVS System Commands.

Defaults: None.