HP3000-L Archives

June 2000, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bob Sorenson <[log in to unmask]>
Reply To:
Bob Sorenson <[log in to unmask]>
Date:
Fri, 2 Jun 2000 14:48:33 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Hello All!

I would appreciate any comments you might have regarding SM capability.  We
have five folks who have SM capability on our production box.  Three are
Ops; two "upper management".  I am being asked to give our Senior
programmer, who now has the title of  "Manager of Production Support", SM
capability.

Any IT audits I've gone through have made it clear to me that Ops and
Programming should be very separate functions.  Operations moves code into
production.  I've asked for justification, and I was told this person needs
it for account maintenance, udc maintenance, and copying files across
accounts.  Only account maintenance can't be done without SM, and I contend
that should be an Operations function.

As with any System Manager, I am ultimately responsible for what happens on
the machine and I'm not comfortable giving this out to somebody who is
bright, but may not understand the ramifications of changes to udcs,
third-party software accounts, etc.

So, yes or no?  Your reasons why you feel the way you do would be greatly
appreciated!    :-)

Bob Sorenson
System Manager

INFOTRUST
1615 Lakeside Drive - Ste 200
Waukegan, IL  60085
Voice:  847 887-8087
Fax:    847 887-8001
[log in to unmask]

ATOM RSS1 RSS2