Re: Testing locks in Aubit4gl

On Tue, July 13, 2021 03:37, Mike Aubury wrote:
> You can use the etc/convertsql/INFORMIX-POSTGRES8.cnv to convert for any
> you need.
>
> eg.
>
> REMAP_ERROR 42703=-217
>
> Informix : -217    Column column-name not found in any table in the query
> Postgresql state 42703 :  UNDEFINED COLUMN  (
> https://www.postgresql.org/docs/8.2/errcodes-appendix.html)
>
>


The difficulty being that I cannot discover what -217 is supposed to mean to
begin with:

$ afinderr -239
/opt/aubit4gl/etc/helpsql_POSTGRES8.hlp:
-239 duplicate key violates unique constraint

$ afinderr -217
$


I have looked for a list of error codes that Informix4GL is expecting in the
exercise and can find no such list.  References to finderr are the only
documentation I chave located.  However, afinderr does not cover the error
codes that the exercise is looking for.

I have located the document specifying the SQLSTATE codes that Informix
produces, but that is not the same thing.

I am actually concerned about the entire subject of locking.   In my previous
experience with 4GLs DB, Table, and Row locking were all handled by the
language syntax itself.  To me this does not appear to be the case with
Informix4GL.   How does Aubit4GL put a lock on a row and test for success? 
Where is this documented?   Or, does one do all this in SQL?

-- 
***          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