RE: STRSQL audit log

This is a rather broad requirement, yet amazingly incomplete.... Does the auditor understand that STRSQL is only one of many ways to alter data in tables? What about ODBC from PCs, or DRDA remote SQL, or DDM?

Journaling will be focused on capturing the actual data changes, but does not capture meaningful information about what process is changing the data. The exit point security monitors can capture details about the SQL statements being executed from ODBC/JDBC services, but they will not work for local SQL interfaces, like STRSQL or STRQMQRY. One could start a global SQL monitor job, that would capture all SQL statements for all jobs on the system, but converting this into a meaningful report could be difficult.

Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul E.
Fenstermacher
Sent: Wednesday, May 21, 2008 7:53 AM
To: Midrange Systems Technical Discussion
Subject: STRSQL audit log


Our auditors want us to maintain a log of activity around this command
like we can do with DFU and DBU. Anyone know a way to do this? Thanks.



Paul Fenstermacher

Certified Specialist - i5 System Administration

Bass Pro Shops

417-873-5424 d

417-429-7694 c

paulf@xxxxxxxxxxx