Gnucobol, Visual Studio code, SuperBOL Studio and database

[celsofigueiredo]

Prezados.
Sou usuário bem básico para gnucobol e VS code e SuperBOL Studio. Ainda estou me ambientando com o VS. Pergunto: Como usar um banco de dados com gnucobol e superBOL?
Dear all.
I am a very basic user of gnucobol, VS code and SuperBOL Studio. I am still getting used to VS. I have a question: How do I use a database with gnucobol and superBOL?
Celso.

[engboris]

Hello Celso.

What do you mean by using a database? Do you mean using EXEC SQL statements in your COBOL programs? If that's what you meant, you need to use a SQL preprocessor.
For instance, you can use GixSQL : https://github.com/mridoni/gixsql which supports PostgreSQL, MySQL/MariaDB, Oracle, SQLite and ODBC. It is is independent from VSCode and SuperBOL Studio.

[celsofigueiredo]

Dear Boris Eng. Sim, é isso mesmo, mas já tentei usar o GixSQL, e não obtive sucesso, por isso perguntei na lista. Vou tentar usar novamente, mas não tenho muitas informações de como usar e configurar. Como eu já disse, sou um zero a esquerda em relação a configurar qualquer coisa. Yes, that's right, but I've already tried using GixSQL, and I wasn't successful, so I asked on the list. I'll try to use it again, but I don't have much information on how to use and configure it. As I said, I'm a complete zero when it comes to configuring anything. Celso. Em qui., 13 de fev. de 2025 às 07:42, Boris Eng ***@***.***> escreveu:

…

Hello Celso. What do you mean by using a database? Do you mean using EXEC SQL statements in your COBOL programs? If that's what you meant, you need to use a SQL preprocessor. For instance, you can use GixSQL : https://github.com/mridoni/gixsql which supports PostgreSQL, MySQL/MariaDB, Oracle, SQLite and ODBC. — Reply to this email directly, view it on GitHub <#404 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADS6UV27Q5XJB7D6K7CLBVL2PRZKZAVCNFSM6AAAAABXAVCPGGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJYGYYTQNI> . You are receiving this because you authored the thread.Message ID: <OCamlPro/superbol-studio-oss/repo-discussions/404/comments/12186185@ github.com>

[engboris]

Personally, I use PostgreSQL 14.15 and it works (I'm not sure about what versions are supported but maybe @emilienlemaire or @ddeclerck has an idea). You should be able to download it here: https://www.enterprisedb.com/downloads/postgres-postgresql-downloads and there is an install guide here: https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/windows/

[celsofigueiredo]

Prezado engboris.

Depois de varias tentativas, consegui instalar corretamente o postgresql e o pgadmin4, no windows 11, mas o GIX e o GIXSQL, consigo instalar mas não funciona corretamente (por isso desisti de usar o GIX). Agora tenho instalado o GnuCOBOL, o PostgreSQL e o Pgamin4. Falta instalar mais alguma coisa para começar a usar cobol com SQL?

Dear engboris,

After several attempts, I managed to correctly install postgresql and pgadmin4 on Windows 11, but I can install GIX and GIXSQL but they don't work properly (that's why I gave up using GIX). Now I have installed GnuCOBOL, PostgreSQL and Pgamin4. I still need to install something else to start using COBOL with SQL?

Celso.

[celsofigueiredo]

Dear engboris,

After racking my brains a bit, I managed to understand that I only need to use GixSQL. The entire set of programs is almost ready, that is, GnuCOBOL, Visual Studio code, superBOL, Database (postgreSQL). I understood that I have to use GixSQL as well. But how can I integrate and use gixSQL with the rest?
Celso.

[celsofigueiredo]

Dear users,

After many mistakes, I managed to install GixSQL, both on Windows and on Linux Debian 12. On Windows, I can call the executable from any location. On Linux Debian 12, I can only run the executable if I am in the same folder as the executable. How do I add the GixSQL path variable to Linux Debian 12?
Celso.

[engboris]

You have to call the preprocessor to transform the EXEC SQL statements of your program by using the gixpp command described here: https://github.com/mridoni/gixsql/blob/main/README.md#using-gixsql

