Mr McDonough, The z/VM "second level system" is the last bastion of WildWestSystemProgramming, you can do anything you want, any way you want . ( as long as it doesn't crash your first-level, of course ).
You have two approaches, really, if you have an LPAR environment availabl e. Approach 1 is to create a UserID to be the second-level guest, LEVEL2VM, or whatever you like. Make copies of as many of your first-level volumes as you need to sufficiently present the "image" of your first-level. Define SPECIAL GRAF in your level 2 UserID so you can DIAL to it once you've gotten it IPL'd. Then, IPL it, and knock yourself out with whatever you want to try. Approach 2 is to do the same, but in a spare LPAR, if you have that luxur y. The "Running Guest Operating Systems" manual in the z/VM doc set has some useful advice, too. Have fun! On Fri, 12 Feb 2010 07:52:26 -0600, McDonough, George <george.mcdono...@mmc.com> wrote: >Hello, Everyone. > >We recently installed a z/VM environment (version 5.4) for a Linux proof >of concept. Going into this project, we only had minimal VM experience >and it was years ago. Despite that, everything went well and we have >since moved some of the Linux machines to production. > >In the upcoming months we are going to be migrating from a z9 processor to >a z10 and it looks like our z/VM system will need maintenance on it. I' m >looking for some direction and instructions on how to build a second lev el >VM system to apply the maintenance to. I've poured through alot of >manuals and Redbooks looking for a step by step process and the best I'v e >found so far are the z/VM Automated Installation and Service and the z/V M >Running Guest Operating Systems books. > >Does anyone have a better document that will give us a cookbook process to >put together a second level system? > >Thanks for your time and help. > >George.
