Re: tblsnum in onstat -k

Sounds good... select * from syslocks.... is easier.. Superboer way fast=http://www.clipjes.nl/clip/nederlands/n/normaal_- _oerend_hard.html On 6 dec, 01:30, mohitanch...@gmail.com wrote: > Version IDS 10: > > Is following sql correct to retrieve associated table for that lock > listed in onstat -k: > select * from sysptnhdr where hex(partnum) = tblsnum;> or > select * from systabnames where hex(partnum) =tblsnum;

On Dec 6, 7:29 am, Superboer <superbo...@t-online.de> wrote: > Sounds good... > select * from syslocks.... is easier..> > Superboer > > way fast=http://www.clipjes.nl/clip/nederlands/n/normaal_- > _oerend_hard.html > > On 6 dec, 01:30, mohitanch...@gmail.com wrote: > > > > > Version IDS 10: > > > Is following sql correct to retrieve associated table for that lock > > listed in onstat -k: > > select * from sysptnhdr where hex(partnum) = tblsnum;> > or > > select * from systabnames where hex(partnum) =tblsnum;- Hide quoted text -> > - Show quoted text - I use syslocks generally, but this time I was looking at the assertion tmp file that Informix generates. So all I have is tblsnum to track down which table had this lock on. But, when I ran the above sql I didn't get any output. Why wouldn't I get any rows, my understanding is that the tblsnum is a partnum from sysptnhdr or systabnames