Is there any reason to not have it USER_VOLUME_INCLUDE *? That way, you
only have to change it if there is some reason for not attaching a disk
to SYSTEM; you are covered when your farm grows or you change volsers.
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Martin, Terry R. (CMS/CTR)
(CTR)
Sent: Monday, August 04, 2008 2:31 PM
To: [email protected]
Subject: Re: DASD Detached from SYSTEM after IPL on one LPAR but
not the other
Thanks all for the information. It turned out that I had an
entry in my production SYSCONFIG that did not reflect the name of the
MDISKS. I changed the names and forgot to change the SYSCONFIG entry.
I had USER_VOLUME_INCLUDE LNX* and it should have been
USER_VOLUME_INCLUDE LNP* for the first three characters of the MDISKS in
the Linux hosts.
Thanks again!
Thank You,
Terry Martin
Lockheed Martin - Information Technology
z/OS & z/VM Systems - Performance and Tuning
Cell - 443 632-4191
Work - 410 786-0386
[EMAIL PROTECTED]
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Hines, Bernard
(MSFC-NNM04AA02C)[INFO PRO]
Sent: Monday, August 04, 2008 7:31 AM
To: [email protected]
Subject: Re: DASD Detached from SYSTEM after IPL on one LPAR but
not the other
While in the system config insure that the volume address is not
in the vary off range.
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Davis, Larry
Sent: Sunday, August 03, 2008 21:21
To: [email protected]
Subject: Re: DASD Detached from SYSTEM after IPL on one LPAR but
not the other
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: [email protected]
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
