RE: Locks persisting after JDBC requests

I think system is trying to reuse ODPs to enhance performance.  Think of
ODPs as handles/cursors to your file.  They're expensive buggers to keep
recreating, so DB2 tries to avoid it when possible.

If you want to disable this behavior, try unchecking "lazy close" support in
your ODBC data source or Java data source connection strings.  It may tank
your performance though.

Elvis

-----Original Message-----
Subject: 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