Then you have to compile your program with cobc and add a -lgixsql flag.

You can test it on a simple COBOL program then you can tell me if you have errors.

[celsofigueiredo]

Dear Boris Eng. I am almost reaching the goal of integrating all these programs to run COBOL with SQL, both on Linux Debian 12 and Windows 11. Soon, I will tell you if I managed to reach this goal. Celso Em seg., 17 de fev. de 2025 às 18:13, Boris Eng ***@***.***> escreveu:

…

You have to call the preprocessor to transform the EXEC SQL statements of your program by using the gixpp command described here: https://github.com/mridoni/gixsql/blob/main/README.md Then you have to compile your program with cobc and add a -lgixsql flag. You can test it on a simple COBOL program then you can tell me if you have errors. — Reply to this email directly, view it on GitHub <#404 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADS6UV5GBLE6H2M3Z7CNZ732QJGGDAVCNFSM6AAAAABXAVCPGGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRSHEZDSNQ> . You are receiving this because you authored the thread.Message ID: <OCamlPro/superbol-studio-oss/repo-discussions/404/comments/12229296@ github.com>

[celsofigueiredo]

Dear Boris Eng.

I started trying to use gixpp, with the command: gixpp -e -S -I. -ext ".,.cpy,.CPY" -i TEST001.cbl -o TEST001.cbsql , it already gave an error, because the (-ext ".,.cpy,.CPY") does not exist. What is the correct way to compile.

Celso.

[engboris]

This was an example command. You don't necessarily need to use exactly those parameters (all the parameters of the gixpp command are described in the README file).

It should work with the two following commands:

gixpp -e -S -i ./prog.cbl -o prog.cbsql
cobc -x prog.cbsql -lgixsql

According to the GixSQL README file:

-e : preprocess for ESQL (mandatory for preprocessing)
-S: use static calls when emitting GixSQL library calls (this is the mode to be normally used)
-i and -o: input and output file paths

The extensions .cbl, .cob, .cbsql shouldn't be too important here.

Then you should finally be able to run your program!

[celsofigueiredo]

Dear engboris,

Thanks again. Your tips have helped me a lot, but I still have problems with the environment configuration. I also saw that there are two files (gixpp and gixsql). Which one should I use and what is the function of each one? I managed to install it on Windows, but I still get errors when I try to run it. On Linux Debian 12, I installed it in the folder (opt\gixsql\bin). Gixpp and gixsql are OK. Postgresql is OK, gnucobol is OK. I have a question about the environment variables. And also, what is the procedure to follow to connect to the Postgres database?

Celso.

[celsofigueiredo]

Dear Engboris,

After some more research, I managed to get to this point:
What is the procedure to follow?

celso@debian:~/cobolVSC/examples$ gixpp -e -S -I. -i TEST001.cbl -o TEST001.cbsql
celso@debian:~/cobolVSC/examples$ cobc -x TEST001.cbsql -L -llibgixsql
TEST001.cbsql: in paragraph 'GIXSQL-CI-P-TEST001-EMPTBL':
TEST001.cbsql:416: error: syntax error, unexpected Identifier
TEST001.cbsql: in paragraph '100-EXIT':
TEST001.cbsql:405: error: 'GIX-SKIP-CRSR-INIT' is not defined
celso@debian:~/cobolVSC/examples$ gixsql TEST001.cbl TEST001.cbsql -S -I.
celso@debian:~/cobolVSC/examples$ cobc -x TEST001.cbsql -L -llibgixsql
TEST001.cbsql: in paragraph 'GIXSQL-CI-P-TEST001-EMPTBL':
TEST001.cbsql:416: error: syntax error, unexpected Identifier
TEST001.cbsql: in paragraph '100-EXIT':
TEST001.cbsql:405: error: 'GIX-SKIP-CRSR-INIT' is not defined

[engboris]

Can you try with a simple COBOL code using EXEC SQL statements? Just to make sure that it works and that the problem is not elsewere (for instance in the COBOL code).

[celsofigueiredo]

