On Jan 28, 2016, at 8:51 AM, Walt Farrell wrote:
On Wed, 27 Jan 2016 18:40:45 -0600, Paul Gilmartin
<[email protected]> wrote:
I thought from discussions here a few years ago that IBM has
provided a
facility that supports renaming of an ENQUEUEd DSN, in the VTOC,
after
requesting confirmation from the operators' console that that DSN
on that
volume is *not* the one to which the ENQ pertains.
Don't know how it interacts with catalog, SMS, indexed VTOCs,
automated
operations, ... This amounts to institutionalizing the technique
of zapping
the VTOC while placing the integrity burden on a human being.
Yes, via the RACF profiles previously mentioned. But someone else
pointed out the line in the documentation stating "Does not work
for SMS-managed data sets."
I have no idea why that restriction exists. I don't recall hearing
about it when we in RACF designed our part of that support.
Walt:
As a guess. All SMS datasets must be cataloged.
Although in all reality you could catalog a "dummy" entry and zap
the dsn to the dummy entry and sms would not know the difference.
Of course you would have to disable new allocations (DISNEW) to the
volume while you did this (forgot to mention in my entry).
After the zap was done you would re-enable the vol volume.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
