RE: [U2] locking question

I notice you're on nix ...

Is the piece of code that writes invoked via an EXECUTE or PERFORM from the code that did the original READU?

I wouldn't expect it to on doze, but on Unix that *might* change the execution environment enough to cause a
problem... (grasping at straws to see if it gives you any more ideas...)

Cheers,
Wol

-----Original Message-----
From: owner-u2-users <at> listserver.u2ug.org [mailto:owner-u2-users <at> listserver.u2ug.org] On Behalf
Of doug chanco
Sent: 01 July 2008 15:03
To: u2-users <at> listserver.u2ug.org
Subject: [U2] locking question

hey all,
      has anybody run across/seen an issue where a process sets a lock
via READU and then when it tries to write back the record cannot because
the record is locked but somehow "lost" the fact that the process trying
to write the record is the process that created the lock?

I am not sure if this is even possible but we at are at a loss as to
whats causing this lockup (which does not occur regularly but enough
that its causing us concerns with our "busy season" coming around)

We had a lock up last night that LIST.READU EVERY showed that that a
process was holding a lock and that the same process was failing on a
write (in a program) and 'stuck' (yes we have old old old old old code