I'd also suggest that you give WRKODBCJOB from Bryan Dietz a try if you
haven't already (http://home.roadrunner.com/~jbmmdietz/wrkodbcjob.html
It isn't going to show you anything that you don't already have access
to through the various WRK* commands but since it centers those commands
around the ODBC/JDBC connections that are currently active and
consolidates all the information onto a single list of connections, it
makes it a heck of a lot easier to bounce around the information.
Have you taken a look at the JVM job? (WRKJVMJOB) Sometimes I can get
nuggets of information by perusing the job/threads/job properties that
will lead to a solution.
Value Added Software, Inc
GIAC Secure Software Programmer-Java
On 12/12/2011 3:11 PM, James Lampert wrote:
Pete Helgren wrote:
Specifically look at the QIBM_QZDA_* exit points. That is where I have
Thanks, and those hooks are all completely vacant.
found exit programs for JDBC/ODBC hanging out....
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.