On Tue, 30 Aug 2016 09:09:45 -0400, John Eells wrote:
>define nonvsam(name('sys1.deleteme.test') volumes(d83xl2) devt(3390))
>catalog('CATALOG.SVPLEX4.USERCAT') <== This one adds the entry to the
>user catalog my user ID's alias points to.
>
>define alias(name('eells.deleteme.test') relate('sys1.deleteme.test'))
>catalog('CATALOG.SVPLEX4.USERCAT') <== This one creates the data set alias.
A word of caution. If the real data set is subject to moving to a different
volume,
for example because of HSM migrate/recall, the second catalog entry will not be
updated when it is recalled. And of course, if the data set is on the IPL
volume,
you would catalog it to ****** or the appropriate symbol.
>Charles Mills wrote:
>>
>> Here's the question. (And like all these things, there is a long story
>> reason why doing things this way seems to make sense.)
I'm curious. Why do you want to do this?
>> SYS1.FOOBAR is a dataset cataloged in the master catalog. It's not "real
>> special" like SYS1.LINKLIB or anything. It's an SMP/E-managed IBM product
>> library. I don't think it is APF-authorized. I think it is linklisted if
>> that makes a difference.
If it is in LNKLST, I see even less reason to do this.
>> JOEBLOW is an ordinary userid.
>>
>> Is it possible to create a catalog entry such that JOEBLOW.MY.FOO.BAR is an
>> alias for SYS1.FOOBAR and batch DD references to JOEBLOW.MY.FOO.BAR will
>> actually allocate SYS1.FOOBAR?
-- Tom Marchant
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
