Tom Marchant wrote:
<snip>
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.
<snip>
Tom raises two important points.
To widen the aperture on his first one a bit further, it is of course
not only DFSMShsm that can move things around. For example, whoever
maintains the data sets that are aliased this way must always remain
conscious of the additional catalog entries that are perhaps maintained
in different catalogs than the primary entries, and change them in
concert in the correct catalog(s) when and if data sets move between
volumes.
--
John Eells
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
