When moving volumes, ensure that the VTOC on the target device is large enough to hold entries for all the data sets to be placed on the target device. If you do not expand the VTOC when moving to a larger volume, DFSMSdss logical data set processing might fail. The following two sections describe how the size of the target VTOC is affected by DFSMSdss processing.

You can also use the REFORMAT EXTVTOC or REFORMAT NEWVTOC functions of ICKDSF to extend or reallocate the VTOC on a volume if it is not large enough.

When performing a full-volume restore operation to DASD, DFSMSdss automatically corrects the free-space information on the volume and can invoke ICKDSF to rebuild the VTOC index. DFSMSdss takes this action when it copies data to a larger-capacity DASD from a smaller-capacity DASD or when both of the volumes, including volumes of equal capacity, contain a VTOC index. DFSMSdss allocates a large (more than 65 535 tracks) dummy data set to recalculate the free-space information. You can ignore any IEC614I messages that DFSMSdss generates during this process.

Following a COPY or RESTORE operation, the VTOC location or the volume serial on the target volume may change. Before this volume can be accessed on any remote system, the UCBs on the remote systems 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.