Thanks Paul, All of the details and suggestions posted on the list are great.
I had most of this down in my Notes Log and really just wanted to get a flavor of how different people are handling this situation. Thanks again. BTW, I'll be sending you a note off list. Please be kind enough to read it and advise. --- On Sat, 9/5/09, Paul, Thomas <thomas.p...@iso.com> wrote: From: Paul, Thomas <thomas.p...@iso.com> Subject: Re: Backup RES Labeling Question To: IBMVM@LISTSERV.UARK.EDU Date: Saturday, September 5, 2009, 10:00 AM Howard, Here is the attachment and how to do this. Please remember to make changes that fits to your environment. Regards Tom _Modifying labels in the SYSTEM CONFIG file _ Modifying labels in the USER DIRECT file _ Changing the labels on the five volumes _ Shutting down your system and restarting it Modifying labels in the SYSTEM CONFIG file Note the first five CP-owned volumes with the QUERY CPOWNED command in Example 4-36. Example 4-36 QUERY CPWONED output ==> q cpowned Slot Vol-ID Rdev Type Status 1 520RES A770 Own Online and attached 2 520SPL A771 Own Online and attached 3 520PAG A772 Own Online and attached 4 520W01 A773 Own Online and attached 5 520W02 A774 Own Online and attached 6 VPA775 A775 Own Online and attached 7 VPA776 A776 Own Online and attached 8 VPA777 A777 Own Online and attached 9 VPA778 A778 Own Online and attached 10 VPA779 A779 Own Online and attached 11 ------ ---- ----- Reserved 12 ------ ---- ----- Reserved ... ==> cprel a ==> link * cf1 cf1 mr ==> acc cf1 f ==> copy system config f = confBKUP = (oldd rep ==> x system config f Issue follow on the command line to reach the CP_Owned volumes ====> /cp_owned /* CP_Owned Volume Statements */ /**********************************************************************/ CP_Owned Slot 1 VM1RES CP_Owned Slot 2 VM1SP1 CP_Owned Slot 3 VM1PG1 CP_Owned Slot 4 VVA771 CP_Owned Slot 5 VVA772 CP_Owned Slot 6 VPA776 CP_Owned Slot 7 VPA778 CP_Owned Slot 8 VPA775 CP_Owned Slot 9 VPA777 ====> file Verify to make sure that there are no syntax errors: ==> acc 193 g ==> cpsyntax system config f CONFIGURATION FILE PROCESSING COMPLETE -- NO ERRORS ENCOUNTERED. Release and detach the F disk, CPACCESS the A disk, and verify, as Example 4-39 shows. Example 4-39 Releasing and detaching the F disk, and verifying the A disk ==> rel f (det DASD 0CF1 DETACHED ==> cpacc * cf1 a CPACCESS request for mode A scheduled. Ready; T=0.01/0.01 09:19:57 HCPZAC6732I CPACCESS request for MAINT's 0CF1 in mode A completed. ==> q cpdisk Label Userid Vdev Mode Stat Vol-ID Rdev Type StartLoc EndLoc MNTCF1 MAINT 0CF1 A R/O 520RES A770 CKD 39 83 MNTCF2 MAINT 0CF2 B R/O 520RES A770 CKD 84 128 MNTCF3 MAINT 0CF3 C R/O 520RES A770 CKD 129 188 You have now changed the labels of the system volumes in the SYSTEM CONFIG file. It is critical that you proceed as your system is now in a state where it will not IPL. 60 IBM z/VM and Linux on IBM System z: Virtualization Cookbook for Red Hat Enterprise Linux 4 Modifying labels in the USER DIRECT file Now modify the labels in the USER DIRECT file. You see many more occurrences of the labels being changed, as Example 4-40 shows. Example 4-40 Modifying labels in USER DIRECT ==> copy user direct c = direwrks = (oldd rep ==> x user direct c ====> Stay on ====> set case m i ====> top ====> ch /510RES/VM1RES/ * * ====> all /510RES/ ====> all Do the previous 3 commands for each volser that needs to be changed. ====> file You have now changed the labels of the system volumes in the USER DIRECT and SYSTEM CONFIG files. It is critical that you proceed with the remaining steps. Changing the labels on the five volumes Change the labels on the five volumes using the CPFMTXA command. You can do this one volume at a time with the CPFMTXA LABEL command. Gain read/write access to the system res volume. link maint 123 123 mr Ready; T=0.01/0.01 13:07:07 q v 123 DASD 0123 3390 510RES R/W 3339 CYL ON DASD 7130 SUBCHANNEL = 000B Ready; T=0.01/0.01 13:08:22 The following command will place the VM1RES label on the volume at virtual address 123. cpfmtxa 123 VM1RES label HCPCCF6209I INVOKING ICKDSF. ICK030E DEFINE INPUT DEVICE: FN FT FM, "CONSOLE", OR "READER" CONSOLE ICK031E DEFINE OUTPUT DEVICE: FN FT FM, "CONSOLE", OR "PRINTER" CONSOLE ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0 TIME: 13 ENTER INPUT COMMAND: CPVOL LABEL UNIT(0123) VOLID(VM1RES) NOVFY ICK00700I DEVICE INFORMATION FOR 0123 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A001B35 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00703I DEVICE IS OPERATED AS A MINIDISK ICK00091I 0123 NED= 2105. .IBM.13.000000014076 ICK091I 0123 NED= 2105. .IBM.13.000000014076 ICK03090I VOLUME SERIAL = 510RES ICK003D REPLY U TO ALTER VOLUME 0123 CONTENTS, ELSE T U ICK03000I CPVOL REPORT FOR 0123 FOLLOWS: VOLUME SERIAL NUMBER IS NOW = VM1RES ICK00001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 13:08:51 11/09/06 This process must be done to each of the system volumes (520pag and 520spl) Now that you have relabeled the system volumes, which are sometimes called clipping the volumes, you can run the DIRECTXA command to update the directory: ==> directxa user z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 2.0 EOJ DIRECTORY UPDATED HCPDIR494I User directory occupies 39 disk pages Ready(00005); T=0.01/0.01 14:30:37 A return code of 5 is expected, because the labels in the USER DIRECT file are different from the spool data in the currently running system. Finally, you are ready to issue a SHUTDOWN command. Shutting down your system and restarting it To test the changes you must shut your system down and then restart it. You cannot do a SHUTDOWN REIPL in this situation because you have to do a FORCE start as follows: ==> shutdown SYSTEM SHUTDOWN STARTED HCPSHU960I System shutdown may be delayed for up to 210 seconds You lose your 3270 session. Perform the following steps to restart the system: 1. Go back to the HMC to IPL your system. 2. Click the LOAD icon in the CPC Recovery menu. 3. Select the Clear radio button. All the other parameters must be correct from the previous IPL. Click OK. 4. Click Yes on the Load Task Confirmation panel. 5. Go back to the Integrated 3270 console. After a few minutes the Standalone Program Loader panel opens. Use the Tab key to traverse to the section IPL Parameters and enter the value cons=sysg. 6. Press the F10 key to continue the IPL of your z/VM system. This takes around three minutes. 7. At the start prompt, you have to specify a FORCE start, again because the spool volume label has changed. Enter the following: ==> force drain 8. Do not change the time of day clock. ==> no 9. When the IPL completes, DISCONNECT from the OPERATOR user ID and log in to MAINT. ==> disc Now your z/VM system volumes must be relabeled. Verify with the QUERY CPOWNED command, as Example 4-42 shows. Example 4-42 Verifying z/VM volumes with QUERY CPOWNED ==> q cpowned Slot Vol-ID Rdev Type Status 1 VM1RES A770 Own Online and attached 2 VM1SP1 A771 Own Online and attached 3 VM1PG1 A772 Own Online and attached 4 VVA773 A773 Own Online and attached 5 VVA774 A774 Own Online and attached 6 VPA775 A775 Own Online and attached 7 VPA776 A776 Own Online and attached 8 VPA777 A777 Own Online and attached 9 VPA778 A778 Own Online and attached 10 VPA779 A779 Own Online and attached 11 ------ ---- ----- Reserved ... In the event that you IPL a system with duplicate system volumes, it is possible that you may have destroyed your saved segments. You can identify this situation when you are unable to IPL CMS. In this case, you have to IPL 190. Important: Do this only if your saved segments have been destroyed. To rebuild saved segments, try the following commands: ==> vmfsetup zvm cms ==> sampnss cms ==> i 190 cl parm savesys cms ==> vmfbld ppf segbld esasegs segblist ( all -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Howard Rifkind Sent: Friday, September 04, 2009 9:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Backup RES Labeling Question Thanks Scott, --- On Fri, 9/4/09, Wandschneider, Scott <scott.wandschnei...@infocrossing.com> wrote: From: Wandschneider, Scott <scott.wandschnei...@infocrossing.com> Subject: Re: Backup RES Labeling Question To: IBMVM@LISTSERV.UARK.EDU Date: Friday, September 4, 2009, 1:11 PM Changing VM VOLSERs Logon as MAINT. Attach nnnRES volume to the base z/VM system. ATTACH rdev TO SYSTEM ç nnnRES Add the following full pack minidisk statements for xxxRES to MAINT on the base system and put the directory online. MDISK F123 3390 000 END nnnRES MW MDISK FCF1 3390 039 120 nnnRES MW READ WRITE MULTIPLE MDISK F2CC 3390 506 005 nnnRES MW READ WRITE MULTIPLE Logoff/Logon to MAINT. Access the new system’s minidisks. ACCESS FCF1 W ACCESS F2CC U Edit the “NEW” directory on the F2CC “U” minidisk, changing all the VOLID's to the new VOLID’s. IBM Default Production Description nnnRES mmxRES SYSRES nnnSPL mmxSP1 Spool Volume 1 nnnPAG mmxPG1 Page Volume 1 nnnW01 mmxW01 Work Volume 1 Where nnn is the base release, i.e. 530 Where mm is the base release, i.e. 53 and x is an identification letter, i.e. “A” ZVMESA5 = “A” Z800ZVM = “B” ODCZVM52 = “C” Edit the “NEW” SYSTEM CONFIG file on the FCF1 “W” minidisk, changing all the VOLID's to the new VOLID’s. Define '123' as 'FFF' and 'F123' as '123' to place the newly modified directory online for the second level VM system. Use QUERY V DASD to verify. DEFINE 123 AS FFF DEFINE F123 AS 123 DIRECTXA user direct u Re-Define the ‘123’ disk. Use QUERY V DASD to verify. DEFINE 123 AS F123 DEFINE FFF AS 123 Attach the remaining new system DASD addresses to MAINT. DETACH rdev FROM SYSTEM ç nnnRES ATTACH rdev TO MAINT ç nnnRES ATTACH rdev TO MAINT ç nnnSPL ATTACH rdev TO MAINT ç nnnPAG ATTACH rdev TO MAINT ç nnnW01 ATTACH rdev TO MAINT ç nnnW02 Change the VOLID's to what they were changed to in the new directory. Execute ICKDSF. REFORMAT UNIT(rdev) VERIFY(nnnRES) VOLID(nnxRES) REFORMAT UNIT(rdev) VERIFY(nnnSPL) VOLID(nnxSP1) REFORMAT UNIT(rdev) VERIFY(nnnPAG) VOLID(nnxPG1) REFORMAT UNIT(rdev) VERIFY(nnnW01) VOLID(nnxW01) REFORMAT UNIT(rdev) VERIFY(nnnW02) VOLID(nnxW02) Detach the volumes from MAINT. DETACH rdev FROM MAINT ç Was nnnRES DETACH rdev FROM MAINT ç Was nnnSPL DETACH rdev FROM MAINT ç Was nnnPAG DETACH rdev FROM MAINT ç Was nnnW01 DETACH rdev FROM MAINT ç Was nnnW02 Vary offline/online the new volumes. IPL the new system. Thank you, Scott From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Howard Rifkind Sent: Friday, September 04, 2009 11:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Backup RES Labeling Question Scott, think you forgot to attach your procedure... And thanks all. --- On Fri, 9/4/09, Wandschneider, Scott <scott.wandschnei...@infocrossing.com> wrote: From: Wandschneider, Scott <scott.wandschnei...@infocrossing.com> Subject: Re: Backup RES Labeling Question To: IBMVM@LISTSERV.UARK.EDU Date: Friday, September 4, 2009, 12:38 PM Here is the procedure I use to change VM VOLSERs after cloning the volumes, maybe you can adapt to your needs. Thank you, Scott From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Howard Rifkind Sent: Friday, September 04, 2009 11:32 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Backup RES Labeling Question Just creating a copy of the sysres volume to use for testing. --- On Fri, 9/4/09, Wandschneider, Scott <scott.wandschnei...@infocrossing.com> wrote: From: Wandschneider, Scott <scott.wandschnei...@infocrossing.com> Subject: Re: Backup RES Labeling Question To: IBMVM@LISTSERV.UARK.EDU Date: Friday, September 4, 2009, 12:29 PM Are you referring to “cloning” a system or just providing a backup of the RES volume? Thank you, Scott From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Howard Rifkind Sent: Friday, September 04, 2009 11:13 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Backup RES Labeling Question Hello all, I had been asked to make a backup copy of the SYSRES volume, volulme id 54GRES, and was provide with a DASD address of 6027 and a new volume id of 54GBRS. I did a CPFMTXA on 6027 with the volume id of 54GBRS and formatted the entire volume as PERM. I then ran DDR and did a COPY ALL and that worked with out any problems. Of course now the volume which was 54GBRS is now 54GRES. Now there are two volumes with the same volume id and the only way to identify which is which is by the DASD address. This seems to me to now present a problem. Should I now go and re label the back up volume to 54GBRS? What is the best way to handle this and how would we go ahead and test the backup SYSRES? Thanks. Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability & Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. This email is intended for the recipient only. If you are not the intended recipient please disregard, and do not use the information for any purpose.
