1) I need to change my VM directory so that I have DEDICATE xxxx VOLID yyyyyy rather than DEDICATE xxxx yyyy (which is what we're doing now).
One possible preparation: If you consistently do not use the last cylinder of every volume, you could restore your disks into minidisks on the VM floor system and have to change nothing at all in *your* system. The disk labels, addresses, etc stay the same. 2) Since we use a VSWITCH to an OSA, I'll need to reconfigure the VSWITCH to use a different address. See above. If you run your system as a VM guest, you attach everything to the "normal" addresses from the floor system, and renumber guests appropriately. 3) We have HIPERSOCKETS defined with DEDICATE statements. This is to allow communication to our z/OS LPARs. #3 is the issue I'm having now if I want to bring things up under an LPAR at the DR site. How do I deal with this? IMHO, that would be the final argument toward installing as a VM guest. Hipersockets are a PITA, but you'd at least be able to attach them at the old addresses in the CP directory and let CP worry about the physical addresses. Is your z/OS system also runnable as a guest? If so, then define virtual hipersockets in the VM floor system and go from there.
