|
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 -----Original Message----- From: Lim Hock-Chai [mailto:Lim.Hock-Chai@xxxxxxxx] Sent: Thursday, November 11, 2004 10:35 AM To: Midrange Systems Technical Discussion Subject: RE: Restrict ability to alter variables in debugger on production sounds good but not practical. If some important job, such as billing/invoicing job, blew up in the middle of the night, try ask the programmer to copy dozens of master files to test system, recreate the problem and then debug it on the test system to see what cause the problem. He/she is going to tell you that just copy those files is going to take all night. Also, there 3 or 4 more jobs that waiting for this job to complete before they can be submitted. Oh, ya, and the backup job comes after that and it need to complete before user start to sign on to the system. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Raby, Steve (GE Advanced Materials, consultant) Sent: Thursday, November 11, 2004 9:56 AM To: Midrange Systems Technical Discussion Subject: RE: Restrict ability to alter variables in debugger on production You can restrict the programmers from updating in the production environment, if they need to run thru any data copy it to test and then they can play to their hearts content. Steve Raby -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.