That's useful for determining where that port is, but we have a process leaving rogue locks lying around. Anything that tells what updated the lock table?
On Thu, Sep 8, 2011 at 9:10 AM, Daniel McGrath <dmcgr...@rocketsoftware.com>wrote: > Once you know the pid of the program with the lock, you can use PORT.STATUS > to determine this. You just need to use the CALL.STACK option. IIRC (It's > been a few months) it would be like: > > PORT.STATUS PID <the progs pid here> CALL.STACK > > Regards, > Dan > > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto: > u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King > Sent: Thursday, September 08, 2011 9:06 AM > To: U2 Users List > Subject: [U2] Lock Status > > Is there anything in Unidata that would report the line of code that set a > particular record lock? > > -Kevin > http://www.PrecisOnline.com > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- -Kevin http://www.PrecisOnline.com _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
