Re: 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

--
I'm riding in the American Diabetes Association's Tour de Cure to raise
money for diabetes research, education, advocacy, and awareness. You
can make a tax-deductible donation to my ride by visiting
https://mideml.diabetessucks.net.

You can see where my donations come from by visiting my interactive
donation map ... https://mideml.diabetessucks.net/map (it's a geeky
thing).
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list
To post a message email: JAVA400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com