× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mike,

You can use a combination of the QIBM_QZDA_SQL2 exit point and Retrieve Job Information (QUSRJOBI) API format JOBI0600 (for client IPV4 IP address).

For the IP address you want to audit you can do a number of things.

o Write the SQL string supplied in QIBM_QZDA_SQL2 to a file, journal or simply print it.
o Have the exit program send an inquiry message to the operator's message queue. This give you the chance to put it in debug, start a job trace or whatever else you feel can be done.

If you already have a commercial package protecting you exit points see if they allow supplemental exit programs to run. At least one package I know of has/had this feature. It did not require you to register the supplemental exit program. You enter your exit program into the product's server properties and you are running.

If you don't you'll have to register your exit program to the exit point using the ADDEXITPGM command (option 8 in WRKREGINF) or the Add Exit Program (QUSADDEP, QusAddExitProgram) API.

You will have to bounce the host server *DATABASE with end active connections *DATABASE after you register your exit program to ensure all QZDASOINIT jobs utilize the exit point.

HTH


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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.