Re: More, Re: Can anybody suggest any reasons why BIRT would be unable to establish a JDBC connection, when running on the same physical box?

[Pete Helgren <pete@xxxxxxxxxx>]

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.

Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
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
> > found exit programs for JDBC/ODBC hanging out....
> Thanks, and those hooks are all completely vacant.
>
> --
> JHHL