Terry,
Let's assume for a moment that both MAINT CF1 and MAINT 2CC live on your current sysres volume (call it<old>RES). 1) Copy it to another volume accessible on your current system, 2) use DDR to copy <old>RES to <new>RES, then 3) add two temporary MAINT mdisks on your current system - CCF1 and C2CC, both on <new>RES at same cylinder locations as on <old>RES. 4) Link and access them, update SYSTEM CONFIG and USER DIRECT per my previous append. 5) DETACH the fullpack disk of your currrent SYSRES volume. YOU DON'T WANT TO ACCIDENTALLY OVERWRITE YOUR CURRENT DIRECTORY WITH THE DEFINITIONS OF YOUR NEW SYSTEM!!! 6) ATTACH <new>RES (or DEFINE MDISK cuu 0 END <new>RES) where cuu is the address specified on the DIRECTORY statement (which you should verify specifies <new>RES) 7) ACCESS C2CC Z and run DIRECTXA USER DIRECT Z to write the new directory on <new>RES. 8) Copy all volumes as before, except copy <new>RES instead of <old>RES 9) Relabel all volumes per previous append using ICKDSF CPVOL LABEL 10) IPL new LPAR 11) Scratch <oldsys>'s <new>RES since was only temporary Just a suggestion: make sure copies of DDR MODULE and ICKSADSF MODULE live on MAINT CF1 so you can run them standalone from SALIPL if needed. Saved my bacon more than once! Good luck! Mark Date: Sun, 5 Apr 2009 20:41:36 -0400 From: terry.mar...@cms.hhs.gov Subject: Re: Copying one z/VM to another using DFDSS To: IBMVM@LISTSERV.UARK.EDU Hi Mark, Thanks for the information. The one thing I forgot to mention was that I cannot access the new addresses from the z/VM LPAR that I am copying to. So that is why I needed a way to make the changes before I copied the packs over so that when they were copied to the new the System Config and User Directory files would be reflecting the new system’s addresses. I think the steps you outlined would require that both of the LPARS have access to the new addresses. It is not the case here. What do you think? Thank You, Terry Martin Lockheed Martin - Information Technology z/OS & z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Wheeler Sent: Sunday, April 05, 2009 8:28 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Copying one z/VM to another using DFDSS I neglected to mention that the new USERC DIRECT A must be copied back to the appropriate SYSC-owned mdisk (MAINT 2CC?) as USER DIRECT. Date: Sun, 5 Apr 2009 16:41:01 -0500 From: mwheele...@hotmail.com Subject: Re: Copying one z/VM to another using DFDSS To: IBMVM@LISTSERV.UARK.EDU Terry, I assume you're not using DIRMAINT or VM:Secure, so following deals only with USER DIRECT... >From your current system, 1) copy all the DASD volumes (SYSRES, etc) to your new system's device addresses, then 2) use ICKDSF CPVOL LABEL commands to change to new device addrs to new volsers. 3) Update all volsers in the new SYSTEM CONFIG (you can use DEFINE MDISK to get access to the new MAINT CF1, for example) 4) Make a copy of your USER DIRECT and change the volsers on the DIRECT statement and all MDISK statements. Save as USERC DIRECT A (perhaps). 5) LINK or ATTACH the new sysres volume to your userid using the device address specified on the DIRECT statement 6) Issue DIRECTXA USERC DIRECT A 7) IPL! Best regards, Mark Wheeler http://www.linkedin.com/in/marklwheeler Rediscover Hotmail®: Get e-mail storage that grows with you. Check it out. _________________________________________________________________ Quick access to your favorite MSN content and Windows Live with Internet Explorer 8. http://ie8.msn.com/microsoft/internet-explorer-8/en-us/ie8.aspx?ocid=B037MSN55C0701A
