Re: Proc*C 2.06 problem

In article <322DA4D9.5FA1_at_esp.bellcore.com>

           ko_at_esp.bellcore.com "Sridhar Ramalingam" writes:

> We are migrating from PRO*C 1.5 to 2.0.6. The
> problem I'm encountering is that SQLCODE variable
> is not being set after an EXEC SQL SELECT statement.
> SQLCODE was being set when I use PROC*C 1.5.
>
> I'm using the following PRO*C 2.0.6 compiler options:
> ireclen=132
> oreclen=132
> select_error=no
> parse=partial
> mode=ansi
> release_cursor=yes
> sqlcheck=syntax
> define=ORACLE
> define=_HPUX_SOURCE
> define=__unix__
> code=ansi_c
> dbms=native
> include=.
> include=/ui/dlbb/envs/5_5/dev/include
> include=/ui/extern/5_5/dev/pecom/include
> include=/ui/extern/5_5/dev/dlbb/include
> include=/ui/extern/5_5/dev/drm/include
> include=/ui/extern/5_5/dev/include
> include=/usr/local/csv/include include=/scmf/TBS/maclib
>
> I include sqlca header file and declare "long SQLCODE"

It's difficult to understand without example code but I would expect one of:
EXEC SQL INCLUDE SQLCA.H;
EXEC SQL INCLUDE SQLCA;
EXEC SQL INCLUDE sqlca.h;
EXEC SQL INCLUDE sqlca;
#include <SQLCA.H>
#include <sqlca.h>
These are each slightly different but usually result in same thing.

and #define SQLCODE sqlca.sqlcode

I have only ever seen SQLCODE referenced with some mechanism like that. I am now at home and unable to check documentation and code but offer my 2 pence for the moment.

--
Walter Briscoe