Re: Orphaned ICF catalog in the VVDS
Norbert, you are the man! A very nifty piece of code. Don't know why i missed your reply first time round. I carried out the missing part of the solution when i got in this morning, (out of time last night) of recataloging the vvds entry in the re-created, missing catalog, then ran the del nscr for the vvds against said catalog. Diagnosis is now clean! Just deleted the catalog to keep it all tidy. regards, Dave *** On Thu, 18 Jul 2013 13:44:50 -0400, Rouse, Willie wrote: I guess I don't understand: put a corresponding entry into the dummy bcs Recatalog the VVDS into the dummy bcs. I posted a complete job to the list on 5 July: http://www.mail-archive.com/ibm-main@listserv.ua.edu/msg15771.html 1. Create a new catalog with the old non-existent catalog name 2. Recatalog the VVDS 3. Delete (NOSCRATCH) the VVDS 4. Delete the catalog //* //S1 EXEC PGM=IDCAMS //* //SYSPRINT DD SYSOUT=* //VVDS DD DIS=SHR,DSN=SYS1.VVDS.Vvol001, // VOL=SER=vol001,UNIT=SYSDA //SYSIN DD * DIAG VVDS IFILE(VVDS) DEF UCAT(NAME(old.catname) - VOL(vol002) - CYL(1 1) - FSPC (0 0)) - DATA(CISZ(4096)) - INDEX(CISZ(4096)) DEF CL(NAME(SYS1.VVDS.Vvol001) - VOL(vol001) - NONINDEXED - RECATALOG) - CAT(old.catname) DEL SYS1.VVDS.Vvol001 - FILE(vol001) - NOSCRATCH- CAT(old.catname) DEL old.catname UCAT DIAG VVDS IFILE(VVDS) /* // -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
Willie, hello, Can you post the relevent snippet from your diagnose output so we can see exactly what's what. Thanks Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
First of all, thanks for the interest. Snippet: IDC11367I THE FOLLOWING VVDS REFERENCED CATALOGS WERE NOT ENCOUNTERED: CATALOG.MVSICF1.VMVSE18 CATALOG.MVSICFM.VMVSOD1 CATALOG.MVSICFM.VMVSE1B CATALOG.MVSICF1.VMVS139 CATALOG.MVSICF1.PROGPROD.VOS1000 CATALOG.MVSICF1.PROGTEST.VOS1000 CATALOG.MVSICF1.TEMPCATQ CATALOG.MVSICFM.VIP1080 CATALOG.MVSICF1.VIP1082 CATALOG.MVSICF1.TRASH.VOS1000 CATALOG.MVSICF1.SYSP.VOS1000 CATALOG.CNMICF1.VOS1060 IDCAMS SYSTEM SERVICES TIME: CATALOG.MVSICF1.NETVIEW.VOS1000 CATALOG.MVSICF1.EMC.VOS1000 CATALOG.MVSICF1.IODF.VOS1000 CATALOG.MVSICF1.TEST1.VOS1000 IDC21363I THE FOLLOWING ENTRIES HAD ERRORS: VPS.FLOR.VPSDCKPT.DATA (Z) - REASON CODE: 42 VPS.FLOR.VPSDCKPT.INDEX (Z) - REASON CODE: 42 VPS.FLOR.VPSDTRAK.DATA (Z) - REASON CODE: 42 VPS.FLOR.VPSDTRAK.INDEX (Z) - REASON CODE: 42 IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8 The VSAM clusters have been corrected, but I still have those non-existing catalogs. Respectfully, Willie C. Rouse Senior Mainframe Consultant Prince George's County, Maryland Office of Information Technology 9201 Basil Court/ Room B8 Largo, MD 20774 Voice: 301-883-7189 Fax: 301-883-3790 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Devine Sent: Thursday, July 18, 2013 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Orphaned ICF catalog in the VVDS Willie, hello, Can you post the relevent snippet from your diagnose output so we can see exactly what's what. Thanks Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
I don't think that IBM has a facility to clean up these types of records in a VVDS. Dino Software's T-Rex does. On Thu, Jul 18, 2013 at 7:44 AM, Rouse, Willie wro...@co.pg.md.us wrote: First of all, thanks for the interest. Snippet: IDC11367I THE FOLLOWING VVDS REFERENCED CATALOGS WERE NOT ENCOUNTERED: CATALOG.MVSICF1.VMVSE18 CATALOG.MVSICFM.VMVSOD1 CATALOG.MVSICFM.VMVSE1B CATALOG.MVSICF1.VMVS139 CATALOG.MVSICF1.PROGPROD.VOS1000 CATALOG.MVSICF1.PROGTEST.VOS1000 CATALOG.MVSICF1.TEMPCATQ CATALOG.MVSICFM.VIP1080 CATALOG.MVSICF1.VIP1082 CATALOG.MVSICF1.TRASH.VOS1000 CATALOG.MVSICF1.SYSP.VOS1000 CATALOG.CNMICF1.VOS1060 IDCAMS SYSTEM SERVICES TIME: CATALOG.MVSICF1.NETVIEW.VOS1000 CATALOG.MVSICF1.EMC.VOS1000 CATALOG.MVSICF1.IODF.VOS1000 CATALOG.MVSICF1.TEST1.VOS1000 IDC21363I THE FOLLOWING ENTRIES HAD ERRORS: VPS.FLOR.VPSDCKPT.DATA (Z) - REASON CODE: 42 VPS.FLOR.VPSDCKPT.INDEX (Z) - REASON CODE: 42 VPS.FLOR.VPSDTRAK.DATA (Z) - REASON CODE: 42 VPS.FLOR.VPSDTRAK.INDEX (Z) - REASON CODE: 42 IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8 The VSAM clusters have been corrected, but I still have those non-existing catalogs. Respectfully, Willie C. Rouse Senior Mainframe Consultant Prince George's County, Maryland Office of Information Technology 9201 Basil Court/ Room B8 Largo, MD 20774 Voice: 301-883-7189 Fax: 301-883-3790 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Devine Sent: Thursday, July 18, 2013 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Orphaned ICF catalog in the VVDS Willie, hello, Can you post the relevent snippet from your diagnose output so we can see exactly what's what. Thanks Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
The cheapest solution is to define the required ucat. Issue a delete command for that ucat against the VVDS, and then delete the recently defined ucat. A PITA granted, but it workds. HTH, snip I don't think that IBM has a facility to clean up these types of records in a VVDS. Dino Software's T-Rex does. First of all, thanks for the interest. Snippet: IDC11367I THE FOLLOWING VVDS REFERENCED CATALOGS WERE NOT ENCOUNTERED: CATALOG.MVSICF1.VMVSE18 snippage /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
I used to do things like that. Then I decided that it wasn't worth the bother. I guess as I get older, I am not as concerned about keeping things shiny like new. On Thu, Jul 18, 2013 at 8:27 AM, Staller, Allan allan.stal...@kbmg.comwrote: The cheapest solution is to define the required ucat. Issue a delete command for that ucat against the VVDS, and then delete the recently defined ucat. A PITA granted, but it workds. HTH, snip I don't think that IBM has a facility to clean up these types of records in a VVDS. Dino Software's T-Rex does. First of all, thanks for the interest. Snippet: IDC11367I THE FOLLOWING VVDS REFERENCED CATALOGS WERE NOT ENCOUNTERED: CATALOG.MVSICF1.VMVSE18 snippage /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
Hi Willie, I believe that Allan has hit the nail on the head for the solution, but i think you may also have to put a corresponding entry into the dummy bcs so that the delete nscr will match up on both sides. Just tried it on a pack on our sysprog lpar in the same situation, recreated the lost catalog and got an idc3012i on the delete nscr for the sys1.vvds.vx. An inelegant solution but quick and easy would be to disnew the volume, empty it out (hsm migrate or dfdss copy etc.) then delete the vvds and define a nice new empty one, then enable the volume back to sms. Sod's law will probably have it that there's a permanently allocated dataset on the volume to put the kibosh on that idea! If you fancy being a guinea pig, theres VVDSFIX an unsupported IBM program you can download. You can read about and download this tool from this URL: http://www.ibm.com/support/docview.wss?uid=isg3S1000618 Was on a share presentation a few years back. Looks like it could be vaiable. Never used it, but i'm sure there are people around who have. Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
Dave, I guess I don't understand: put a corresponding entry into the dummy bcs I created and empty ucat with orphan name. Then tried to delete it with the following JCL //VVR EXEC PGM=IDCAMS,REGION=512K //SYSPRINT DD SYSOUT=* //DD1 DD DSN=SYS1.VVDS.VPP1013,DISP=OLD //SYSIN DD * DELETE CATALOG.MVSICFM.VIP1080 NSCR FILE(DD1) /* I get: IDCAMS SYSTEM SERVICES TIME: DELETE CATALOG.MVSICFM.VIP1080 NSCR FILE(DD1) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFK-18 IDC0551I ** ENTRY CATALOG.MVSICFM.VIP1080 NOT DELETED IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 Respectfully, Willie C. Rouse Senior Mainframe Consultant Prince George's County, Maryland Office of Information Technology 9201 Basil Court/ Room B8 Largo, MD 20774 Voice: 301-883-7189 Fax: 301-883-3790 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Devine Sent: Thursday, July 18, 2013 12:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Orphaned ICF catalog in the VVDS Hi Willie, I believe that Allan has hit the nail on the head for the solution, but i think you may also have to put a corresponding entry into the dummy bcs so that the delete nscr will match up on both sides. Just tried it on a pack on our sysprog lpar in the same situation, recreated the lost catalog and got an idc3012i on the delete nscr for the sys1.vvds.vx. An inelegant solution but quick and easy would be to disnew the volume, empty it out (hsm migrate or dfdss copy etc.) then delete the vvds and define a nice new empty one, then enable the volume back to sms. Sod's law will probably have it that there's a permanently allocated dataset on the volume to put the kibosh on that idea! If you fancy being a guinea pig, theres VVDSFIX an unsupported IBM program you can download. You can read about and download this tool from this URL: http://www.ibm.com/support/docview.wss?uid=isg3S1000618 Was on a share presentation a few years back. Looks like it could be vaiable. Never used it, but i'm sure there are people around who have. Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
On Thu, 18 Jul 2013 13:44:50 -0400, Rouse, Willie wrote: I guess I don't understand: put a corresponding entry into the dummy bcs Recatalog the VVDS into the dummy bcs. I posted a complete job to the list on 5 July: http://www.mail-archive.com/ibm-main@listserv.ua.edu/msg15771.html 1. Create a new catalog with the old non-existent catalog name 2. Recatalog the VVDS 3. Delete (NOSCRATCH) the VVDS 4. Delete the catalog //* //S1 EXEC PGM=IDCAMS //* //SYSPRINT DD SYSOUT=* //VVDS DD DIS=SHR,DSN=SYS1.VVDS.Vvol001, // VOL=SER=vol001,UNIT=SYSDA //SYSIN DD * DIAG VVDS IFILE(VVDS) DEF UCAT(NAME(old.catname) - VOL(vol002) - CYL(1 1) - FSPC (0 0)) - DATA(CISZ(4096)) - INDEX(CISZ(4096)) DEF CL(NAME(SYS1.VVDS.Vvol001) - VOL(vol001) - NONINDEXED - RECATALOG) - CAT(old.catname) DEL SYS1.VVDS.Vvol001 - FILE(vol001) - NOSCRATCH- CAT(old.catname) DEL old.catname UCAT DIAG VVDS IFILE(VVDS) /* // Norbert Friemel -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [SPAM] Re: Orphaned ICF catalog in the VVDS
Since this is an orphaned catalog try DELETE ... cat.name VVR and then follow it w/the same delete except change the 'VVR' to an 'NVR'. Kind Regards Jim -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rouse, Willie Sent: Thursday, July 18, 2013 12:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [SPAM] Re: Orphaned ICF catalog in the VVDS Dave, I guess I don't understand: put a corresponding entry into the dummy bcs I created and empty ucat with orphan name. Then tried to delete it with the following JCL //VVR EXEC PGM=IDCAMS,REGION=512K //SYSPRINT DD SYSOUT=* //DD1 DD DSN=SYS1.VVDS.VPP1013,DISP=OLD //SYSIN DD * DELETE CATALOG.MVSICFM.VIP1080 NSCR FILE(DD1) /* I get: IDCAMS SYSTEM SERVICES TIME: DELETE CATALOG.MVSICFM.VIP1080 NSCR FILE(DD1) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFK-18 IDC0551I ** ENTRY CATALOG.MVSICFM.VIP1080 NOT DELETED IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 Respectfully, Willie C. Rouse Senior Mainframe Consultant Prince George's County, Maryland Office of Information Technology 9201 Basil Court/ Room B8 Largo, MD 20774 Voice: 301-883-7189 Fax: 301-883-3790 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Devine Sent: Thursday, July 18, 2013 12:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Orphaned ICF catalog in the VVDS Hi Willie, I believe that Allan has hit the nail on the head for the solution, but i think you may also have to put a corresponding entry into the dummy bcs so that the delete nscr will match up on both sides. Just tried it on a pack on our sysprog lpar in the same situation, recreated the lost catalog and got an idc3012i on the delete nscr for the sys1.vvds.vx. An inelegant solution but quick and easy would be to disnew the volume, empty it out (hsm migrate or dfdss copy etc.) then delete the vvds and define a nice new empty one, then enable the volume back to sms. Sod's law will probably have it that there's a permanently allocated dataset on the volume to put the kibosh on that idea! If you fancy being a guinea pig, theres VVDSFIX an unsupported IBM program you can download. You can read about and download this tool from this URL: http://www.ibm.com/support/docview.wss?uid=isg3S1000618 Was on a share presentation a few years back. Looks like it could be vaiable. Never used it, but i'm sure there are people around who have. Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
I have run an IDCAMS diagnose on a volume to find non-existent catalog entries . I tried DELETE VVR/NVR/TRUENAME to no avail. How can I get rid of the stranded catalog references in the VVDS? Respectfully, Willie C. Rouse I've used this in the past. MAL705 is a volser. Can't remember anymore if the CATALOG.FHMWPLEX.UCAT actually existed when I ran the job or not. I also couldn't begin to tell you what OS level we were at when I used it. Whatever you do, DON'T forget the NOSCRATCH. I'd recommend setting up a test case to run against before doing it on a live volume. ddk //* //* DELETE PTR FROM VVDS BACK TO A CATALOG //* //STEP01 EXEC PGM=IDCAMS //MAL705 DD DSN=SYS1.VVDS.VMAL705,VOL=SER=MAL705, //DISP=SHR,UNIT=SYSALLDA //SYSPRINT DD SYSOUT=* //SYSINDD * DELETE SYS1.VVDS.VMAL705 CL NOSCRATCH FILE(MAL705) - CAT(CATALOG.FHMWPLEX.UCAT) This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
W dniu 2013-07-04 17:36, Rouse, Willie pisze: I have run an IDCAMS diagnose on a volume to find non-existent catalog entries . I tried DELETE VVR/NVR/TRUENAME to no avail. How can I get rid of the stranded catalog references in the VVDS? AFAIR you have the following choices: - just ignore it and sleep well - use commercial VSAM utilities - re-init whole volume Of course first option is recommended :-) -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Orphaned ICF catalog in the VVDS
On Thu, 4 Jul 2013 11:36:21 -0400, Rouse, Willie wrote: I have run an IDCAMS diagnose on a volume to find non-existent catalog entries . I tried DELETE VVR/NVR/TRUENAME to no avail. How can I get rid of the stranded catalog references in the VVDS? 1. Create a new catalog with the old non-existent catalog name 2. Recatalog the VVDS 3. Delete (NOSCRATCH) the VVDS 4. Delete the catalog //* //S1 EXEC PGM=IDCAMS //* //SYSPRINT DD SYSOUT=* //VVDS DD DIS=SHR,DSN=SYS1.VVDS.Vvol001, // VOL=SER=vol001,UNIT=SYSDA //SYSIN DD * DIAG VVDS IFILE(VVDS) DEF UCAT(NAME(old.catname) - VOL(vol002) - CYL(1 1) - FSPC (0 0)) - DATA(CISZ(4096)) - INDEX(CISZ(4096)) DEF CL(NAME(SYS1.VVDS.Vvol001) - VOL(vol001) - NONINDEXED - RECATALOG) - CAT(old.catname) DEL SYS1.VVDS.Vvol001 - FILE(vol001) - NOSCRATCH- CAT(old.catname) DEL old.catname UCAT DIAG VVDS IFILE(VVDS) /* // Norbert Friemel -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Orphaned ICF catalog in the VVDS
I have run an IDCAMS diagnose on a volume to find non-existent catalog entries . I tried DELETE VVR/NVR/TRUENAME to no avail. How can I get rid of the stranded catalog references in the VVDS? Respectfully, Willie C. Rouse Senior Mainframe Consultant Prince George's County, Maryland Office of Information Technology 9201 Basil Court/ Room B8 Largo, MD 20774 Voice: 301-883-7189 Fax: 301-883-3790 This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
