On Thu, May 21, 2009 at 9:46 AM, Fred Schmidt <fred.schm...@nt.gov.au> wrote:
> I have tried defining a second user and LINK’ing to MAINT’s minidisks. That > only allows read access if MAINT is already logged on. Another approach is to separate the tasks on a functional level in different maintenance userids. With MAINT owning your z/VM software maintenance, you can use another account to manage the directory, be SFS admin, do performance analysis, manage your hardware, be RACF special, etc. You then provide logonby access to those who need to do that work. Assign privileges to each account as required. And if you only use that account when you actually do something with it, the contention problem goes away. Often a lot of tasks don't need full CP class ABCDEG and LNKNOPASS and what else. Take advantage of the protection that VM can offer to limit the impact of mistakes. To me the good part is that you realize someone "is doing something" with that part, so you can prevent breaking things that others are working on. Rob