Dear Engboris,
I don't know what to do anymore. Everything is up to date. I followed the instructions and it still gives an error.
Celso.

celso@debian:~$ gixpp --version
gixpp - the ESQL preprocessor for Gix-IDE/GixSQL
Version: 1.0.20b
libgixpp version: 1.0.20b

celso@debian:~$ cobc --version
cobc (GnuCOBOL) 3.2.0
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
Este programa é livre; ver a origem para condições de cópia.  NÃO existe
garantia; nem sequer para COMERCIALIZAÇÃO ou ADEQUAÇÃO A UM DETERMINADO FIM.
Written by Keisuke Nishida, Roger While, Ron Norman, Simon Sobisch, Edward Hart
Compilado em:  Jul 28 2024 07:01:00
Empacotado em: Jul 28 2023 17:02:56 UTC
C version "11.4.0"
celso@debian:~$ gixsql --version
gixpp - the ESQL preprocessor for Gix-IDE/GixSQL
Version: 1.0.20b
libgixpp version: 1.0.20b

celso@debian:~/cobolVC/examples$ cobc -x TSQL001A.cbsql -L -llibgixsql
/usr/bin/ld: /tmp/cob4199_0.o: na função "TSQL001A_":
cob4199_0.c:(.text+0x34f): referência não definida para "GIXSQLConnect"
/usr/bin/ld: cob4199_0.c:(.text+0x3f5): referência não definida para "GIXSQLStartSQL"
/usr/bin/ld: cob4199_0.c:(.text+0x4d3): referência não definida para "GIXSQLSetResultParams"
/usr/bin/ld: cob4199_0.c:(.text+0x57f): referência não definida para "GIXSQLExecSelectIntoOne"
/usr/bin/ld: cob4199_0.c:(.text+0x5a8): referência não definida para "GIXSQLEndSQL"
/usr/bin/ld: cob4199_0.c:(.text+0x6b7): referência não definida para "GIXSQLConnectReset"
collect2: error: ld returned 1 exit status
celso@debian:~/cobolVC/examples$ gixsql TSQL001A.cbl TSQL001A.cbsql -S -I.
celso@debian:~/cobolVC/examples$ cobc -x TSQL001A.cbsql -L -llibgixsql
/usr/bin/ld: /tmp/cob4232_0.o: na função "TSQL001A_":
cob4232_0.c:(.text+0x34f): referência não definida para "GIXSQLConnect"
/usr/bin/ld: cob4232_0.c:(.text+0x3f5): referência não definida para "GIXSQLStartSQL"
/usr/bin/ld: cob4232_0.c:(.text+0x4d3): referência não definida para "GIXSQLSetResultParams"
/usr/bin/ld: cob4232_0.c:(.text+0x57f): referência não definida para "GIXSQLExecSelectIntoOne"
/usr/bin/ld: cob4232_0.c:(.text+0x5a8): referência não definida para "GIXSQLEndSQL"
/usr/bin/ld: cob4232_0.c:(.text+0x6b7): referência não definida para "GIXSQLConnectReset"
collect2: error: ld returned 1 exit status
celso@debian:~/cobolVC/examples$ export PATH=$PATH:/opt/gix-ide/lib/x64/gcc
celso@debian:~/cobolVC/examples$ set DBNAME=pgsql://127.0.0.1:5432/postgres
celso@debian:~/cobolVC/examples$ set DBAUTH=postgres.postgres
celso@debian:~/cobolVC/examples$ cobc -x TSQL001A.cbsql -L -llibgixsql
/usr/bin/ld: /tmp/cob4316_0.o: na função "TSQL001A_":
cob4316_0.c:(.text+0x34f): referência não definida para "GIXSQLConnect"
/usr/bin/ld: cob4316_0.c:(.text+0x3f5): referência não definida para "GIXSQLStartSQL"
/usr/bin/ld: cob4316_0.c:(.text+0x4d3): referência não definida para "GIXSQLSetResultParams"
/usr/bin/ld: cob4316_0.c:(.text+0x57f): referência não definida para "GIXSQLExecSelectIntoOne"
/usr/bin/ld: cob4316_0.c:(.text+0x5a8): referência não definida para "GIXSQLEndSQL"
/usr/bin/ld: cob4316_0.c:(.text+0x6b7): referência não definida para "GIXSQLConnectReset"
collect2: error: ld returned 1 exit status

