Hi Mark,

Thank you fr the additional input
Regards
Jack

On Wed, 31 Aug 2022 at 17:35, Steely.Mark <[email protected]> wrote:

> This is what I used for the SYSIN:
>
> //SYSIN    DD  *
> CMD=DELBCSR;XXXXXXX.DSNCPY.XXXXX              ;
> /*
> //
> //* NOTE: DSN MUST BE 44 CHARACTERS PADDED WITH BLANKS
>
> For some reason it took me a long time to figure out the DSN format for
> the DELBCSR command.
>
> Warning:  Use at you own risk
>
> Thanks
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of Jack Zukt
> Sent: Wednesday, August 31, 2022 11:25 AM
> To: [email protected]
> 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 Mark,
>
> Thank you for the suggestion.
> There is FIXVVDS on SYS1.LINKLIB with a description on SYS1.SAMPLIB. I am
> going to read and maybe give it a try.
> Regards
> Jack
>
> On Wed, 31 Aug 2022 at 17:01, Steely.Mark <[email protected]>
> wrote:
>
> > Check this link:
> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> > ibm.com%2Fsupport%2Fpages%2Fvvdsfix-unsupported-vsam-utility-used-corr
> > ect-problems-catalogs-and-vvds-entries&amp;data=05%7C01%7CSteely.Mark%
> > 40aaa-texas.com%7C0b4c39d54e974eae13b608da8b6d6e08%7Cd5f618ff295149048
> > f7e999c2dd97ab2%7C0%7C0%7C637975599375288953%7CUnknown%7CTWFpbGZsb3d8e
> > yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C30
> > 00%7C%7C%7C&amp;sdata=AEcV2zpFaJDFTgdOx%2BgQzPAHNOcELTqSiDuxPtJJJLw%3D
> > &amp;reserved=0
> >
> > It talks about VVDS Fix utility - I am not sure if you can download it
> > any more - I have not been able to find a current download site.
> >
> > I have the load module. I might be able to add as an attachment and
> > send in an e-mail.
> >
> > Let me know.
> >
> > Thanks
> >
> >
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List <[email protected]> On
> > Behalf Of Gibney, Dave
> > Sent: Wednesday, August 31, 2022 10:49 AM
> > To: [email protected]
> > 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.
> >
> >
> > 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fur
> > > ld
> > > efense.com%2Fv3%2F__https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fpages%2Fap
> > > ar
> > > %2FO&amp;data=05%7C01%7CSteely.Mark%40aaa-texas.com%7Cc5a2914e21564f
> > > ae
> > > 855608da8b686bc7%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637975
> > > 57
> > > 7843502184%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> > > zI
> > > iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=EYxok8JRgE
> > > 3O
> > > 9XJEbwHA5VupkEsG19M51YqyqODNTWQ%3D&amp;reserved=0
> > > 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
>
> ----------------------------------------------------------------------
> 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

Reply via email to