In COBOL it is common that an FD contains one or more OCCURS clauses, a concept that doesn't exist in a relational data base. When we migrate from an indexed file system to a relational data base, using isCOBOL Database Bridge; this could cause... Read More
RDBMS
Question: I installed Microsoft SQL Server, but I can't find the SQL Server JDBC Driver. Where is it located? Answer: Visit the Microsoft SQL Server JDBC Driver home page at https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft... Read More
isCOBOL needs the proper JDBC driver to interact with any RDBMS, including Oracle. JDBC drivers are Java libraries (jar) that are usually supplied by the RDBMS vendor. Each RDMBS has its own drivers. Oracle has several different types of drivers,... Read More
isCOBOL supports Postgres (PostgreSQL) in two ways: Through a built-in COBOL/ESQL compiler which translates EXEC SQL statements to JDBC Through isCOBOL ESQL Generator which creates bridge programs that route COBOL indexed file I/O statements to... Read More
isCOBOL has several options to access any RDBMS like MS SQL, Oracle, DB/2, MySQL, PostgreSQL, and any other RDBMS that provides a JDBC driver. You can access these databases with ESQL. The isCOBOL runtime comes with a robust SQL processor. If you... Read More
This is usually caused by having 'sqljdbc' and 'sqljdbc4.jar' in your CLASSPATH or the %ISCOBOL%/lib directory. You only need the sqljdbc4.jar. You should delete the sqljdbc.jar. Here is a link to Microsoft's documentation that... Read More
To use Pro*COBOL, compile with the isCOBOL -cp option to enable full POINTER support. This is necessary because the Pro*COBOL precompiler translates EXEC SQL statements to a C API that passes COBOL data as pointers and saves them internally to be... Read More