Re: SQL logging

Mike -

Have you taken steps to isolate the ODBC jobs to a separate subsystem with its own private memory pool or shared memory pool in order to get the work out of the *BASE memory pool? I would strongly recommend this if you have not.

When I did this recently on my client's system, it stopped a lot of thrashing that was happening on the system, and overall system performance improved significantly.

- sjl


"Mike Cunningham" wrote in message news:mailman.3314.1330025647.29960.midrange-l@xxxxxxxxxxxx...

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.