I remember at one time IBM had a free / shareware tool that could delete bad DSN entries. I used it a couple of times - but it has been years and I can't remember the name or where it is.
I will keep looking. Thanks -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jack Zukt Sent: Wednesday, August 31, 2022 8:04 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IDC3009I & IDC1566I with a weird dsn ATTENTION: This e-mail came from an external source. Do not open attachments or click on links from unknown or unexpected emails. Hi Carmen Thank you for the input. I have tried IDCAMS DELETE but to no avail. As for FDR, you are probably right. It might be something left from a job running FDR that ended abnormally. But considering the number of "lost" entries, some of those jobs must have considered complete even with the errors. Regards, Jack On Wed, 31 Aug 2022 at 13:58, Carmen Vitullo <petevi...@gmail.com> wrote: > Jack, 2 things some to mind, have you tried to use IDCAMS to delete > the entry using NVR (non vsam) file > > DELETE FILE(DD1) - > > 'COMPONENT' NVR > > also I recall, you use FDR to compact volumes, and one volume during > compaction fails it leaves a 'pointer' for the lack of a better term > as an non standard data set name that cannot be deleted by normal > methods, to get rid of the file you need to run the compact job again > to a successful end > > > Carmen > > On 8/31/2022 5:50 AM, Jack Zukt wrote: > > Hi Allan, > > This "thing" has got no description; it is not a NONVSAM nor a VSAM > entry. > > There is no VOLSER associared with it. I tried using IDCAMS DELETE > NONVSAM > > but all I got in return was > > IDC3203I ITEM '.....|.' DOES NOT ADHERE TO RESTRICTIONS. Which is > > not surprising considering that it does have spaces in it. > > > > Regards > > Jack > > > > > > On Tue, 30 Aug 2022 at 21:28, Allan Staller < > > 00000387911dea17-dmarc-requ...@listserv.ua.edu> wrote: > > > >> Classification: Confidential > >> > >> LISTCAT ENT(entryname) ALL > >> Select the component (cluster index) and volume (xxxxxx) > >> > >> Use IDCAMS in batch: > >> //STEP EXEC IDCAMS > >> //SYSPRINT DD * > >> //DD1 DD UNIT=SYSDA,DISP=SHR,VOL=SER=xxxxxx > >> //SYSIN DD * > >> DEL componentname VVR FILE(DD1) > >> /* > >> > >> HTH, > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf > >> Of Jack Zukt > >> Sent: Tuesday, August 30, 2022 9:04 AM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: IDC3009I & IDC1566I with a weird dsn > >> > >> [CAUTION: This Email is from outside the Organization. Unless you > >> trust the sender, Don’t click links or open attachments as it may > >> be a > Phishing > >> email, which can steal your Information and compromise your > >> Computer.] > >> > >> Hi all, > >> > >> Another situation that come up. Is anyone of you familiar with > >> these > >> messages: > >> > >> IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS > >> IGG0CLFF-5 IDC1566I ** .....|. ...........8..........U.......2..... > >> NOT LISTED > >> > >> As far as I can see, there is not one dataset with such a name on > >> any of the available DASD. And yet I have 34 of those messages > >> across 7 user catalogs (and they can be there for a long time) > >> Aside from a RC(04) on > the > >> LISTCAT CAT(), there seems to be no other issue. > >> However, I cannot find a way to get rid of those as the dataset > >> name > does > >> not adhere to restrictions. > >> Any ideas? > >> jack > >> > >> ------------------------------------------------------------------- > >> --- For IBM-MAIN subscribe / signoff / archive access instructions, > >> send > email > >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> ::DISCLAIMER:: > >> ________________________________ > >> The contents of this e-mail and any attachment(s) are confidential > >> and intended for the named recipient(s) only. E-mail transmission > >> is not guaranteed to be secure or error-free as information could > >> be > intercepted, > >> corrupted, lost, destroyed, arrive late or incomplete, or may > >> contain viruses in transmission. The e mail and its contents (with > >> or without referred errors) shall therefore not attach any > >> liability on the > originator > >> or HCL or its affiliates. Views or opinions, if any, presented in > >> this email are solely those of the author and may not necessarily > >> reflect the views or opinions of HCL or its affiliates. Any form of > >> reproduction, dissemination, copying, disclosure, modification, > >> distribution and / or publication of this message without the prior > >> written consent of > authorized > >> representative of HCL is strictly prohibited. If you have received > >> this email in error please delete it and notify the sender immediately. > Before > >> opening any email and/or attachments, please check them for viruses > >> and other defects. > >> ________________________________ > >> > >> ------------------------------------------------------------------- > >> --- 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 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
