Here's the procedure to move existing catalog entries. Might consider a UCAT for just their entries. I've seen examples where they have HLQ1.product.V1R1.*LIB and HLQ1.product.V1R2.*LIB but the user gets just HLQ1.product.*LIB with system variables but I don't remember the details. https://www.ibm.com/docs/en/zos/2.1.0?topic=catalog-splitting-catalogs-moving-entries
On Sat, Mar 26, 2022 at 10:40 PM Rob Schramm <[email protected]> wrote: > > 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 -- 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 [email protected] with the message: INFO IBM-MAIN
