RE: STRDBG problem

Thanks for your reply Shannon.
I understand the STRDBG can change production data. My question relates to
how can I capture some audit trail of what happens while in STRDBG


Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxxxxx
P:(631) 244-2000 ext. 5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill



"Shannon
ODonnell"
<sodonnell@turbog To
orilla-software.c "'Midrange Systems Technical
om> Discussion'"
Sent by: <midrange-l@xxxxxxxxxxxx>
midrange-l-bounce cc
s@xxxxxxxxxxxx
Subject
RE: STRDBG problem
07/02/2008 12:50
PM


Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






Yeah...but STRDBG CAN! Change production data. All you have to do is use
the command EVAL PGMVAR = NEWVALUE while the program is running under
debug and you've changed the value of the variable.

I don't see a way to unconditionally prove what you want to prove.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Wednesday, July 02, 2008 11:10 AM
To: Midrange Systems Technical Discussion
Subject: STRDBG problem


Okay - I may have inadvertently opened up a can of worms.
We use MKS implementer for change control and promotion of changed objects
into our PRODUCTION system.
When we promote CLP and RPGIII programs into PRODUCTION, the compile of
these programs does NOT use OPTION(*SRCDBG). I have submitted a request to
our systems dept to change this default on both CRTCLPGM and CRTRPGPGM so
that if any problems occur on PRODUCTION we can use STRDBG to help
ascertain the cause.
To cut a long story short, with SOX compliance, how can it be shown that a
use of STRDBG does NOT change PRODUCTION data or conversely how can an
audit trail with the use of STRDBG/STRISDB be captured. There has been a
veiled threat that STRDBG (& STRISDB) may be taken away from us on the
PRODUCTION system because of this.
ANY & ALL help will be more than gratefully accepted.



Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxxxxx
P:(631) 244-2000 ext. 5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
--
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.