I am not sure if DIRECTXA really checks the volser of the device listed in its control statement, but since the volser is there, I change the volser of that volume between editing the new directory and using DIRECTXA to write the object directory to it.
I think you've got all the steps in a good order. /Tom Kern Mike Rydberg wrote: > 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
