Hi Also remember to print out a copy of the Directory of the Clone or a DIRMAP/DISKMAP these will have the cylinder locations of the your DIRECTORY and SYSTEM CONFIG files. This comes in handy if you should need to change something on the CLONE after building it. You can do a DEFINE MDISK on the 1st level guest pointing to your CLONE RES and make changes to the DIRECTORY and or SYSTEM CONFIG. You can actually UPDATE the DIRECTORY of the CLONE from the 1st level z/VM and your back in business.
This saved me a few times from having to do more work than necessary. Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191 -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of McDonough, George Sent: Friday, February 12, 2010 2:23 PM To: [email protected] Subject: Re: Building Second Level VM System For Maintenance Hello. Thanks to everyone who responded. I think I'm beginning to get the picture on how to build the environment. My biggest confusion was the cloning process. I was under the impression (either I was told or I read it somewhere) that the system looked for volser 540RES and that name could not be changed. Obviously if that were the case, building a second instance with a volume of the same name could create a management nightmare. That was a hot topic of conversation when I first joined this list. But it looks like I can use distinct names for the second level machine with the corresponding updates to the config file. If this is wrong, please correct me. Once again, thanks for everyone's time and assistance. George. George McDonough, z/OS Project Leader MMC Global Technology Infrastructure | Enterprise Systems Engineering 431 Washington Street, Mail Stop G-2-G, Franklin, MA 02038, USA +1 (508) 553 2025 | Fax +1 (508) 553 3834 | [email protected] www.mmc.com -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] Sent: Friday, February 12, 2010 12:42 PM To: [email protected] Subject: Re: Building Second Level VM System For Maintenance George, I have described the cloning of a zVM with own volume labels 2 years ago on the thread below. http://listserv.uark.edu/scripts/wa.exe?A2=ind0807&L=IBMVM&P=R1076&I=-3&; X=62B6C21118642982C6&Y=fjpohlen-maillist%40gmx.de Hope this helps. kind regards Franz Josef Pohlen Am 12.02.2010 14:52, schrieb McDonough, George: > 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 t o 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 > leve l 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've > > found so far are the z/VM Automated Installation and Service and the > z/VM > > Running Guest Operating Systems books. > > Does anyone have a better document that will give us a cookbook > process t o put together a second level system? > > Thanks for your time and help. > > George. > > ********************************************************************** This e-mail transmission and any attachments that accompany it may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law and is intended solely for the use of the individual(s) to whom it was intended to be addressed. If you have received this e-mail by mistake, or you are not the intended recipient, any disclosure, dissemination, distribution, copying or other use or retention of this communication or its substance is prohibited. If you have received this communication in error, please immediately reply to the author via e-mail that you received this message by mistake and also permanently delete the original and all copies of this e-mail and any attachments from your computer. Thank you. **********************************************************************
