ADSM-L

Re[2]: Admin deleted, job not run

1998-07-29 13:36:41
Subject: Re[2]: Admin deleted, job not run
From: Jerry Lawson <jlawson AT THEHARTFORD DOT COM>
Date: Wed, 29 Jul 1998 13:36:41 -0400
Richard -

The problem we would probably get into here is one with the security
department - While the root user concept is a fundamental part of Unix, it is
not a mainframe concept.  The security folks in my shop have a "mainframe
mindset" that basically says that ids will not be shared between people.
Since there is an alternative (of sorts) here -they probably wouldn't approve
this type of approach.

The bureaucratic mind never fails to amaze me.

Jerry Lawson
jlawson AT thehartford DOT com

______________________________ Reply Separator _________________________________
Subject: Re: Admin deleted, job not run
Author:  owner-adsm-l AT VM.MARIST DOT EDU at SMTP
Date:    7/29/98 8:48 AM


>In my shop, that would bring ADSM to its knees, since I set up all of
>the automation using my id.

I think the obvious solution here is to simply define a general administrative
ID within a shop (much like root on a Unix system) and use that for
administrative tasks involving configuration changes where ADSM is sensitive to
the administrator ID.  Use private administrator IDs for queries, Set commands,
and the like.  Individual administrators can then come and go, but the general
one can persist.
     Richard Sims, Boston University OIT
<Prev in Thread] Current Thread [Next in Thread>