----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--- Begin Message ---
On Mon, 2010-06-14 at 18:46 -0500, Paul Gilmartin wrote:
> On Mon, 14 Jun 2010 15:44:58 -0700, Gibney, Dave wrote:
> >
> > I've tried to promote fully qualified aliases to have a static name in
> >the JCL and other places while supporting versioning in the actual
> >dataset name.
> > It's been successful with a different set of products/co-worker, but
> >he recently took a job elsewhere. The alias concept seems to be more
> >confusing to the remaining folks. :(
> >
> There's much one could do with SET symbols in JCLLIB INCLUDE
> members. But one immediately wishes for longer set symbol
> names, such as:
>
> // SET ISV1$PAST$LINKLIB='...',
> // ISV1$CURRENT$LINKLIB='...',
> // ISV1$CURRENT$MACLIB='...',
> // ISV1$FUTURE$LINKLIB='...'
> ... etc.
>
> Would file tailoring help?
>
> -- gil
What I suggested was using ALIASes. Real DSN would be
SYS3.product.version.LINKLIB . There would be SYS3.product.PROD.LINKLIB
as an ALIAS to that. SYS3.product.PREV.LINKLIB pointing to the current
or previous version. And SYS3.product.NEW.LINKLIB pointing to either the
current or "test" version of the "product".
Everybody else thought it was stupid. And too much of a bother to
maintain.
--
John McKown
Maranatha! <><
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--- End Message ---
