Changing VM VOLSERs
1. Logon as MAINT. 2. Attach nnnRES volume to the base z/VM system. ATTACH rdev TO SYSTEM ç nnnRES 3. 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 4. Logoff/Logon to MAINT. 5. Access the new system’s minidisks. ACCESS FCF1 W ACCESS F2CC U 6. 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” 7. Edit the “NEW” SYSTEM CONFIG file on the FCF1 “W” minidisk, changing all the VOLID's to the new VOLID’s. 8. 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 9. Re-Define the ‘123’ disk. Use QUERY V DASD to verify. DEFINE 123 AS F123 DEFINE FFF AS 123 10. 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 11. 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) 12. 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 13. Vary offline/online the new volumes. 14. 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. 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.