[celsofigueiredo]

Dear Engboris,

I've tried everything, but I think I'm missing something regarding environment variables: I tried to use a COBOL program with SQL, together with GixSQL and the result was the one below, where I'm going wrong.

D:\GixSQL\examples>cobc -x TSQL001A.cbsql -L -llibgixsql
D:/OpenCobolIDE/GnuCOBOL/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\Celso\AppData\Local\Temp\cob6880_0.o:cob6880_0.c:(.text+0x399): undefined reference to GIXSQLConnect' D:/OpenCobolIDE/GnuCOBOL/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\Celso\AppData\Local\Temp\cob6880_0.o:cob6880_0.c:(.text+0x439): undefined reference toGIXSQLStartSQL'
D:/OpenCobolIDE/GnuCOBOL/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\Celso\AppData\Local\Temp\cob6880_0.o:cob6880_0.c:(.text+0x509): undefined reference to GIXSQLSetResultParams' D:/OpenCobolIDE/GnuCOBOL/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\Celso\AppData\Local\Temp\cob6880_0.o:cob6880_0.c:(.text+0x5ba): undefined reference toGIXSQLExecSelectIntoOne'
D:/OpenCobolIDE/GnuCOBOL/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\Celso\AppData\Local\Temp\cob6880_0.o:cob6880_0.c:(.text+0x5e4): undefined reference to GIXSQLEndSQL' D:/OpenCobolIDE/GnuCOBOL/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\Celso\AppData\Local\Temp\cob6880_0.o:cob6880_0.c:(.text+0x6f4): undefined reference toGIXSQLConnectReset'

Celso

[emilienlemaire]

Hello Celso.

This might be helpful to resolve your problems on Debian:

gixpp -e -S -I /opt/gixsql/share/gixsql/copy -I . -i TSQL001A.cbl -o TSQL001A.cbsql
# Notice the new -I flag which indicate where to find the GIXSQL copybook

cobc -x TSQL0001A.cbsql -L /opt/gixsql/lib -lgixsql
# Notice the addition of `/opt/gixsql/lib` after `-L` and the suppression of `lib` after `-l`

With these changes you should be able to use gixsql everywhere where the binary is executable, and get rid of your errors.

If you'd like more informations, the cobc command failed because the -L flag expects a path and the -llibgixsql is interpreted as this path, so gnucobol does not look for the gixsql functions at the right place.

I think you could also try to run this command on Windows: cobc -x TSQL001A.cbsql -lgixsql (almost the same as before but without the -L.)

[celsofigueiredo]

Dear emilienlemaire.
I managed to get past the compilation part, but now when executing, I got the following error:

D:\GixSQL\examples>cobc -x TSQL001A.cbsql -lgixsql
D:\GixSQL\examples>TSQL001A.exe

---

DATASRC :
DB :
USER :

---

CONNECT SQLCODE: -0000000201

As I said before, I'm terrible at configuring. There's something else missing, but I don't know what it is.

Celso.

[celsofigueiredo]

Dear.
I managed to progress a little further, but I still have the error below:
attempt to reference invalid memory address (signal)
What's left to do.

Celso

[engboris]

Hello Celso. Are you sure it's a problem of configuration and not of the COBOL program? The best would be to try with the simplest program using EXEC SQL statements. Providing more information would also make it easier for us to help you.

[celsofigueiredo]

Dear engboris.

I'm using the examples that come with Gix-IDE and GixSQL. And I'm running and compiling them via the command line. Before, the program compiled with numerous errors, but now I've managed to compile without any errors. I think I'm making a mistake in the variables that I have to execute before the program (I think this is where I'm making a mistake). Then I run the program and it gives the error message from the previous message.
Would you have a very simple example of connecting to a database, with a step-by-step guide, so that I can see where I'm going wrong?

Celso.