As I recall, in doing tests, we could catalog an MVS "bad" name that was a good name for DOS.
So, back when I was doing NDM/Connect:Direct, I ran some tests to validate the handling (because someone managed to set up a bad DSN). I knew about this stuff because I used to make a living off of DOS* to MVS* migrations. And the last time I did one was with z/OS 1.1 and I think we did have a tape that got cataloged with a "bad" MVS name.' This stuff was documented at one time because of sharing disk volumes with DOS. Regards, Steve Thompson --- mike.a.sch...@gmail.com wrote: From: Mike Schwab <mike.a.sch...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] Invalid names in Catalog Date: Mon, 19 Jul 2021 13:20:35 -0500 I think quoted DSNs get into a VTOC but not the catalog. On Mon, Jul 19, 2021 at 11:17 AM Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Mon, 19 Jul 2021 12:08:39 -0400, Steve Thompson wrote: > > >DSN=‘..=......................’,disp=(OLD,DELETE.... etc. > > > Ah! smartass quotes! > > >This is how you get rid of DOS file names that get cataloged from the old > >days. > > > I believe that JCL forbids any use of catalog if DSN is quoted, regardless of > DSNCHECK. > (Silly rule except how would convererr know?) > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- 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
