Title: 2nd-Level VM Install Question

Dave,

 

You are being cautiously paranoid.  J

 

You are correct in your thinking that the second level guest with dedicated device numbers will only see those vol-ser’s that are attached to the second level guest or dedicated to it.

 

Your concern would be for the first level system seeing duplicate vol-ser’s, primarily at IPL time. To avoid confusing the first level system during IPL, you can use the “Offline_At_IPL” statement in your first level SYSTEM CONFIG file. If you attach/dedicate device number 1000 – 1007 to your second level guest, the code – Offline_at_IPL 1000-1007 will prevent the first level system from using these device numbers and making them part of the active configuration during IPL. Once the first level system is IPL-ed, you can then vary device numbers 1000-1007 online, attach them to your second level system and off you go.

 

I use this same scheme across LPARs. I have two z/VM system and I use the “offline_at_ipl” scheme to keep the two systems separated.

 

HITACHI
 
DATA SYSTEMS

 

Raymond E. Noal

Lab Manager, San Diego Facility

Office: (858) 537 - 3268

Cell:   (858) 248 - 1172

 


From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of KEETON Dave B
Sent: Wednesday, December 07, 2005 3:48 PM
To: [email protected]
Subject: 2nd-Level VM Install Question

 

In building a second level VM instance of VM510, under VM510, I see that INSTIIS wants to pin VOLIDs that are the same as my first level system. I understand that these volumes will only be attached to the second level guest user and are on different real devices but writing a non-unique label to multiple DASD volumes used in the same LPAR has me a little freaked. Is there a way to change the default VM510 VOLIDs or, since these are unique to the guest, am I just being paranoid?

TIA,

Dave Keeton
Systems Analyst
z/VM Linux Support
Oregon Dept. of Transportation
955 Center Street NE
Salem, OR 97301

Office: (503) 986-3199
FAX:    (503) 986-3242

Reply via email to