On 2014-12-10 17:48, Charles Mills wrote: > > Question: Does the use of aliases make sense? Let's say HLQ.BAR is > identical across A, B and C. Should I make one HLQ.BAR.COMMON and > alias it as .A, .B and .C? Or is that overkill for a simple one-person > situation? Should I just make three identical PDSes and not over-complicate > the problem? > > Disk space is not the issue -- these are relatively small datasets. I > guess it just bothers my engineering desire for elegance to have three > identical datasets when I could have three pointers to one dataset. I > guess "not mucking up the maintenance" -- changing one and failing to > change the others > -- is also a possible concern.
I have only had to do this once, (actually in the opposite direction) with a particularly difficult ORACLE migration. I needed to support 2 concurrent versions of ORACLE and avoid massive JCL changes. I defined the original name to be an alias of a "versioned" name for the ORACLE syslibs. In the background, I could manipulate each versioned syslib as needed. At the correct time, the original name was pointed at the "other" version of Oracle and all was transparent. Later, undid this and moved the "versioned" dataset back to the original name and deleted the alias. HTH, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
