RE: JDBC host server job locks object after 2nd query

This may be a Captain Obvious type of question, but are you closing your statements and connections after the query is done ?

Also what type of Java app ? Web App, Web Service, Console or other background type of app ? Run once or always running ?

Or maybe it's just V7R2....

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------

message: 5
date: Fri, 16 Apr 2021 09:37:19 -0500
from: David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: JDBC host server job locks object after 2nd query

Folks:

I'm cross posting this to the java & midrange list because I'm not sure
it's a specific to java.

I've got a situation where, when I query a file using jdbc, it's locked
by the host server job (QZDASOINIT) for the length of the query.

If I query the same file again, using the same connection, the file is
locked and remains locked after the query is complete.

Is this a case of the query optimizer trying to be efficient? Is this
something that can be controlled using jdbc properties or QAQQINI?

This is happening on 7.2.

Thanks!

david