I wasn't actually talking about using a symbol (as in system symbol)... but referring to the unix command create symbolic link. ln -s [OPTIONS] FILE LINK
and that is why I was proposing a SYMLINK. but I am not tied to the name if it causes confusion. ALIASLINK works.. or something like it. I am much more interested in the underlying functionality and creating something useful for helping sysprogs and other manage catalogs. Rob On Sun, Mar 27, 2022 at 8:43 AM Seymour J Metz <sme...@gmu.edu> wrote: > I would expect IBM to tell you to use SYMBOLICRELATE. Index levels in > dsnames are not, in general, catalog names, and that makes the analogy with > Unix paths a bit sketchy. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Rob Schramm [rob.schr...@gmail.com] > Sent: Saturday, March 26, 2022 6:40 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: IDCAMS ALIAS vs a symbolic link? > > All, > Has anyone considered how the current ALIAS restrictions are a bit > limiting? And that something more like a symbolic link (USS and for those > that object z/Unix) would be helpful? > > In this example we have a ISV product that has JCL far flung and we want to > change the HLQ and move it to another catalog... but put it in without > disrupting things. > > usercat1 has the old data sets - SYSUC1.some.product > usercat2 has the new data sets - SYSUC2.some.new.product > > such that SYSUC1.some.product gets renamed to SYSUC1.some.product.old and > we create a symbolic link in usercat1 actually points to the data sets in > usercat2. > > It just seems like the ALIAS system is quite limited when we consider that > a symbolic link is a bit more flexible. > > DEF SYMLINK(NAME(SYSUC1.SOME.PRODUCT) REL(SYSUC2.SOME.NEW.PRODUCT) ) > > Let me know what you think. > > Rob Schramm > > ---------------------------------------------------------------------- > 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