RE: STRDBG problem

Alan,

I don't think what you are asking for exists...

Allowing the debugging of programs on a production system just isn't going to fly with SOX and/or PCI.

However, do yourself a big favor and make sure that instead of simply your authority to the STRDBG
command, the admins simply make sure you don't have *CHANGE authority to the programs in production (
or *USE to the program plus the *SERVICE special authority).

This way, you won't be able to debug programs, but you will be able to switch a job into debug mode so
you can get diagnostic information from the query engine when running SQL statements.


Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Wednesday, July 02, 2008 12:10 PM
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 e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.