On Tue, 30 Aug 2016 10:17:54 -0500, Tom Marchant wrote:
>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.
>
Ouch! This negates one main value of cataloguing.
Hmmm... If the data set is deleted, do the additional aliases
remain catalogued, orphaned? Does SMS play in this game?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
