Database Management Systems (DBMSs)

Lists supported and tested DBMSs along with the COBOL Server features that use them.

All RDBMS testing is done on both 32- and 64-bit platforms based on RDBMS client software availability.

With regard to support for each of these third-party RDBMS supported version, Micro Focus :

  • Provides support until the standard end-of-service (EOS) date provided by the RDBMS vendor
  • If your deployment requires support for a given RDBMS beyond the vendor's EOS dates, check with Customer Care for availability of Extended Support Plus options.
  • Encourages you to include third-party RDBMS consideration when planning an upgrade to your Micro Focus product

With regard to resolving reported issues with Micro Focus software while using a third-party RDBMS, Micro Focus :

  • Attempts to resolve issues for supported DBMSs on tested or untested platforms
  • Investigates issues involving planned but not yet supported RDBMSs, and attempts to resolve non-architectural issues that also occur in the latest supported RDBMS version

This release of COBOL Server supports the following Database Management Systems:

COBSQL (Pro*COBOL)

Back to Top

Note: COBSQL (Pro*COBOL) is supported for native COBOL only.

Before deploying a COBSQL application, be sure to install and configure all applicable third-party software.

Availability
Operating System/Platform 32-bit 64-bit
x86-64 running Windows Check mark Check mark
XA Switch Module
When the Enterprise Server feature is enabled, the Oracle XA switch module is provided for COBSQL (Pro*COBOL), and is available on the same platforms as are indicated in the Availability section above. Oracle Instant Client fully supports all 1PC functionality with Pro*COBOL applications.
Restriction: The Oracle Instant Client does not support the 2PC functionality of the Oracle XA switch module. To use 2PC functionality with Pro*COBOL applications, you must install Oracle Client, not Instant Client.
Supported/tested version
For this release, COBSQL was tested with Oracle Pro*COBOL versions 19c and 21c.
Planned support
Support for the following is planned for a future release:
  • Oracle 23c

DB2 ECM (non-mainframe) and HCO for DB2 LUW (mainframe)

Back to Top

Before deploying a DB2 application, be sure to install and configure all applicable third-party software.

Note: DB2 is supported for native COBOL only.
Availability
Operating System/Platform 32-bit 64-bit
x86-64 running Windows Check mark Check mark
XA Switch Module
When the Enterprise Server feature is enabled, the DB2 XA switch module is provided and is available on the same platforms as are indicated in the Availability section above.
Supported/tested versions
For this release, DB2 ECM was tested with DB2 LUW 11.1 and 11.5.

OpenESQL

Back to Top

Before deploying an OpenESQL application, be sure to install and configure all applicable third-party software.

Availability
Operating System/Platform COBOL native and .NET/JVM COBOL 32-bit 32-bit COBOL native and .NET/JVM COBOL 64-bit 64-bit
x86-64 running Windows Check mark Check mark
XA Switch Module
When the Enterprise Server feature is enabled, the ODBC One-phase Commit, SQL Server, and PostgreSQL switch modules are provided and available on the same platforms as are indicated in the Availability section above.
Native COBOL
  • OpenESQL supports access to relational databases using ODBC 3.0-compliant drivers
  • Refer to your driver vendor's documentation to determine whether your driver is suitable for use with OpenESQL
.NET COBOL
  • OpenESQL supports access to relational databases using compliant .NET framework drivers
  • OpenESQL has been tested against the following ADO.NET data providers:
    • Microsoft provider for SQL Server
    • Microsoft provider for Oracle
    • IBM DB2
    • Oracle Data Provider for .NET (ODP.NET) - fully managed and unmanaged providers
    • OleDb
    • Managed ODBC .NET providers
    • Npgsql 3.2.2 for EDB PostgreSQL
JVM COBOL
OpenESQL supports access to relational databases using JDBC 4.0-compliant JDBC drivers. The following table shows the tested DBMSs and their corresponding JDBC driver filenames:
Tested DBMS Versions JDBC 4.0 Compliant Drivers

DB2 LUW 11.1

DB2 LUW 11.5

db2jcc4.jar (and db2jcc_license_cu.jar )

Oracle 19c

Oracle 21c

ojdbc7.zip 1

Microsoft SQL Server 2016

Microsoft SQL Server 2017

Microsoft SQL Server 2019

sqljdbc4.jar 2
EDB PostgreSQL 11.x and later postgresql-42.0.0.jre7.jar
1 Some Oracle JDBC drivers are distributed as .zip rather than .jar files.

2 On Windows platforms, if you are not using Windows authentication, no additional resources are required. However, if you are using Kerberos authentication with a driver version of 4.0 or later, although integrated authentication is not required, you might need to follow additional configuration steps as described in the driver documentation. No additional resources are required for UNIX platforms.

To use JDBC DataSource Objects, you must also install and configure a JNDI server.

  • If you are using a Java application server, it includes a JNDI server you can use to configure DataSource objects. This process is described in the Java documentation for the application server.
  • If you are not using a Java application server, or if you require a standalone JNDI server to configure DataSource objects for initial evaluation and development, see the To install and configure Simple-JNDI topic in your Visual COBOL documentation for instructions on downloading, installing, and configuring the open source JNDI server Simple-JNDI for this purpose.
Supported/tested versions
For this release, OpenESQL was tested with:
  • Oracle 19c and 21c
  • DB2 LUW 11.1 and 11.5
  • SQL Server 2016, 2017, 2019, 2022, Azure DB, and Azure MI
  • Microsoft Azure SQL Database
  • Microsoft Azure SQL Managed Instance
  • PostgreSQL GDG community edition (early adopter program) and EDB PostgreSQL 12.x, 13.x, and 14.x
  • Amazon AWS Aurora and RDS for PostgreSQL 12.x, 13.x, and 14.x
  • MySQL 8.0
Note: Micro Focus provides compatibility for PostgreSQL and MySQL but does not directly contribute to or support either open source project. Any issues relating to the functionality of either DBMS should be addressed through an open source support vendor.