> Sorry if these question seem stupid but there are days working with VM that I feel just that.
Nope, the question is not by any means "stupid". You have reached what is IMHO, the very most difficult part of z/VM: migration of an existing system to a new release. In general, the process is very tedious and open to simple, but disastrous mistakes. You want to use the newly loaded and maintained MDISKs, SFS directories, and SDF's (System Data Files) that IBM supplied on the new system. But you also want to maintain your customized configuration files (e.g. SYSTEM CONFIG, TCPIP DATA, and myriad others), and old SPOOL files. You also want to use, untouched, other non-IBM directory entries such as those for CMS users, local service machines (be they CMS-based or Linux-based), and non-IBM ISV products. ESM's (External Security Managers) make that process a bit more difficult than using a flat "USERID DIRECT" file. With a flat "USER DIRECT" file you can copy the newly updated IBM entries into a new "MERGED DIRECT" file, then copy the non-IBM entries to the end of that "MERGED DIRECT" file, validate everything ... go from there, eventually renaming MERGED DIRECT to USER DIRECT once everything works. But the "go from there" part is what experienced z/VM sysprogs have spent decades learning on their own, and from members of this list (and from VMSHARE before that). Carefully study the "z/VM Migration Guide". It has many of the processes required. But it does not cover 100% of the pain. We're starting a process of leaving all of IBM's distributed MDISKs on one 3390-9 sysres DASD. When we need to change anything (e.g. those TCPIP files on the TCPMAINT 198 disk) on one of those MDISKs after the install, we'll change that virtual address to begin with D (e.g. from 2C2 to D2C2 as a sign that it is the "Distributed" MDISK) and DDR it to a new MDISK on a local sysres at the original MDISK address (e.g. 2C2). When preparing the next migration, any MDISKs on the local sysres will be carefully examined for changed files. It should make identifying those changed files a lot easier next time. We're about to migrate one system to a fully maintained z/VM 5.4.0 next week. The best advice I can give you is to have hardcopy USER DIRECT files from both systems, and keep the syntax of CP DEFINE MDISK handy. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "MacIntyre, Cory" <cory.macint...@navistar.com> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 04/14/2009 09:19 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject VM 5.4 now what? I have install 5.4 and IPL?d it as a second level system and everything looks good. Now what? I?ve looked for a book or documentation for migrating it to replace the first level machine but I am coming up empty. Can someone point me to a migration guide or procedure so that I don?t do something stupid and wipe out profiles and such. Do I just copy the res volume up to the alt volume? Are there profiles that I have to copy over? Sorry if these question seem stupid but there are days working with VM that I feel just that. Novice is as novice does, which can be dangerous. Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
