Look in your system config file you used to IPL your production system and make sure there are values for all your user volumes which cause them to be attached to your system at IPL time They will look something like this, I use wild cards because we have a naming convention associated with each LPAR USER_VOLUME_INCLUDE VP* USER_VOLUME_INCLUDE DB* USER_VOLUME_INCLUDE M2D* USER_VOLUME_INCLUDE EC* USER_VOLUME_EXCLUDE M2D9%% Hope this helps
Larry Davis Tata Consultancy Services email [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Tata Consultancy Services <http://www.tcs.com/> ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Sunday, August 03, 2008 9:49 PM To: IBMVM@LISTSERV.UARK.EDU Subject: DASD Detached from SYSTEM after IPL on one LPAR but not the other Hi I IPL'ed both of my z/VM 5.3 LPARS on Sunday. After the VAL/DEV LPAR was brought up I started to logon and IPL the Linux guests. I had no problems on this LPAR. Now, after I IPL'ed the PROD LPAR I started to bring up the PROD Linux guests. This time when I logged on the guests the guest could not access any of the MDISKS assigned to it. I looked and found that all of the MDISKS were no longer attached to SYSTEM. I know these were attached on Friday because I brought all of the Linux guests up without a problem. It seems that they were detached during the IPL. On the VAL/DEV LPAR the MDISKS for the Linux guests stayed attached to SYSTEM after the IPL. Does anyone know why the MDISKS were detached from the SYSTEM on my PROD LPAR after the IPL? Thanks, Terry
