I understood exactly what you were asking for, and I explained why I expected that IBM would not be receptive to an RFE. Back in the CVOL era there was somewhat of an analogy between index levels and Unix directories, but things are different with VSAM catalog. The whole inode thing doesn't exist for classic datasets.
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Rob Schramm <[email protected]> Sent: Monday, March 28, 2022 10:36 AM To: [email protected] Subject: Re: IDCAMS ALIAS vs a symbolic link? 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 <[email protected]> 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 > https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3&data=04%7C01%7Csmetz3%40gmu.edu%7C8f8a302678e94cf5d5a608da10c878f5%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637840750468953897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3pHni4EBIoTJb0HbBcIofwnFZrJKfXkSg9GKdIaleJI%3D&reserved=0 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf > of Rob Schramm [[email protected]] > Sent: Saturday, March 26, 2022 6:40 PM > To: [email protected] > 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 [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
