From sad experience: If the dataset moves, no catalog entry is updated. The next reference to it gets 'data set not found on volume xxxxxx'. A data set managed this way must be marked 'no migrate' to HSM.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Tuesday, August 30, 2016 8:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Elementary dataset alias question On Tue, 30 Aug 2016 10:17:54 -0500, Tom Marchant wrote: >On Tue, 30 Aug 2016 09:09:45 -0400, John Eells wrote: > >>define nonvsam(name('sys1.deleteme.test') volumes(d83xl2) devt(3390)) >>catalog('CATALOG.SVPLEX4.USERCAT') <== This one adds the entry to the >>user catalog my user ID's alias points to. >> >>define alias(name('eells.deleteme.test') relate('sys1.deleteme.test')) >>catalog('CATALOG.SVPLEX4.USERCAT') <== This one creates the data set alias. > >A word of caution. If the real data set is subject to moving to a >different volume, for example because of HSM migrate/recall, the second >catalog entry will not be updated when it is recalled. And of course, >if the data set is on the IPL volume, you would catalog it to ****** or the >appropriate symbol. > Ouch! This negates one main value of cataloguing. Hmmm... If the data set is deleted, do the additional aliases remain catalogued, orphaned? Does SMS play in this game? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
