> For example I managed to get it up boot but I couldn't get CMS to start: > > 03:14:54 ipl 190 > DMSWSP327I The installation saved segment could not be loaded > z/VM V5.4.0 2008-10-13 07:27 > > DMSDCS1083E Saved segment CMSPIPES does not exist > DMSDCS1083E Saved segment CMSPIPES does not exist > DMSDCS1083E Saved segment CMSVMLIB does not exist > DMSACP113S A(191) not attached or invalid device address > Ready; T=0.01/0.01 03:14:55
I have managed to do this to several z/VM systems over the years. The way it always happens to me is having two systems running that can both "see" each other's disks. It seems the volumes other than the IPL volume are referenced by labels (volsers), not real device numbers (rdevs). So I believe the system with the higher rdevs starts spooling and paging to another system's volumes. There are a few ways to avoid this: 1) Use Offline_at_IPL in SYSTEM CONFIG to prevent each system from seeing the other systems' disks. 2) Relabel the W01, W02 (No W01 and W02 volumes if using 3390-9s), SPL and PAG volumes at install time, at the start of the INSTDVD EXEC, for example. 3) Relabel all 5 volumes (3 for 3390-9s) immediately after install. #1 and #2 have the side effect of having mutiple volumes with the default label of the "res pack" (540RES for example). If a z/OS system can also "see" these volumes, the sysadmins get upset because it slows down a z/OS IPL. If that isn't a problem, #2 is probably the easiest. #3 can be tricky, so it is documented in the Virtualization Cookbooks (http://www.redbooks.ibm.com/abstracts/sg247493.html for SLES or http://www.redbooks.ibm.com/abstracts/sg247492.html for RHEL), section 4.11 Hope this helps. "Mike MacIsaac" <[email protected]> (845) 433-7061 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
