I have thought about SYMBOLICRELATE several times in the past and always
came up with the same conclusion.
More trouble for the SYSPROG to maintain than it saves in "clarity" for
your manager. The major drawback is that
each SYMBOLICRELATE alias must be updated (manually) whenever the
underlying object changes.
Check the "Setting Up A SYSPLEX" Redbook(?) for tips on USS. The VERSION
parameter in specific. The concept of release dependent code is built
in.
There is some additional stuff in the Unix System Services planning
manual.
HTH,
<snip>
I'm just curious about something. Does anybody use SYMBOLICREATE to
create aliases so that the actual DSN can automatically change based on
a static system symbol? I'm thinking about things such as version
numbers or z/OS &SYSNAME. Does anybody even have system relative DSNs?
I'm thinking perhaps like SYS2.&SYSNAME..PARMLIB with an alias of
SYS2.SYSTEM.PARMLIB so that a job can simply refer to
SYS2.SYSTEM.PARMLIB and get the correct, system-specific, PARMLIB. I'm
trying to determine if it is actually useful. My manager likes for
product libraries to have the release/maintenance as a node in the DSN.
But this means that we need to make JCL changes when we upgrade. Or we
need to put the executable libraries in the LNKLST. We currently do the
latter, but I don't really care for it for "low use" products. But is it
better to create a normal ALIAS without the maintenance level and simply
reDEFINE the alias when I upgrade? Rather than change the IEASYMnn
member of PARMLIB. Or just do it like we do now and require JCL changes
so that the JCL itself documents which version/maintenance level is
desired?
This is coming up, in my mind only so far, because I plan to use UNIX
sysplex sharing and use something similar. I plan to have a
system-specific version of then /usr/local subdirectory. In order to
simplify things, I'll use a symbolic link with $SYSSYMR like:
cd /usr
mkdir SY1-local
mkdir SY2-local
ln -s '$SYSSYMR/&SYSNAME.-local' system-local
and then in /etc/profile, have:
export PATH=${PATH}:/usr/system-local/bin:/usr/local/bin
so that a system local version of a program will override the "global"
/usr/local version.
</snip>
----------------------------------------------------------------------
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
