Re: STRDBG problem

Hi Alan,

It may not be good enough for the auditors, but perhaps you could use
something like

STRCPYSCN SRCDEV(*REQUESTER)
OUTDEV(*NONE)
OUTFILE(MYLIB/DEBUGLOG)

before starting debug, and

ENDCPYSCN SRCDEV(*REQUESTER)

after ending debug, then printing the outfile.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Alan Shore wrote:

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