Nice find. That post supports what you said about CLRPFM hard closing the
pseudo closed cursors, provided file's WAITFILE attribute is set to 1 or
greater. Based on that, check the WAITFILE keyword. If that checks out, then
perhaps this isn't a pseudo closed cursor but an open cursor?
BTW, connection pooling in the application server is a good thing for
performance, but that overrides database connection pooling (host server
jobs are not recycled, they're kept open between uses). That would explain
ODP accumulation in those jobs.
In any case, let us know how you resolve it.
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: Re: QZDASOINIT file lock prevents CLRPFM after v5r2 --> v5r4
upgrade
I found a reference in the archive to an IBM tech doc:
http://archive.midrange.com/midrange-l/200703/msg00685.html
IBM Software
Technical Document
Document Number: 18874457
____________________________________________________________
Functional Area: Host Servers
SubFunctional Area: Database Server
SubSubFunctional Area: General
____________________________________________________________
Product: 400-12 HOST SUPPORT (5769SS1HS); OS/400 BASE (5722SS100)
Release: V4R3M0; V4R4M0; V4R5M0; V5R1M0; V5R2M0; V5R3M0; V5R4M0
Classification: IBM Internal Use
Keywords: JDBC, ODBC, SQL, SQLCLI
____________________________________________________________
Document Title:Pseudo Closed Cursor FAQ
But I can't seem to find that document on IBM's web site.
Does the "Classification: IBM internal Use" mean you can't find it on
the web site?
Thanks!
Charles
midrange.com
