Lists supported and tested DBMSs along with the
Visual COBOL 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 version of
Visual COBOL supports the following Database Management Systems:
COBSQL (Pro*COBOL)
Back to Top
Before deploying a COBSQL application, be sure to install and configure all applicable third-party software.
Note: COBSQL (Pro*COBOL) is supported for native COBOL only.
- Availability
-
Feature/Platform
|
32-bit
|
64-bit
|
x86-64 running Red Hat Linux
|
X
|
X
|
x86-64 running SUSE Linux
|
X
|
X
|
IBM System p running AIX
|
X
|
X
|
IBM System z running Red Hat Linux
|
X
|
X
|
IBM System z running SUSE Linux
|
X
|
X
|
Itanium running HP-UX
|
X
|
X
|
x86-64 running Solaris
|
X
|
X
|
SPARC running Solaris
|
X
|
X
|
- 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.
- Certification of RDBMS Precompilers for Native COBOL
- Certification of RDBMS precompilers with
Micro Focus products is the responsibility of the RDBMS vendor, rather than
Micro Focus. Certification information can be found within the relevant Oracle documentation. If you have an
Oracle MetaLink account, document # 43208.1 provides details of all language compilers certified by Oracle for use with their precompilers.
- Preprocessors
- COBSQL supports the following database preprocessors:
- Oracle Pro*COBOL versions 18c and 19c database preprocessors
- Sybase Open Client Embedded SQL/COBOL Version 11.1 or later
- Informix Embedded SQL/COBOL Version 7.3 or later
- Compiling
- On x86 and x86-64 platforms, when compiling with COBSQL for use with Oracle, do not use the COBSQL directive option NOMAKESYN,
since this directive results in COMP host variables, and on Intel platforms these are incompatible with the native byte order
expected by Oracle.
- Testing
- For this version, COBSQL was tested with Oracle Pro*COBOL versions 18c and 19c.
- Executing
- On HP-UX, to execute an application precompiled using Pro*COBOL (or COBSQL) after you have created a callable shared object
of Oracle DBMS routines, you need set an environment variable, LD_PRELOAD, to point to the Oracle client callable shared object,
for example:
LD_PRELOAD=$ORACLE_HOME/lib/libclntsh.so
export LD_PRELOAD
A script is available that creates an executable run-time system or a callable shared object containing Oracle support. You can find the script in the Micro Focus Knowledge Base article titled
Building and executing Pro*COBOL applications on UNIX.
DB2 ECM
Back to Top
Before
developing or
deploying
a DB2 ECM application, be sure to install and configure all applicable third-party software.
Note: DB2 ECM is supported for native COBOL only.
- Availability
-
Feature/Platform
|
32-bit
|
64-bit
|
x86-64 running Red Hat Linux
|
X
|
X
|
x86-64 running SUSE Linux
|
X
|
X
|
IBM System p running AIX
|
X
|
X
|
IBM System z running Red Hat Linux
|
X
|
X
|
IBM System z running SUSE Linux
|
X
|
X
|
Itanium running HP-UX
|
|
X
|
x86-64 running Solaris
|
|
|
SPARC running Solaris
|
X
|
X
|
PowerLinux LE running Red Hat Linux
|
|
X
|
PowerLinux LE running SUSE Linux
|
|
X
|
- 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.
- Certification of RDBMS Precompilers for Native COBOL
- Certification of RDBMS precompilers with
Micro Focus products is the responsibility of the RDBMS vendor, rather than
Micro Focus. You can find IBM document certification information for DB2/COBOL applications within the IBM Information Center for DB2,
in the topic
Support for database application development in COBOL.
- Preprocessor
- DB2 ECM supports the following database preprocessors:
- IBM DB2 LUW Version 10.5 or later
- IBM DB2 Connect Version 10.5 or later
- Testing
- For this version,
DB2 ECM was tested with
DB2 LUW
10.5 and 11.1, and 11.5
OpenESQL
Back to Top
Before
developing or
deploying an OpenESQL application, be sure to install and configure all applicable third-party software.
- Availability
-
Feature/Platform
|
Native and JVM COBOL 32-bit
|
Native and JVM COBOL 64-bit
|
x86-64 running Red Hat Linux
|
X
|
X
|
x86-64 running SUSE Linux
|
X
|
X
|
x86-64 running Solaris
|
X
|
X
|
IBM System p running AIX
|
X
|
X
|
IBM System z running Red Hat Linux
|
X
|
X
|
IBM System z running SUSE Linux
|
X
|
X
|
Itanium running HP-UX
|
X
|
X
|
SPARC running Solaris
|
X
|
X
|
PowerLinux LE running SUSE Linux
|
|
X
|
PowerLinux LE running Red Hat Linux
|
|
X
|
- XA Switch Module
- When the Enterprise Server feature is enabled, the
ODBC One-phase Commit, SQL Server, and PostgreSQL
(early adopter program) switch modules are provided and available on the same platforms as are indicated in the
Availability section above.
The PostgreSQL switch module
(early adopter program) is available on the following
platforms:
- x86-64 running Red Hat Linux
- x86-64 running SUSE Linux
- 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
- 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 10.5
DB2 LUW 11.1
DB2 LUW 11.5
|
db2jcc4.jar (and
db2jcc_license_cu.jar)
|
Oracle 18C and 19c
|
ojdbc7.zip1
|
Microsoft SQL Server 2014
Microsoft SQL Server 2016
Microsoft SQL Server 2017
Microsoft SQL Server 2019
|
sqljdbc4.jar
|
EDB PostgreSQL 10.5 and 11.x
|
postgresql-42.0.0.jre7.jar
|
1Some Oracle JDBC drivers are distributed as
.zip rather than
.jar files.
|
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 this documentation set for instructions on downloading, installing, and configuring the open source JNDI server
Simple-JNDI for this purpose.
- Testing
- For this version, OpenESQL was tested
with the following:
- Oracle 18c and 19c
- DB2 LUW 10.5, 11.1, and 11.5
- SQL Server 2017 and 2019
- PowerLinux LE using DB2 LUW 10.5 only
- EDB PostgreSQL 10.5 and
MySQL 5.7 (5.3 ODBC drivers only) on the following platforms:
- x86-64 running Red Hat Linux
- x86-64 running SUSE Linux
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.