RE: SQL logging

Mike,

You could always try the iNav SQL Performance Monitor. At iNav 5.4 it is under Databaes>the I in question>Schemas>SQL Performance Monitors. Right click and New to add a monitor.

Gary Monnier


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Thursday, February 23, 2012 11:32 AM
To: Midrange Systems Technical Discussion
Subject: SQL logging

We have an application running on a Linux server making a database connect via ODBC to DB2 on our iSeries. On some occasions CPU use on the iSeries goes sky high on the QZDASOINIT jobs that service the ODBC connection. This application has some components that were developed as DB2 stored procedures, all written in SQL (no high level RPG stored procedures). Looking at the jobs does not reveal much. We have hundreds of users on this system and the high CPU use is not consistent. We suspect that it might be one of the stored procedures that might be doing this but don't know which one. Is there any way to log every request coming in from an ODBC connection so the next time it happens we can see what was being run around the time of high CPU? We have dumped the DB2 database transaction journal records and they do not show high numbers during the busy time which makes me think it is either a loop in the code in a procedure doing calculations or is an index being built on the fly.
However index advisor does not show any long running indexing going on.
--
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.