SMS-managed Volume Operations
Full-Volume operations
FDR and ABR full-volume dumps and restores (TYPE=FDR) and COMPAKTOR operations support SMS-managed volumes. During full-volume dumps, SMS class information from VVRs and NVRs is recorded in control records at the beginning of the backup data set (along with DSCBs and other VVDS information).
During full-volume restores and COMPAKTions, checks are made to ensure that volumes that were SMS-managed when they were dumped can only be restored to current SMS-managed volumes on a system with SMS active, and that non SMS-managed backups can only be restored to non-SMS volumes. Since SMS-managed data sets must be cataloged, SMS-managed volumes cannot be restored to new volume serials, since that would create uncataloged versions of the data sets on the volume, so CPYVOLID=YES is forced for the restore or COMPAKTion of a SMS-managed volume.
However, since the volume being restored have may changed since the backup was taken, some of the data sets on the volume may not be cataloged or may be cataloged to another volume. FDR, ABR, and COMPAKTOR make no attempt to ensure that the data sets being restored are properly cataloged by the full-volume restore operation. Since all data sets on a SMS-managed volume must have entries in the VVDS (either VVRs or NVRs), the IDCAMS command DIAGNOSE can compare the VVDS to the catalog and identify any data sets that are improperly cataloged. The IDCAMS command DELETE NOSCRATCH can be used to delete inaccurate catalog entries, and DEFINE RECATALOG may be used to rebuild accurate catalog entries, including the SMS class information, for both VSAM and non-VSAM data sets.
Under special circumstances, it may be necessary to circumvent these rules. For example, you may need to restore SMS-managed volumes under a non SMS-managed system. The keyword SMSPROT=NONE on an FDR or ABR RESTORE or COPY statement bypasses the SMS checks described above. SMSPROT=NONE is recommended (and usually required) for restores at disaster recovery sites.
SMS-managed volume conversion
When implementing SMS, there are two ways of converting data sets to SMS management. A volume can be converted in place, or data sets can be moved from non-SMS volumes to SMS-managed volumes.
IBM literature refers to the CONVERTV function of DFSMSdss as the mechanism for converting a volume in place to SMS management. The FDR system program FDRCONVT performs the same function, making DFSMSdss unnecessary. FDRCONVT can convert a volume by invoking the SMS ACS routines to assign storage and management classes to every data set on a volume. It can also convert a volume back to a non-SMS volume. See Section FDRCONVT-Overview for complete details.
DFSMSdss CONVERTV must not be used on a volume initialized for ABR, since it incorrectly modifies the ABR Model DSCB: use FDRCONVT.
FDRCOPY MOVE (described in FDRCOPY-COPY-and-MOVE-Statements) or FDRDSF DUMP and RESTORE (DSF-DUMP-Statement and DSF-RESTORE-Statement) can be used to move data sets from non-SMS volumes to SMS-managed volumes (assigning storage and management classes) or back to a non-SMS volume, using the techniques described below.
Usually, moving data sets to SMS-managed volumes with FDRCOPY is preferable to using FDRCONVT, if spare DASD volumes are available. Converting volumes requires that an entire volume be converted at one time and that any problems that would prevent conversion (such as uncataloged data sets or ineligible data set types) be resolved. If the volumes being converted contain parts of multi-volume data sets, then all of the other volumes on which those data sets reside must also be converted. An FDRCOPY MOVE allows groups of data sets to be converted in a less drastic manner, and allows for an easier fallback to non SMS-managed.