Special considerations for RESTORE

The following special considerations apply when you perform a restore operation:

When restoring a partitioned data set that has a secondary allocation of zero, the amount of unused space allocated to the target data set might be different from that of the source data set if the ALLDATA and ALLEXCP keywords were not specified for the dump.
When restoring a VSAM data set with no secondary allocation, a secondary allocation can be added as follows:
- When the primary allocation is less than one cylinder, a secondary allocation equal to the primary is created.
- When the primary allocation is greater than or equal to one cylinder, a secondary allocation is created by computing one percent of the primary and rounding up to the next cylinder (in tracks).
The index component can also have secondary space added if it has no secondary allocation.
The RESTORE FULL or RESTORE TRACK commands might invoke ICKDSF to rebuild the VTOC INDEX data set for a target volume. Therefore, users of these commands require the appropriate authority for ICKDSF.
When performing a logical or physical data set restore operation of a VSAM extended-format data set, the target data set allocation must be consistent with the source data set allocation as follows:
- If the source is an extended-format VSAM, then the target must be an extended-format VSAM.
- If the source is a compressed VSAM KSDS, then the target must be a compressed VSAM KSDS.
- If the source is an alternate index for an extended-format KSDS, then the target must be an alternate index for an extended-format KSDS.
- The target control interval size must be equal to the source.
The actions DFSMSdss performs for RENAME, RENAMEUNCONDITIONAL, REPLACE, or REPLACEUNCONDITIONAL depend on the keywords you specify and the configurations of data sets on volumes. This section contains figures that describe specific environments for DFSMSdss restore operations.
If you restore a data set that has an F8/F9 DSCB pair on the volume from which it is dumped to a volume that does not support F8/F9 DSCBs, the attributes in the F9 DSCB are lost. To retain these extended attributes, the target volumes of the RESTORE must support F8/F9 DSCBs.