VM volume tolerance

VM volumes can now be copied and relabeled using TDMF in an MVS environment. However, TDMF cannot monitor updates to the source volume while the migration is in progress, nor can the VM (CP and CMS) control block be manipulated to achieve a non-disruptive Swap migration.

To migrate a VM formatted volume, it must be varied offline from all attached VM systems. In the case of a system, spool, or page volume, the associated VM systems must be shut down and later IPL’d.

Important: For volume migrations, updates to the source volume made during the migration by users other than the z/OS guest systems, might not be copied to the target. These users will continue to access the obsolete source volume after the swap, and users that link to the source volume by its original device address, and not its volume serial number, will need to change their profiles. For Point-In-Time migrations, updates to the source volume made during the migration by users other than the z/OS guest systems, might not be copied to the offline target.

Note: The FASTCOPY option is not available for use when migrating a VM formatted volume, as VM volumes are not required to have a VTOC; thus, the information required for the FASTCOPY option is unavailable.