Re: QZDASOINIT file lock prevents CLRPFM after v5r2 --> v5r4 upgrade

This e-mail is directed to Charles Wilt, and as I have no direct connection
to him, I beg the lists forgiveness.
Charles - you mentioned that you use Webmethods.
If you are willing to answer a question or 2 with respect to the AS/400 &
Webmethods, I would be very grateful
Please contact me via my attached e-mail address
Thanks in advance


Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


midrange-l-bounces@xxxxxxxxxxxx wrote on 02/09/2009 01:29:15 PM:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.