RE: Restrict ability to alter variables in debugger on production

["Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxx>]

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