Additional Software Requirements on Windows

To ensure full functionality for some Enterprise Developer features, you might be required to obtain and install additional third-party software in addition to the prerequisite software installed automatically by the Enterprise Developer setup file. The following information specifies the third-party software required for each feature.

.NET Core

Back to Top

.NET Core SDK

You must have installed .NET Core SDK 2.1 or later before you can use Enterprise Developer to build a COBOL application for use with .NET Core. Installing Visual Studio's ".NET Core cross-platform development" component installs .NET Core SDK 2.1.

If you want to publish COBOL applications to work with a versions of .NET Core other than 2.1 you can download and install the relevant versions of the .NET Core SDK. See Microsoft: .NET Downloads for more information.

Visual Studio

You must be using Visual Studio 2017 version 15.9 or later to be able to develop and publish a COBOL application for use on .NET Core.

In addition, you must have installed a version of the .NET Core SDK. You can install .NET Core SDK 2.1 by installing Visual Studio's ".NET Core cross-platform development" component. If you do not have this component installed you can install it from Visual Studio by clicking Help > Micro Focus Product Help > Install Missing Feature(s) > .NET Core development .

Application Server JCA support for Enterprise Server

Back to Top

Java EE 7, including support for EJB 3.2 and Java Connector Architecture 1.7, is supported for the deployment of EJBs generated using the Interface Mapping Toolkit.

The following Java application servers are supported using the following JDKs:

Application Servers JDK (vendor) Java EE COBOL RA CICS RAs and ECI
JBoss EAP 7.1.4 1.8 (Oracle)

1.8 (AdoptOpenJDK)

7 X X
Oracle WebLogic 12.2.1 1.8 (Oracle) 7 X
IBM WebSphere 9.0 1.8 (IBM) 7 X
Tomcat 9.0.x* 1.8 (AdoptOpenJDK)
*Apache Tomcat is an HTTP server and servlet container supporting Java Servlet and JavaServer Pages (JSP). Micro Focus Tomcat non-transactional support includes servlet generation with J2SE Beans; no transactional support is provided. Tomcat does not support the use of Enterprise Java Beans (EJBs) or resource adapters (RAs).

Please consult your Application Server documentation to determine which JDK you should use. The JDK is used to:

  • Start the Application Server
  • Compile EJBs and Servlets generated by the Interface Mapping Toolkit or the imtkmake command

After installing the JDK, you need to set up your Java environment.

CICS Web Services

Back to Top

To use CICS Web Services, you must first install the IBM CCSID conversion tables. See CCSID Conversion Tables for details.

Code Analysis

Back to Top

Apache Ant is required to perform code analysis from the Enterprise Developer command line. You can download Apache Ant from Apache's Web site.

COBOL on Microsoft Azure

Back to Top

This release supports the Microsoft Azure SDK version 3.0.

Microsoft Azure requires that you install some additional software. See the Microsoft Microsoft Azure Web site for a full list of the required software.

Database Access - 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 Windows X X
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.
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 Version 12.2 and 18c 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 version 12.2.

Database Access - HCO for DB2 LUW

Back to Top

Before developing or deploying an HCO for DB2 LUW application, be sure to install and configure all applicable third-party software.

Note: HCO for DB2 LUW is supported for native COBOL only.
Availability
Feature/Platform Native COBOL 32-bit Native COBOL 64-bit PL/I 32-bit PL/I 64-bit
x86-64 running Windows X X X X
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.
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
HCO for DB2 LUW supports the following database preprocessors:
  • IBM DB2 LUW Version 10.5 or later
  • IBM DB2 Connect Version 10.5 or later
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)
Testing
For this version, HCO for DB2 LUW was tested with versions 10.5 and 11.1.

Database Access - HCO for SQL Server (HCOSS)

Back to Top

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

Availability
Feature/Platform 32-bit 64-bit
x86-64 running Windows X X
Database Migration
  • SQL Server 2012 or later, any edition
  • Microsoft .NET Framework 4.0
  • 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 Provider for DB2 version 5.0 or later
    Notes:
    • Microsoft OLE DB Provider for DB2 version 6.0 does not currently work with HCOSS. If you require further information, contact Micro Focus SupportLine.
    • Be sure to configure the OLE DB Provider to connect to the mainframe. See your Microsoft documentation for details.
  • Mainframe DB2
Notes:
  • We support only the mainframe DB2 versions that are currently under IBM support.
  • 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 below.
Application Migration
ADO.NET applications
ADO.NET applications require either of the following combinations:
  • SQL Server 2008 R2 and SqlClient Data Provider in .NET Framework 3.5
    Note: Microsoft recommends .NET Framework 3.5.1
  • SQL Server 2012 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 SQL Server COBOL Stored Procedures.
Deploying Native Applications
Development Machine
Install SQL Server 2012 or later, along with its recommended Microsoft ODBC driver version.
Development SQL Server Machine
SQL Server 2012 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 2012 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 2012 or later System CLR Types
  • SQL Server 2012 or later Shared Management Objects
