EXEC SQL DECLARE D63_A999 TABLE
( VAR1 CHAR(17) NOT NULL,
VAR2 DECIMAL(13, 0) NOT NULL,
VAR3 DATE NOT NULL,
VAR4 DECIMAL(7, 0) NOT NULL,
VAR5 CHAR(1) NOT NULL,
VAR6 CHAR(1) NOT NULL,
VAR7 DECIMAL(11, 0) NOT NULL,
VAR8 DECIMAL(7, 0) NOT NULL,
VAR9 CHAR(9) NOT NULL,
VAR10 DECIMAL(15, 2) NOT NULL,
VAR11 CHAR(2) NOT NULL,
VAR12 DATE NOT NULL,
VAR13 DECIMAL(9, 0) NOT NULL,
VAR14 DECIMAL(3, 0) NOT NULL,
VAR15 CHAR(1) NOT NULL,
VAR16 CHAR(1),
VAR17 DECIMAL(7, 0),
VAR18 DECIMAL(7, 0),
VAR19 CHAR(1) NOT NULL,
VAR20 CHAR(35) NOT NULL,
VAR21 CHAR(35) NOT NULL,
VAR22 CHAR(35) NOT NULL,
VAR23 CHAR(35) NOT NULL,
VAR24 CHAR(35) NOT NULL,
VAR25 CHAR(35) NOT NULL,
VAR26 CHAR(35) NOT NULL,
VAR27 CHAR(1) NOT NULL,
VAR28 CHAR(1) NOT NULL,
VAR29 CHAR(1) NOT NULL,
VAR30 CHAR(40) NOT NULL
) END-EXEC.
What is wrong with that code?
I googled for "unsupported VAR construction" and got no relevant hits.
How do I understand the messages coming out of esqlOC? Is there some reference or technique to debug it?
Original code is from DB2 and the target is postgres.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just a note: Sergey just updated esqlOC switching to version 3 [contrib:r976], you may want to recheck if there are any differences and not ask @ska00 for help (at least more helpful error messages).
Thanks Simon, sorry for the delayed response on this.
We just tested with esqlOC v3.0 and we still get the same "unsupported VAR
construction in DECLARE SECTION:" error when compiling. Other research
suggests that esqlOC should be treating "DECLARE SECTION" as a comment as
it is DB2 mainframe specific. Thanks for any insight and help with this.
Thanks Simon, sorry for the delayed response on this.
We just tested with esqlOC v3.0 and we still get the same "unsupported VAR
construction in DECLARE SECTION:" error when compiling. Other research
suggests that esqlOC should be treating "DECLARE SECTION" as a comment as
it is DB2 mainframe specific. Thanks for any insight and help with this.
I got this error:
unsupported VAR construction in DECLARE SECTION:
On this code:
EXEC SQL DECLARE D63_A999 TABLE
( VAR1 CHAR(17) NOT NULL,
VAR2 DECIMAL(13, 0) NOT NULL,
VAR3 DATE NOT NULL,
VAR4 DECIMAL(7, 0) NOT NULL,
VAR5 CHAR(1) NOT NULL,
VAR6 CHAR(1) NOT NULL,
VAR7 DECIMAL(11, 0) NOT NULL,
VAR8 DECIMAL(7, 0) NOT NULL,
VAR9 CHAR(9) NOT NULL,
VAR10 DECIMAL(15, 2) NOT NULL,
VAR11 CHAR(2) NOT NULL,
VAR12 DATE NOT NULL,
VAR13 DECIMAL(9, 0) NOT NULL,
VAR14 DECIMAL(3, 0) NOT NULL,
VAR15 CHAR(1) NOT NULL,
VAR16 CHAR(1),
VAR17 DECIMAL(7, 0),
VAR18 DECIMAL(7, 0),
VAR19 CHAR(1) NOT NULL,
VAR20 CHAR(35) NOT NULL,
VAR21 CHAR(35) NOT NULL,
VAR22 CHAR(35) NOT NULL,
VAR23 CHAR(35) NOT NULL,
VAR24 CHAR(35) NOT NULL,
VAR25 CHAR(35) NOT NULL,
VAR26 CHAR(35) NOT NULL,
VAR27 CHAR(1) NOT NULL,
VAR28 CHAR(1) NOT NULL,
VAR29 CHAR(1) NOT NULL,
VAR30 CHAR(40) NOT NULL
) END-EXEC.
What is wrong with that code?
I googled for "unsupported VAR construction" and got no relevant hits.
How do I understand the messages coming out of esqlOC? Is there some reference or technique to debug it?
Original code is from DB2 and the target is postgres.
Just a note: Sergey just updated esqlOC switching to version 3 [contrib:r976], you may want to recheck if there are any differences and not ask @ska00 for help (at least more helpful error messages).
Related
Commit: [r976]
Thanks Simon, sorry for the delayed response on this.
We just tested with esqlOC v3.0 and we still get the same "unsupported VAR
construction in DECLARE SECTION:" error when compiling. Other research
suggests that esqlOC should be treating "DECLARE SECTION" as a comment as
it is DB2 mainframe specific. Thanks for any insight and help with this.
-Jim P.
On Tue, Nov 9, 2021 at 11:06 AM Simon Sobisch sf-mensch@users.sourceforge.net wrote:
Related
Commit: [r976]
Progress! Looks like there is a missing test for ' cl.sqlaction != 12 ',
the attached patch fixes the problem.
On Wed, Jan 12, 2022 at 10:15 PM Jim Popovitch coboljim@users.sourceforge.net wrote:
Related
Commit: [r976]
Fixed [r993].
Related
Commit: [r993]
Thank you Sergey.
On Sat, Jan 15, 2022 at 3:41 PM Sergey Kashyrin ska00@users.sourceforge.net
wrote:
Related
Commit: [r993]