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


On Mon, Feb 9, 2009 at 1:29 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

All,

I've got a set of files that get written to by a Web Methods job via JDBC.

A couple of hours later a batch job on the system processes the files
and uses CLRPFM to clear them.

Even since the machine was upgraded from v5r2 to v5r4, the process has
stared failing becasue the CLRPFM can't get an exclusive lock to the
file and the QZDASOINIT job still has a lock.

We're going to be double-checking that the Web Method job is closing
everything it should be. And we know that we could use SQL instead of
CLRPFM clear the file without the lock issue.

I know the system will sometime "pseudo-close" open data paths. But
my understanding is that if an ODP is "pseudo-closed", any request for
an incompatible lock by another process, ie. the CLRPFM, would cause
the ODP to be fully closed and locks released. Thus, the CLRPFM
shouldn't fail from a "pseduo-close".

Is my understanding correct?

Irregardless, the question being asked is what changed, as we started
having a problem the day after the upgrade and the Web Method process
has not been changed. So I'm wondering if anybody knows or has any
thoughts about
--When the "pseduo-close" functionality was added.
--System values the might control the use of "pseduo-close"
--changes between v5r2 and v5r4 that might be causing this
--things to check, like MAXUSE() on the pre-start job entry that could
have been reset by the upgrade

Others?

Links to IBM documentation gladly accepted.

Thanks!
Charles Wilt