Re: Restrict ability to alter variables in debugger on production

["Bob Kohlndorfer" <bkohlndorfer@xxxxxxxxxx>]

This is kind of an old thread by now but I came across something that might be 
of interest here.
It looks like one of the compile options for ILE programs is the Optimization 
level.  
It has 3 options:
*NONE                                                    
    Generated code is not optimized. This is the fastest 
    in terms of translation time.  It allows variables to
    be displayed and modified while in debug mode.       
                                                         
*BASIC                                                   
    Some optimization is performed on the generated code.
    This allows user variables to be displayed but not   
     modified while in debug mode.                        
                                                          
 *FULL                                                    
     Optimization which generates the most efficient code.
     Translation time is the longest. User variables may  
     not be modified but may be displayed, although the   
     presented values may not be the current values.      

Perhaps if this functionality could be put into production environments it 
could prevent anyone from changing variable during debug.  It may be 
impractical to get your whole production environment done at once but perhaps 
if you do have to debug a program it should be recompiled with an optimization 
level first.

Regards,
Bob Kohlndorfer
Unbeaten Path International


----- Original Message ----- 
From: <vhamberg@xxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, November 10, 2004 11:09 AM
Subject: Restrict ability to alter variables in debugger on production


A customer has asked whether there is an iSeries-usable debugger that can be 
used in such a way that a programmer cannot change the values of variables 
while stepping through a program. Reason for this is SOX. They want to avoid 
all the documentation and special approval required to do this.

I know, programmer's should not even be looking at production data. And they 
should probably have a set of test data to do this. And trying to get around 
these requirements sounds like a breach in the first place. Nonetheless, they 
are asking.

Thanks
Vern
--
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.