syslocks problems

I would appreciate some help Thanks in advance Problem/Question: It seems that the several sysmaster locking tables may be hosed up since the syslocks view doesn't have any rows associated with it. Has anyone seen this behavior before? How can onstat -k be correct, yet syslocks is incorrect? Can this be causing problems with our OLTP applications? Environment: Were running IDS 7.31 FC2 on HPUX 11 we are running OLTP applications - 300-400 user sessions Background: 1- If you run the query: select * from syslocks, you get "no rows found" 2- Interestingly, if I run the sql for the view (syslocks is a view), I will retrieve rows - ??? 3- But, the rows I retrieve from (2) are all associated with session id = 1 instead of the true user sessions - ??? 4 - From onstat -u, session id 1 has position 7 flag of "D" indicating it is a Daemon thread (what is this doing?) 5 - onstat -k shows 499 active locks. The "owner" address corresponds to the user threads (session id <> 1) from onstat -u indicating that onstat -k seems be retrieving correct information 6 - Here's the sql for the syslocks view select dbsname, b.tabname, keynum, rowidr, e.txt[1,4], d.sid, f.sid from syslcktab a, systabnames b, systxptab c, sysrstcb d, flags_text e, outer sysrstcb f where a.partnum = b.partnum and a.owner = c.address and c.owner = d.address and a.wtlist = f.address and e.tabname = 'syslcktab' and e.flags = a.type