Unless my memory is failing me, by default I4GL behaves as if WHENEVER
ERROR CONTINUE is effect. If you add WHENEVER ERROR STOP and I4GL (or
I4GL-RDS) does not stop when that error occurs, it is a bug; it should stop.
If there's a bug, there is also a simple workaround as noted by Art until
the bug is fixed test the value of SQLCODE after the connection attempt.
It is likely that the problem will have been created when CONNECT et al
were added to I4GL. The vast majority of statements will work as expected.
On Mon, May 13, 2013 at 2:43 AM, JUAN ROCA <jluis.roca@hotmail.com> wrote:
> Hello,
> I'm using ipcshm connection (deliberately incorrect; I should use tlitcp
> connection instead) in my 4gl program to test DATABASE & CONNECT statement
> concurrently.
>
> This is the code:
>
> database stores7
> main
> database stores7
> display sqlca.sqlcode
> connect to 'stores7'> display sqlca.sqlcode
> end main
>
> When I execute the connect statement it fails with sqlca.sqlcode = -27000
> but
> not stops execution.
>
> I thought that a negative sqlcode value stopped 4gl execution.
>
> Does anyone know the answer to that uncommon behaviour?
>
> Thanks a lot.
>
> Joan Roca
>
>
>
>
>
>
>
--
Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h>
Guardian of DBD::Informix - v2013.0118 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."
--047d7b621d9ccb376704dc9afe91
*******************************************************************************
To post a response via email (IIUG members only):
1. Address it to ids@iiug.org
2. Include the bracketed message number in the subject line: [30257]
*******************************************************************************
↧
