Re: STRSQL audit log

2008/5/21 <bev.russell@xxxxxxxxxxx>:

I have the same issue as Paul and the auditors want something that is
automatically generated. Is there any way to call the command behind F13
directly. Is there an API for it? I haven't had a chance to dig into that
yet. Has anyone else had to satisfy this audit request?

As far as I'm aware you can't get to this through an API. There is a
convoluted route where you can do a DMPSYSOBJ (ISQLSTuserprofile*)
CONTEXT(QRECOVERY) TYPE(19) SUBTYPE(EE) (where userprofile is the
name of the user whose saved SQL session you are trying to get to.)
You then have to parse the resultant spooled file to reconstruct the
SQL history. This only works if the user has set their options to save
their session, obviously.

There is a nice free utility to scan a user's SQL history that might
help - http://home.alltel.net/craigru/jcrdown2.html#JCRSSQL_tag

I expect the correct way to go is to use the appropriate exit point -
QIBM_QZDA_SQL1 & QIBM_QZDA_SQL2 look to be likely candidates and log
all SQL access. There's an article on this at
http://www.itjungle.com/fhg/fhg110806-story01.html

Regards, Martin