zDMF device swap processing

If HyperSwap® is available, device swaps will be transparent to zDMF processing. When a device swap occurs, it is automatically recognized by all zDMF Servers, and the device allocations are transparently adjusted for all migration groups. Message GZD3125I is issued for each device that is swapped. This message reports the volume serial, old device number, and new device number of the swapped device. This message is issued on all zDMF Servers that have migration groups using the swapped device.

Note: IBM® recommends that HyperSwap be enabled on all z/OS® images executing zDMF.

If HyperSwap is not available, device swaps may require manual intervention depending on your zDMF Server configuration.

If a zDMF Server has a migration group definition that implicitly or explicitly specifies a device that is swapped on another z/OS image that shares the device, only the zDMF Server where the z/OS SWAP command was executed will be aware of the device swap. All other zDMF Servers will not recognize the device swap. This lack of recognition will be reported by message GZD3128E on the zDMF Server where the z/OS SWAP command was issued. This message reports the volume serial, old device number, and new device number of the swapped device.

All relevant migration groups will be placed in DEACT status on all zDMF Servers. Any normal z/OS device management procedures, such as vary offline/online, must be performed on all z/OS images.

All migration groups that have the swapped device implicitly or explicitly specified must then be deleted, promoted, and activated so that the swapped device's new characteristics will be recognized. Cycling the zDMF Server without redefinition of all migration groups is not sufficient. Abend or other unpredictable results may occur if this is not performed against all migration groups.