Jonathan, Yes I was thinking the same thing about using the SYSTEM CONFIG to isolate which devices come online during IPL, and I will probably take advantage of this feature to some extent in the future. Right now, the duplicate volsers makes it hard to keep backup sets straight and opens up other obvious exposures and adds more complexity to the migration to the z10.
Thanks to all that replied. Regards, Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Quay, Jonathan (IHG) Sent: Friday, January 30, 2009 6:12 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Re-labeling CP-Owned volumes on a live system You don't *have* to do this. I have five VM images and just use system config to define what images see what device addresses and thus segregate which duplicate volsers go with which system images. ________________________________ From: The IBM z/VM Operating System on behalf of Mike Rydberg Sent: Wed 1/28/2009 11:01 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re-labeling CP-Owned volumes on a live system I am assisting with a migration from a z9 to a new z10, which runs several VM LPARs. One problem is that a couple of the VM systems use the same DASD volsers on different device addresses. These volsers had been isolated by creative IOCP configuration on the z9, segregating the duplicate volumes/devices from each of the VM LPARs, but the problem is such that it needs to be resolved now, so that each VM system has unique CP volsers. The VM system that we chose to re-label does not use dirmaint, so I'll be hand editing of the USER DIRECT. It's been a long time since I have done this, so I would like to know if I have forgotten any of the key steps to re-label all the CP Owned volumes from a live system. Here's the steps that I think will accomplish this. While the system is up and running: - update the CP Owned list in the MAINT CF1/2 SYSTEM CONFIG - xedit a copy of the USER DIRECT and change the CP volsers on all the MDISK statement to the new volsers. (ie: change /OLDRES/NEWRES/ *, c /OLDSPL/NEWSPL/ *, c /OLDPAG/NEWPAG/ *, c /OLDW01/NEWW01/ *, etc) - use CPFMTXA to change the labels on all the old volsers to the new volsers. This can be done after the system is shutdown, if that matters. - place the updated USER DIRECT online (DIRECTXA USER DIRECT), note that I'm not sure if it matters whether this is done before or after the volume re-label step. - Shutdown and IPL VM with the device address for NEWRES. I have backups of all the volumes already. We have other VM systems with access to these DASD volumes for recovery if things don't go well or that can assist in this task. Is there anything obvious with that I may have missed or a better order for these steps? Thanks Mike
