|
that is what we are trying to get implemented on our shop. A bit different though, we are actually creating a system that the on-call programmer can sign on to get some additional access to production system. This system requires on-call programmer to comment as why he/she needs to sign on and what he/she did before sign off. I think it also saves the joblog. Not sure if this will pass SOX yet. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Morrison Sent: Thursday, November 11, 2004 10:43 AM To: Midrange Systems Technical Discussion Subject: RE: Restrict ability to alter variables in debugger on production At a previous employer, we worked with a system setup as I described earlier. Programmers had read only access to production libraries. If the on-call programmer needed additional access to correct a problem, the night operator would run a special job granting additional authority for that session. After ending the session, the programmer would again be restricted to read only access of production data. Steve Morrison Beacon Insurance 940-720-4672
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.