I believe they are the best shot at fixing an issue like you describe. Since the garbage is in the usercat, FIXVVDS tools aren't likely helpful.
You other possibility would be to define a new usercat and REPRO MERGECAT all the good entries to the new usercat. > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Jack Zukt > Sent: Wednesday, August 31, 2022 9:26 AM > To: [email protected] > Subject: Re: IDC3009I & IDC1566I with a weird dsn > > [EXTERNAL EMAIL] > > Hi Dave, > I do not think that I will get the go ahead for that, even it would be > worth a try. > Thank you anyway > Regards, > Jack > > On Wed, 31 Aug 2022 at 16:49, Gibney, Dave < > [email protected]> wrote: > > > Try a free trial of one of the Catalog utility addons. Rocket has the > > Mainstar product. Dinosoft has one. > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List <[email protected]> > On > > > Behalf Of Jack Zukt > > > Sent: Wednesday, August 31, 2022 3:42 AM > > > To: [email protected] > > > Subject: Re: IDC3009I & IDC1566I with a weird dsn > > > > > > [EXTERNAL EMAIL] > > > > > > Hi Joe, > > > > > > Thank you for you input. I had seen that.We are running 2.4 in which > > that > > > APAR PTF (UJ00743) has already been SUP (UJ02056) > > > I have 34 pairs of those messages for 7 usercats, on a job that lists 66 > > > usercats. I think that if this was a bug t would affect all the listcats. > > > I do not know how these entries got there. Probably some utility that did > > > not end as expected. But as the "dataset name" does not adhere to MVS > > > rules, I cannot find a way to get ride of them. > > > Regards > > > Jack > > > > > > > > > On Tue, 30 Aug 2022 at 17:36, Joe Monk <[email protected]> wrote: > > > > > > > Might be this: > > > > https://urldefense.com/v3/__https://www.ibm.com/support/pages/apar/O > > > > A57619__;!!JmPEgBY0HMszNaDT!qbrh2jxLqNZygDoVJ62dAkhZOvSQxuhv78u > > > bqh78z7GtnLWv1yIQyvd8gcrIKNPkHzKfBPotP9zFHQ$ > > > > > > > > Users of CSI and LISTCAT Level may receive inconsistent errors > > > > on entries that have no problem otherwise due to uninitialized > > > > workarea data. > > > > > > > > > > > > Joe > > > > > > > > On Tue, Aug 30, 2022 at 9:04 AM Jack Zukt <[email protected]> wrote: > > > > > > > > > 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 [email protected] with the message: INFO IBM- > > > MAIN > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to [email protected] with the message: INFO IBM- > MAIN > > > > > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM- > MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
