Thanks, Scott! -----Original Message----- From: Scott Rohling <[email protected]> Reply-to: The IBM z/VM Operating System <[email protected]> To: [email protected] Subject: Re: Merging DirMaint? Date: Mon, 16 Mar 2009 11:49:04 -0600
Sure -- just do a DIRM RLDE when you're done so DIRMAINT knows the new region names... Scott On Mon, Mar 16, 2009 at 10:31 AM, Dave Keeton <[email protected]> wrote: Ron, You're right, test is going away. It will eventually become the next release of z/VM at some point later down the road... I just had a 'duh' moment after reading your reply. The scope of the problem is not nearly as big as I thought. In test there are only a couple of Linux guests, as well as the CA products. The bulk of the production guests will, as you said, come over with the existing EXTENT CONTROL file. My only remaining question then would be is it possible to redefine the EXTENT CONTROL file and change the RegionId definitions to using the VolSer instead? -----Original Message----- From: Ron Schmiedge <[email protected]> Reply-to: The IBM z/VM Operating System <[email protected]> To: [email protected] Subject: Re: Merging DirMaint? Date: Mon, 16 Mar 2009 10:17:59 -0600 Dave, I don't think that merging the two versions of USER DIRECT (which was the answer you got) will have any affect on the EXTENT CONTROL file. What you have on the testbed now will not change unless you get the two EXTENT CONTROL files and merge entries from each. So if you want your new production to retain the definitions for production, you would put the production EXTENT CONTROL file onto your testbed and throw away the testbed one - or hide it somewhere for the testbed you plan to rebuild. If your testbed is going away (which I think you said was happening), why would you need to retain the testbed version of the region definitions? On Mon, Mar 16, 2009 at 10:01 AM, Dave Keeton <[email protected]> wrote: > I have a follow-up question about the EXTENT CONTROL file.... In my > ignorance, I used the same REGIONS naming convention in both production > and test. Here's an example: > > This is the test system: > > :REGIONS. > *RegionId VolSer RegStart RegEnd Dev-Type Comments > LNX901 LNX9G6 1 END 3390-09 > > This is production: > > :REGIONS. > *RegionId VolSer RegStart RegEnd Dev-Type Comments > LNX901 LNX9F1 1 END 3390-09 > > It looks like to me I've shot myself in the foot by using the same > convention for the RegionId. Any suggestions on how to clean this up? > > Thanks, > Dave > > I'm trying to determine how to merge all the directory entries for my > production systems into the test directory prior to IPL'ing z/VM 5.4 as > production. My first concern is the EXTENT CONTROL. Each instance of > DirMaint has its own DASD pool, separate from the other. I am concern > about things getting mucked up by consolidating the pools. What's the > most effective way to do this? > > When z/VM 5.4 is up and running correctly, the plan is to rebuild the > test LPAR with the latest release of z/VM so we can stay on top of the > releases. > > Thanks in advance, > > Dave >
