Shmuel Metz (Seymour J.) wrote:
In <[EMAIL PROTECTED]>, on 04/13/2008
at 12:00 AM, Edward Jaffe <[EMAIL PROTECTED]> said:
I don't see nearly as many configurations as a busy consultant like
Mark, But, I have noticed with our customers that the LLQ of
SMP/E-maintained, MVS "classic" data sets seems to always mirror the
DDDEF name in target zone.
Otherwise JCLIN wouldn't work.
Actually, JCLIN works no matter what the data set LLQ is. When you code
JCLIN, you specify the DDDEF (or DD) names *as* LLQs. You never specify
any *real* LLQs.
This observation led to the following idea, which I had previously
advanced only to a select few through verbal conversation:
Are you aware of extended indirect cataloging? If not, read up on
SYMBOLICRELATE.
I'm familiar with indirect cataloging -- substituting a system symbol
for the volume name. (We recommend this as the best way to support large
configurations with multiple operating systems and/or product releases.)
SYMBOLICRELATE is an entirely different concept. It is called _extended
alias_ support and allows you to refer to one data set using an
alternate name. I agree this appears to be a good way to achieve the
desired objective using existing operating system facilities.
However, when I experimented with this a while back, I found that it
worked as expected only when the HLQs of the base name and alias were
the same -- or more precisely -- expected to be in the same catalog.
I created a file called 'MYUID.BASE' and used SYMBOLICRELATE to create
'SYS1.ALIAS.OF.BASE'. In my environment, data sets starting with MYUID
are cataloged in a user catalog. Data sets starting with SYS1 are
cataloged in the master catalog. Try as I might, I could not figure out
how to get the system to see 'SYS1.ALIAS.OF.BASE' as an alias of
'MYUID.BASE'. (Perhaps I overlooked something.)
The above restriction should not be important in most if not all system
data set cases. Indeed, the example of SYS1.SBLSxxx vs
SYS1.IPCS.SBLSxxxx is a classic example of where extended aliases would
be applicable. Seems like ServerPac could distribute a procedure/program
to create/issue the appropriate DEFINE ALIAS statements for any data
sets whose HLQs were changed from the delivered defaults.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
