Locks persisting after JDBC requests

All

 

There's a situation on our production box that I don't understand.  We
have a Java front end client that pulls data from AS/400 and Oracle DBs.
When we pull data from the AS/400 database, the requests run just fine,
but there seems to be a lock held on both the logical file and its
parent physical file.  I've tested this through DB Visualizer as well as
the client application, and the request creates *SHRRD locks with
HELD(*YES) status.

 

What gives?  Why does the QZDASOINIT job lock the file once the request
has completed?


Thanks

 

-Ed



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.