In a message dated 98-07-09 21:32:37 EDT, you write:

> Well guess what!  Programmers at this company are not AUTHORIZED to do
>  this on a production machine, this has me floored!
>  I would appreciate any suggestions my fellow-list-people would offer me
>  to somehow circumvent this perplexing problem.
>  Thanks very much in advance.

My current client uses a series of fully-audited "firecall" ID's on their
production box that are disabled until a developer "checks one out" from the
help desk.  The ID's have pretty much QGOD authorization, so the auditing is
important (they caught one guy giving himself *ALLOBJ authority on his regular
ID from the firecall!).  If the developer doesn't "check in" the "firecall"
ID, it is automatically disabled at the end of the day.  Works pretty well...

One Solution,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"The trouble with life in the fast lane is that you get to the other end in an
awful hurry." -- John Jensen
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].