Testing locks in Aubit4gl

I am working through the exercises in "Informix4GL by Example".  I am at
exercises 22 and 23.  These are specific to the Informix database system and
check for error codes: First to determine the database features; and second to
determine if an attempted lock is successful or not.

These error codes
(-107,-113,-134,-143,-144,-154,329,-349,354-377,-512,-513,-527,-827) are not
documented in PostgreSQL so I infer that they apply only to Informix.

My question is:  Are there equivalent error codes for determining whether or
not a table or row lock as succeeded or failed and why:  If so then where are
they documented?

PostgreSQL notes that SQLCODE is deprecated in favour of SQLSTATE.  I gather
that the SQLSTATE structure is not implemented in Aubit4GL. PostgreSQL list of
valid error codes is very much limited.

SO, if one cannot get the reason for a lock failing through examining an error
code then how does one do so in Aubit4GL?

Any help is appreciated.

-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
   Unencrypted messages have no legal claim to privacy
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:[email protected]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3