I like to know what happens to my systems. So I even never tried PUT2PROD.
And just like Brian, I swap MAINT's minidisk addresses 190/193/19E with 490/493/49E. I wish DIRMAINT provided a SWAPMDSK command to swap mdisk addresses, now I need DIRM OFFLINE DIRM FOR MAINT CHV 190 TO FFFF DIRM FOR MAINT CHV 490 TO 190 DIRM FOR MAINT CHV FFFF TO 490 ...similar for other mdisks... DIRM ONLINE Furthermore, I labeled my 190/490 disks to correspond to a CMS saved system (like CMS20A and CMS20B or even CMS22A). I've got an NSS named CMS that reads the label of the 190 disk and then IPLs that NSS (i.e. CMS20A or B) The SYSPROF EXEC also reads the S-disk label too and uses the same suffix to load segments for PIPE, SFS etc: CMS20FA/CMS20FB etc I wrote this stuff in the VM/SP R6 days when we often required 2 or 3 CMS levels (e.g. some fix we needed for SFS caused problems for DB2), as the segment names are differnt too, I can switch CMS levels during day-time. I also use it when migrating to a new release: selected users link to the 190 disk of the new MAINT user and simply "IPL CMS" as they always do. More info and code: http://www.vm.ibm.com/download/packages/descript.cgi?IPLER Kris, IBM Belgium, VM customer support
