The problem I've always had with BULDACCT is that the first job it creates
contain passwords.  You can put this into any secure group you want, but any
user with OP capability and access to a tape drive may potentially restore it
from the tape to a local group and view it.  Storing the directories is a much
more secure option, IMHO, and the UDC's are "reset" when COMMAND.PUB.SYS is
restored.

----
Lee Gunter                    The Regence Group
Supervisor, TRG HP/MPE Systems     503.375.4498
----
Opinions expressed are solely mine.



From: "Paveza, Gary" <[log in to unmask]> on 10/13/99 10:00 AM

Please respond to "Paveza, Gary" <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: [HP3000-L] Creating SLT with additions




Personally we have just the basics.  After loading from an SLT, we can
restore from our backups because Restore is there.  We restore a BULDJOB
which is a full system buldjob (created weekly) first.  After running that
job to create our account structure, we can then perform a full restore, and
run the second buldjob to set all UDCs.

While I can see the benefits of putting additional files on the SLT, is it
really necessary?  I would think that it would have the potenial to cause
more confusion for someone not familiar with a particular environment.

For the same reason, I find the DIRECTORY option unnecessary in store's.
Why bother when a BULDJOB can contain all that information?  At least here,
our account structure doesn't change very often.  We have system wide UDCs
to prevent the addition of new users, new accounts, and new groups (we have
to because we shadow our system to a secondary system for backups and
account structure needs to be identical).