|
- OUTDDNAME or OUTDYNAM is required for a physical restore, even
for SMS-managed data. They are optional for a logical restore operation,
except:
- For multivolume data sets that are preallocated on volumes that
are different from the original source volumes; or
- When the original source volume is not available, and the restored
data set is not going to be SMS-managed.
- DFSMSdss now distinguishes between non-SMS and SMS volumes specified
in the OUTDDNAME or OUTDYNAM keywords. For non-SMS allocations, only
the volumes that are non-SMS are considered for allocation. Similarly,
only SMS volumes are considered for SMS allocations.
This distinction
is also used when determining the volume count for a multivolume allocation.
Where volume count is determined from the number of specified volumes,
only those volumes eligible for the type of allocation being done
are counted. If there are no volumes that match the type of allocation
(SMS volumes for SMS allocation, or non-SMS volumes for non-SMS allocation),
processing proceeds with a null volume list.
- If a non-VSAM data set is migrated by DFSMShsm after a logical
dump operation is performed on the data set, it should be recalled
before a restore is attempted for the data set. If it is not recalled
and if either OUTDDNAME or OUTDYNAM is specified indicating an output
volume with REPLACE or REPLACEUNCONDITIONAL and RECATALOG(*), DFSMSdss
issues a message indicating that an error occurred while trying to
catalog the restored data set because it was already cataloged as
a migrated data set. The data set will be restored on the volume specified
by the OUTDDNAME or the OUTDYNAM, but the data set will not be cataloged.
If neither OUTDDNAME nor OUTDYNAM is specified, DFSMSdss issues a
message indicating that data sets with a volume serial of MIGRAT cannot
be restored.
If the DD statement corresponding to the ddn of
the OUTDDNAME contains the data set name and disposition but not the volser,
DFSMShsm recalls the data set automatically and DFSMSdss restores
the data set.
|