Deployment SQL Server Machine
SQL Server 2012 or later
Note: This can be the same machine as the deployment machine, but is not required to be.
Testing
For this version, HCO for SQL Server was tested with SQL Server 2012, 2014, 2016, and 2017.

Database Access - Mainframe Batch Database Tools (MBDT)

Back to Top

Availability
Feature/Platform 32-bit 64-bit
x86-64 running Windows X X
OpenESQL
The MBDT toolset consists of OpenESQL applications, and are native code using ODBC. Please see the Database Access - OpenESQL section for further details.
Testing
For this version, MBDT was tested with:
  • DB2 LUW 10.5
  • Oracle 12.2
  • SQL Server 2012

Database Access - 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 .NET COBOL 32-bit Native and .NET COBOL 64-bit PL/I 32-bit PL/I 64-bit
x86-64 running Windows X X X X
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
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)
  • Visual Studio 2017 or later Professional, Enterprise or Community Edition
  • Any of the following:
    Target Version Microsoft Recommendation
    SQL Server 2012 and later .NET Frameworks 4.x CLR v4.0-based .NET Framework 4.5.2
    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

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 2019.
Testing
For this version, OpenESQL was tested with:
  • Oracle 12.2 and 18c
  • DB2 LUW 10.5 and 11.1
  • SQL Server 2012, 2014, 2016, and 2017
  • EDB PostgreSQL 10.5
  • MySQL 5.7 (5.3 ODBC drivers only)
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.
Planned
Support for the following is planned for future release:
  • Azure SQL Database (Managed Instance)
  • Azure SQL Database (Logical server)
  • Amazon Aurora PostgreSQL-Compatible Edition

Database Access - SQL Option for DB2

Back to Top

Availability
Feature/Platform 32-bit
x86-64 running Windows X
XA Switch Module
XDB XA switch modules are provided and are available for the Windows x86-64 32-bit platform.

Deployment - running . NET COBOL applications from a network server

Back to Top

For .NET COBOL applications that you run from a network server, the server must have the Microsoft .NET Framework version 4.5.2 or later and the Microsoft Visual C++ 2017 Redistributable Runtime installed.

Enterprise Server for .NET

Back to Top

  • Microsoft .NET Framework 4.0
  • Microsoft SQL Server 2008 R2 or later. For beta or development installations, SQL Server Express 2008 R2 is sufficient.

    You can download Microsoft's SQL Server from http://www.microsoft.com/sqlserver/en/us/get-sql-server/try-it.aspx.

  • A TN3270 terminal emulator. Micro Focus Rumba+ Desktop is supplied with this product.
Note: You also need to enable IIS and some additional Windows features. Read the Quick Start section in your Enterprise Server for .NET help for further instructions on how to set up your operating environment.

Interface Mapping Toolkit (IMTK)

.NET client generation for Service Interfaces requires Visual C++, which is an optional feature of Visual Studio 2015 and later. To ensure that Visual C++ is installed with Visual Studio, you must do a custom installation of Visual Studio, and specifically choose the Visual C++ option.

Java Development Kit (JDK)

Back to Top

For COBOL JVM code and Java Interoperability, Java 8 (32 or 64-bit versions), and Java 11 (64-bit version only) are supported. Alternatively, you can download AdoptOpenJDK's OpenJDK 8 with Hotspot from AdoptOpenJDK's Web site and unpack the archive anywhere on your machine.
Note: Eclipse does not run using Java 11.

JCL Support - DSNREXX

Back to Top

Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability; however, this feature is not intended for production use and it is not supported as such.
Availability
Feature/Platform 32-bit 64-bit
x86-64 running Windows X X
OpenESQL
DSNREXX is supported in OpenESQL applications, and is native code using ODBC. See the Database Access - OpenESQL section in this topic for additional software requirements, and the DSNREXX Support topics for complete details.
Testing
For this version, DSNREXX was tested with:
  • DB2 LUW 10.5
  • SQL Server 2012

Mainframe Access - Endevor Support

Back to Top

  • To use the Mainframe Access support for Endevor you must be using Endevor R14 or later. CA stabilized the Endevor API at R14, so if you upgrade from R14 to a later version you will not need to update the support module that Mainframe Access uses.

Micro Focus Rumba

Back to Top

  • On Windows 8, in order to install Micro Focus Rumba you must have the Microsoft .NET Framework 3.5 Service Pack 1 installed.

WebSphere MQ

Back to Top

This product supports IBM WebSphere MQ version 7 and later.

Windows Forms

Back to Top

  • Microsoft Visual Studio is required for using the Interface Mapping Toolkit (IMTK) to generate Windows Forms and ASP.NET Web site test clients.
  • Microsoft Internet Information Service (IIS) is also required for generating Windows Forms test clients.