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?

Dan Kimmel wrote:

Doesn't look to me like the login for WINTOUCH was accepted. I don't
see the

User WINTOUCH from client 10.8.2.134 connected to server.

Message that I expect to see on a successful connection.

Is there a security exit in place at this customer? We had a similar
problem with a customer who was using a security product to filter
all logins. The login attempt shows in QHST, but nothing else shows
up, success or failure. The login is basically held like there was a
QSYSOPR inquiry message waiting for a reply.

What I know about the operating system's exit hooks, and a buck, might
still get you a cup of coffee.

I looked up exit programs, in connection with database host servers, and
the first thing I found was in connection with the PCSACC network
attribute. On the box in question, it's set to *OBJAUT.

Is there someplace else I should be looking for security exit programs clamping down on JDBC? Or something I can do to test your hypothesis empirically?

Oh, and I just ran another BIRT test; there are no QSYSOPR messages in connection with it. And nothing in the joblog for the QZDASOINIT job that QHIST says I connected to, that could have been me, other than a "ACGDTA for 543510/QUSER/QZDASOINIT not journaled; reason 1."; all other joblog messages are either hours before, or minutes after, my BIRT report attempt.

--
JHHL