RE: STRDBG problem

Charles,

You know, my response still hasn't reached me. Odd since I sent it this
morning.


I was not giving a sales pitch on Authority Broker. I suggested to Alan
he ask his auditors if Authority Broker would satisfy their needs. It
is a possible solution to his rather dicey dilemma. Nothing more.

But since you asked <G>, here goes.

From a green screen, a combination of Authority Broker and a source

debugging program you can provide an excellent audit trail. You can
find an example of a source debugging program at
https://publib.boulder.ibm.com/infocenter/systems/scope/hw/index.jsp?top
ic=/apiref/apiexusdeb.htm.


I'd be interested in how you get Authority Broker started for a debug
session in WDSCi. PowerTech's Network Security product will provide
you an audit trail for network traffic passing through the host servers
(WDSCi utilizes the host servers). PowerTech's Compliance Monitor
product provides reporting capabilities for the journal entries created
by STRDBGSVR.

Authority Broker has several exit points you can utilize for STRSQL
issues. To obtain information from a STRSQL session you can write exit
programs to do so (for example STRDBMON at switch time and ENDDBMON at
end switch time). Authority Broker Event reporting can be directed to a
database file. So, the information from your exit program can be
combined with Authority Broker's Event output. With this combined
information I believe you will have virtually everything you require.


iNav's Run SQL Scripts can be audited using PowerTech's Network
Security.


As an aside, the least popular thing to do will result in Authority
Broker reporting database changes... journal your files to QAUDJRN.
Authority Broker will report journaled activity during the profile
switch.


HTH


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


Gary,

Are you saying that your product would provide an audit trail for the
debug session? Not just the fact the STRDBG was used, but exactly what
went on during the debug?

If so, what about debugging via WDSCi instead of the green screen?

For that matter does you product provide an audit trail of the records
changed using STRSQL or iNav's Run SQL Scripts?

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 Gary Monnier
Sent: Wednesday, July 02, 2008 12:39 PM
To: Midrange Systems Technical Discussion
Subject: RE: STRDBG problem

Alan,

The fact of the matter is debug can be used to alter production data.
It just that it would occur before hitting the database via chgpgmvar
or eval. Given this I can see how an suditor would want some sort of
trail to follow. Ask your auditors if a product like our Authority
Broker product will satisfy their needs. You can find out more about
it at our web site www.powertech.com.

Gary Monnier
The PowerTech Group, Inc.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Wednesday, July 02, 2008 9: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.

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.