Gabor Markon

Thanks, I prefer Iron Spring's PL/I. It is a fair "F/G" level implemantation.

Perhaps I have landed in the wrong discussion. I mean this tool: esqlOC by Sergey.

Thanks, agree. IBM's PL/I is a full++ implementation of the PL/I standard.

Is it possible to extend the program to PL/I? The input SQL is only minimally different from COBOL. The parsing may of course be a tougher nut to crack.

Hello, sorry for the late answer. I try recently to use the OCIDE as Simon proposed. It seems to work fine with the preprocessor, but the generated code has a couple of errors which I must to check. Am Sa., 15. Mai 2021 um 17:04 Uhr schrieb Vincent (Bryan) Coen vcoen@users.sourceforge.net: Is this bug for the PG manual now finished ? If not what exactly is required to go into the manual replace what and where ? [bugs:#673] https://sourceforge.net/p/gnucobol/bugs/673/ bug in CALL-CONVENTION and CALL...

I use OpenCobol IDE 4.7.6 to compile the Db2 sample program "cblsql2" under Windowx 10. Before compiling, I generate the proper COBOL source by using Db2 "prep", which I include then as input in the IDE. I get the same errors as James: " C:\Users\pc\AppData\Local\Temp\cob19424_0.o:cob19424_0.c:(.text+0x251): undefined reference to sqlgstrt' C:\Users\pc\AppData\Local\Temp\cob19424_0.o:cob19424_0.c:(.text+0x3b8): undefined reference tosqlgaloc' ... " I use following GCC: C:\progs\OpenCobolIDE\GnuCOBOL\bin>gcc...

Hello Bruce, issues 1. (Java application does not interpret the hyphen "-" as a part of the field name) and 2. (field names will be not delivered in the loop in the sequence defined in the copybook ) are clear now, thanks. As for JZOS: I'll try to implement your suggestion in the next time. Regards Gabor

Hello Bruce, thanks for the prompt answer, I will try asap, and let you know. Regards Gabor Am Fr., 13. März 2020 um 14:35 Uhr schrieb Bruce Martin bruce_a_martin@users.sourceforge.net: Firstly it would be better to use the JRecordInterface1.COBOL.newIOBuilder(>>) interface. It seems the Java application does not interpret the hyphen "-" as a part of the field name. Rather the name will be cut at "-" and only the part after ("FT", "POS"...) will be delivered by the code line "entry.getKey()". Depends...