to use STRDBG you DO have to STRDBG ALWUPD(*YES), and that is the problem.
This is taking place on out production system, and the auditing concern was
that while in debug, production data COULD be changed (using EVAL) and
there was no way to capture this change.
Programmer/Analyst, Direct Response
P:(631) 244-2000 ext. 5019
"If you're going through Hell, keep going" - Winston Churchill
midrange-l-bounces@xxxxxxxxxxxx wrote on 07/02/2008 03:10:51 PM:
Perhaps I misunderstood the question or do not understand any implication
of SOX, but ...
Should you not STRDBG ALWUPD(*YES) to change values in debug and update
output. whether PF, DSPF or PRTF?
If you don ont start it like that, you cannot run debug properly, when a
programme contains updateble files. It warns you for that.
If there is an update in the file, use journalling, triggers and other
traditional auditing tools available.
*********** REPLY SEPARATOR ***********
On 2-7-2008 at 12:57 Alan Shore wrote:
Thanks for your reply Shannon.
I understand the STRDBG can change production data. My question relates
how can I capture some audit trail of what happens while in STRDBG
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives