Information on locking-conflicts

Hi group, I'm writing a small tool for monitoring our informix-application (printing cpu-utilisation per session, long-running sql, ...), using lots of information out of the SMI-tables. Yesterday I added code to print SQL-Errors; this works fine. Informix puts most Error-Info of each session in some SMI-Tables and keeps it there until the next sql-call. No problem so far ... However I added this piece of code to trap all locking-conflicts and print tablename, lockowner, and so on. It seems that these errors are either not trapped in the SMI or not kept until the next call - I just get SQLCODE 0 in case of locking errors. BTW, I can't find the locking-errors using onstat either. Qustions: * Is there a reason not to store specific SQL- and ISAM-Codes in the SMI? * Are there other ways to find errors based on locking-conflicts? (I don't want to read the syslocks every time, just in case of an error!) Thanks in advance, Peter -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/_/ Mag. Peter Kolmhofer __ _ _____ _/ _/_/ Informix & DB2 DBA __ --/_|___\\______ _/ _/_/ Porsche Informatik (Austria) _ _ ( _ _ \\) _/ _/_/ A-5101 Bergheim, Handelszentrum 7 -(_)-------(_)- _/ _/_/ +43 662 4670-6258 fax: -6501 email:kop@porsche.co.at _/ _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/