Bruce, unforunally VSAM doesn't support this and zFS use VSAM. We use ALIAS with SYMBOLICRELATE very often and works just fine as it did for you. HFS supports ALIAS with SYMBOLICRELATE.
Roland -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Hewson Sent: Saturday, April 21, 2007 8:14 AM To: [email protected] Subject: Re: Batch JCL, System Symbols, and Symbolic Aliases Hello Gil, responses below: On Fri, 20 Apr 2007 10:09:19 -0600, Paul Gilmartin <[EMAIL PROTECTED]> wrote: >I know, this has been belabored tediously here, but this may be a new >wrinkle. I believe: > >o Symbolic aliases in catalogs are resolved by substituting values > of system symbols for their names. This occurs at Catalog reference time. For batch JCL this occurs at ALLOCATION time. > >o System symbols are not available to batch JCL. Agreed! IBM documented restriction. > >o So, may I conclude that symbolic DSNAME aliases must not be employed > in batch JCL? > Incorrect. SYMBOLICRELATE aliases are the perfect method to make use of System Symbols in batch jobs. >-- gil >-- >StorageTek >INFORMATION made POWERFUL Whereas an ALIAS using RELATE can only be created when the target dataset catalog entry exists, the ALIAS with SYMBOLICRELATE will always be created. I assume this difference in code path is the reason they chose to use a new keyword. I haven't tested SYMBOLICRELATE alias entries with date or time variables. But I use them all the time to improve our multi-stack, multi-lpar TCP environment, especially the SYSTCPD dataset name. e.g. ALIAS --------- SYS1.TCPIP.TCPDATA IN-CAT --- XXXXXXXXXXX HISTORY RELEASE----------------2 ASSOCIATIONS SYMBOLIC-SYS1.TCPIP.&SYSNAME..TCPDATA RESOLVED-SYS1.TCPIP.SYSA.TCPDATA ---------------------------------------------------------------------- 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
