Re: Negative locks on tbstat -u

} } RSAM Version 5.02.UC7 -- On-Line -- Up 8 days 00:54:51 -- 42432 Kbytes } } Users } address flags pid user tty wait tout locks nreads } nwrites } 400019f0 ------D 7998 informix nty/037 0 0 0 701 3031 } [stuff deleted] } 400029cc --B---- 9499 hedds - 0 0 4 4930 0 } 40002a40 ------- 9536 hedds - 0 0 2 1973 0 } 40002ab4 --B---- 9065 woodsm - 0 0 2 53 3 } 40002c84 --B-R-- 2142 foosm - 0 0 -16780 13090 } 11820 } 28 active, 256 total } } Transactions } address flags user locks log begin isolation retrys coordinator } 40008df0 A---- 400019f0 0 0 NOTRANS 0 } [stuff deleted] } 4000d7a0 A---- 40001f60 1 0 COMMIT 0 } 4000e3e8 A-B-- 40002c84 -16780 347 COMMIT 0 } 4000f654 A---- 400024d0 1 0 COMMIT 0 } } 23 active, 256 total } } What causes the number of locks to go negative? Is the number of locks over } } flown or something? The ovlocks field in the tbstat -p is zero, so I don't } know } if the process is ok or should be killed. } } Any help will be greatly appreciated. } } My guess is that MAXINT or MAXLONG was exceeded, causing the number to look funky. The maximum integer and long (etc) are set per platform. If it make you uneasy, tbstat -z (look it up to be sure) clears your statistics, but I would not worry about it. } } ===================================================================== } Paul Watje Database Something or Another } watjep@hasting.com Hastings Books, Music, & Video } -- Naomi Walker (aka N7FSA) | naomi@anasazi.com | Phoenix, Arizona ---------------------------------------------------------------------- It's almost impossible to overestimate the unimportance of most things.