Hi, We finally were able to remove the bad with the help of TREX. We were able to list the GDG GAT entries with TREX. After sending them the listings, they created a Zap for us to delete the entry.
I executed the zap and was able to create the entry the right way, it rolled right in. :) This was something new to me. I guess I didn't know that when creating a GDG entry that the system rolled it in first and then catalogs it. Also didn't know about GAT entries. Every day you learn something new. :) Thanks everybody for your input. Judith Nelson | Senior Systems Programmer Sammons® Financial Group Member Companies One Sammons Plaza | Sioux Falls, SD 57193 Phone: (605) 373-2321 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Burrell, Todd Sent: Saturday, July 7, 2018 8:59 AM To: [email protected] Subject: Re: [External] Re: remove bad GDG entry from GDG base Have you tried DELETE dsn NSCR or just putting a U beside the entry in an ISPF 3.4 listing? -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Nelson, Judith Sent: Thursday, July 05, 2018 5:59 PM To: [email protected] Subject: Re: [External] Re: remove bad GDG entry from GDG base We tried. :( DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 FILE(VOL2) NVR IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-92 IDC0551I ** ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT DELETED IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 Judith Nelson | Senior Systems Programmer Sammons® Financial Group Member Companies One Sammons Plaza | Sioux Falls, SD 57193 Phone: (605) 373-2321 [email protected]<mailto:[email protected]> -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Marchant Sent: Thursday, July 5, 2018 10:05 AM To: [email protected] Subject: [External] Re: remove bad GDG entry from GDG base On Thu, 5 Jul 2018 09:27:07 -0500, Brad Wissink wrote: >We need to remove a GDG entry from a GDG base, but the catalog entry >doesn't exist. What happened was that during the creation of the GDG >(PTP.DP.TRMS.ARCH999.X3.G0308V00) the user catalog filled up and could >not extend. I suspect that the NVR was created in the VVDS. I would try DELETE NVR, followed by DEFINE. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
