Lists supported and tested DBMSs along with the
Enterprise 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
OpenText Support for Micro Focus Products for availability of Extended Support Plus options.
- Encourages you to include third-party RDBMS consideration when planning an upgrade to your
Enterprise Server
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
Enterprise 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
|
|
|
- XA Switch Module
-
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:
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
|
COBOL 32-bit
|
COBOL 64-bit
|
PL/I 32-bit
|
PL/I 64-bit
|
x86-64 running Windows
|
|
|
|
|
- XA Switch Module
-
The DB2 XA switch module is provided and is available on the same platforms as are indicated in the
Availability section above.
- Host Compatibility Option (HCO)
- Host Compatibility Option requires that you have one of the following software products installed and configured:
- IBM DB2 Connect - Personal, Enterprise, Application Server or Unlimited Edition
- IBM DB2 LUW - Workgroup or Enterprise Server Editions including Advanced versions
- IBM DB2 LUW - Express or Express-C Edition
- IBM Data Server Client (assumes installation of a remote DB2 LUW Server product)
- Supported/tested versions
- For this release,
HCO for DB2 LUW was tested with
versions 11.1 and 11.5.
HCO for SQL Server (HCOSS)
Back to Top
Before
deploying an HCOSS application, be sure to install and configure all applicable third-party software.
- Availability
-
Operating System/Platform
|
COBOL native
32-bit
|
COBOL native
64-bit
|
PL/I 32-bit
|
PL/I 64-bit
|
x86-64 running Windows
|
|
|
|
|
- Database Migration
-
- HCOSS Client Host node
-
- SQL Server 2016 or later
- Microsoft .NET Framework 4.7.2
- Microsoft SQL Server Integration Services - available with the Microsoft SQL Server edition
Note: Microsoft SQL Server Express edition might not support SSIS. See your Microsoft documentation for details.
- Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)
Note: Microsoft recommends MSOLEDBSQL only, as all other versions are deprecated or are no longer maintained. However, if MSOLEDBSQL
is not installed, SQL Server Native Client (SNAC) is used if available.
- Microsoft OLE DB Provider for DB2 version 5.0 or later
Notes:
- Be sure to configure the OLE DB Provider to connect to the mainframe. See your Microsoft documentation for details.
- When using Microsoft OLE DB Provider for DB2 version 6.0, set the
Extract Schema Cast STATEMENT column to VARCHAR during SysViews extract option.
- SQL Server Target Host node
- SQL Server 2016 or later
- Mainframe DB2
- IBM-supported z/OS DB2 versions only
Note: If you intend to develop applications on your local machine, but deploy applications to a SQL Server database on a remote
machine, configure the remote machine using the requirements listed in the
Deploying Native Applications > Deployment Machine section later in this topic.
- Application Migration
-
- ADO.NET applications
- ADO.NET applications require SQL Server 2016 or later and SqlClient Data Provider in .NET Framework 4.x
Note: Microsoft recommends .NET Framework 4.5.2
- COBOL Stored Procedures
- See the requirements specified in
COBOL SQL Server Stored Procedures.
- Deploying Native Applications
-
- Development Machine
- Install SQL Server
2016 or later, along with its recommended Microsoft ODBC driver version.
- Development SQL Server Machine
- SQL Server
2016 or later.
Note: This can be the same machine as the development machine, but is not required to be.
- Deployment Machine
-
- Install
Enterprise Server or
Enterprise Test Server
- Install SQL Server
2016 or later, along with its recommended Microsoft ODBC driver version.
If you want to bind your application from the deployment machine, install the following additional software:
- Microsoft .NET 4 framework, or later
- SQL Server 2016 or later System CLR Types
- SQL Server 2016 or later Shared Management Objects
- Deployment SQL Server Machine
- SQL Server
2016 or later
Note: This can be the same machine as the deployment machine, but is not required to be.
- Supported/tested versions
- For this release, HCO for SQL Server was tested with SQL Server 2016, 2017, 2019, Azure DB, and Azure MI. Both SQL Server
2017 and 2019 were tested on Windows and Linux platforms.
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
|
PL/I 32-bit
|
PL/I 64-bit
|
x86-64 running Windows
|
|
|
|
|
- XA Switch Module
-
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
and PL/I
-
- 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 13.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
Enterprise Developer documentation for instructions on downloading, installing, and configuring the open source JNDI server Simple-JNDI for this purpose.
- SQL CLR Integration
- The following software is required to use the SQL CLR integration feature, which is specifically for the development and deployment
of COBOL stored procedures under Microsoft SQL Server. This feature is available for projects created using the SQL Server
Database Project template, which becomes available after installing the
ASP.NET and web development tools feature from the Visual Studio IDE (see
To install missing features from the IDE for details).
Projects based on the SQL Server Database Project template require:
- Microsoft SQL Server Tools (SSDT SDK)
- Any of the following:
|
Target
|
Version
|
Microsoft Recommendation
|
SQL Server 2016 and later
|
.NET Frameworks 4.x
|
CLR v4.0-based
|
Review the latest Microsoft recommendations to select an appropriate .NET Framework.
|
SQL Azure Database (option 1)
|
.NET Frameworks (2.0, 3.0, 3.5)
|
CLR v2.0-based
|
Review the latest Microsoft recommendations to select an appropriate .NET Framework.
|
SQL Azure Database (option 2)
|
.NET Frameworks 4.x
|
CLR v4.0-based
|
Review the latest Microsoft recommendations to select an appropriate .NET Framework.
|
If you are accessing Microsoft SQL Server from a remote machine, install the same
Enterprise Developer or
Enterprise Server version on the remote Microsoft SQL Server machine as you have running on your local machine. For additional information,
see
SQL Server COBOL Stored Procedures .
Important: The SQL CLR Database project template available in previous versions of
Enterprise Developer is no longer supported. Projects based on the SQL CLR Database project template are automatically upgraded to use the SQL
Server Database project template when opened in
Enterprise Developer
for Visual Studio 2022 .
- 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 13.x, 14.x, and 15.x
- Amazon AWS Aurora and RDS for PostgreSQL 13.x, 14.x, and 15.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.