Re: 2nd-Level VM Install Question

[KEETON Dave B]

All,

Thanks for all the suggestions and help. We're going to stick with Hans' suggestion for now and look at the options for doing a second level, IPLable, production systems after getting the sandbox up.

Regards,

 

Dave

---

From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack
Sent: Thursday, December 08, 2005 4:12 AM
To: VMESA-L@LISTSERV.UARK.EDU
Subject: Re: 2nd-Level VM Install Question

Dave--I would recommend the Hans Rempel approach over the idea of keeping the 2nd level system volids off-line except where you want them.  Sooner or later, you are going to get your hands crossed and do something to the wrong nnnRES volume.  The better approach, however IMHO, is to not leave the production system volid's the same as what is shipped in the starter system.  It is a pain in the rear to have to go in and rename the volid's in an existing system but it is a far better approach.  Look in the archives on this list for many discussions on changing the volid's on an existing system.  Then, once you've got that done, you're protected forever at least in your production environment.
Jim

At 06:47 PM 12/7/2005, you wrote:

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?


Jim Bohnsack
Cornell Univ.
(607) 255-1760