I believe that if the program ended the lock would be released, so by
finding the PID via LIST.READU and then determining the program name
associated with the PID via PORT.STATUS you are identifying the program
which currently holds the lock unless the program ends between the
LIST.READU and PORT.STATUS.
At least in my Unix/Universe world.
Wjhonson wrote:
This won't work unless the program is halted-waiting.
Most likely it's moved on to do a hundred other things since the lock in
question, but left it hanging because the pid is still living.
If the pid dies it would release the lock, but for example, even on non-SB
systems, phantoms which run constantly can leave locks hanging forever.
-----Original Message-----
From: Jeff Schasny <jscha...@gmail.com>
To: U2 Users List <u2-users@listserver.u2ug.org>
Sent: Thu, Sep 8, 2011 8:34 am
Subject: Re: [U2] Lock Status
Kevin,
I think that the closest you are going to be able to get is the program
n question using LIST.READU to determine the PID and PORT.STATUS to
hen find the program. I don't know of any way to dynamically get to the
rogram line number from there. You could, of course, just look through
he program source and the READUs then make an educated guess from there.
Kevin King wrote:
Unfortunately, no love there either John. I even went to the GETREADU( .. )
function in BASIC.. nothing there.
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
--
------------------------------------------------------------------------
Jeff Schasny - Denver, Co, USA
jschasny at gmail dot com
------------------------------------------------------------------------
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
