Barbara Nitz wrote:
this has been my request for a long long long time. (with the exception of
the ZFS datasets of course). The problem with this is that the other
Serverpac jobs that massage the CPAC parmlib/proclib that come with it.
That was my other 'problem'. I don't want that CPAC stuff on my target (or
residence) volume, and I did not find a way to move it to an SMS-managed,
pre-existing qualifier. I ended up massaging that, too. I only keep CPAC as
reference.
So I guess the answer is 'no way' to my question.
And I just discovered that SYS1.UADS is in SMPE, but was NOT restored by
serverpac, same as sys1.Auads. In my thinking it would have been fine to not
have a sys1.uads *at all*, but to have it in the SMPE environment but not on
the restored volumes is bad. How do I know if there will be maintenance to it
when it will not find anything?
The only part of this I'll comment on is whether or not one should have
a UADS data set at all.
I will assert one should, purely for recovery purposes in case the
security database and its backup must be restored. In a very
restrictive networking environment, one can log on with UADS to recover
the security DB from backups, and re-IPL with normal security
immediately afterward.
Just my two cents.
--
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
