RE: Restrict ability to alter variables in debugger on production

["Raby, Steve \(GE Advanced Materials, consultant\)" <steve.raby@xxxxxx>]

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

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Morrison
Sent: Thursday, November 11, 2004 4:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: Restrict ability to alter variables in debugger on
production


Under these circumstances, (SOX), why are the programmers running debug over
production data? 


Steve Morrison
Beacon Insurance
940-720-4672 

-----Original Message-----
From: Rick.Chevalier@xxxxxxxxxxxxxxx [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]

Sent: Thursday, November 11, 2004 9:16 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Restrict ability to alter variables in debugger on production

First, an assumption - The programmers are using debug to look at production
jobs accessing production data.

Wouldn't this setup prevent programmers from using debug at all?  If, under
debug, a program tries to open a file for update using the command defaults
the job will abend.  Changing the UPDPRDDTA parameter to *YES will allow the
file to open under debug but the system security is set to only allow read.
Again, I believe this will cause the job will abend when it tries to open a
file for update.

Am I missing something?

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Morrison
Sent: Thursday, November 11, 2004 8:52 AM
To: Midrange Systems Technical Discussion
Subject: RE: 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. 

Set up the programmers libraries as *TEST libraries. Allow them read only
access to the production data libraries. This will prevent them from
changing production data. The OS will enforce the security, and there is no
need for a special debugger that will not allow a programmer to change data
while stepping through the programs. 


Steve Morrison
Beacon Insurance
940-720-4672 

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

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