CL Command DSPAUDJRNE displays or prints all Audit entries. All ODBC connectivities will come under JOB ‘QZDASOINIT’. Each job desribes it’s descriptions.
Note that, You must have activated Auditing for your system to hae the audit entries.
I hope this helps.
The QAUDJRN audit journal will tell you when a user connects to a QZDASOINIT job, but it won’t tell you if any user actually did anything unless you enable user and object audit for all users and all objects that you want to track. Further, if user/object auditing is enabled, it won’t tell you what was read or changed. (Database journals can track changes as could triggers. Triggers that log each read and/or change could quickly create log files far larger than the files they track.)
An ODBC transaction will generally be a SQL statement. The various ‘QZDA’ exit points give you a chance simply to log the SQL statements to track transactions. That can be more useful and take up far less space.