Additional Software Requirements on Windows

Application server support for JVM COBOL

Back to Top

The following application servers are supported using the following JDKs:

You need Oracle's JDK. The earliest supported release of Oracle's JDK 1.7 is 1.7.027. You can download Oracle's JDK from Oracle's Web site.

Application server JCA support for Enterprise Server

Back to Top

Java EE 5 and Java EE 6 are supported for the deployment of EJBs generated using the Interface Mapping Toolkit, as follows:

• Java EE 5 includes support for EJB 3.0 and Java Connector Architecture 1.5
• Java EE 6 includes support for EJB 3.1 and Java Connector Architecture 1.6

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

AppMaster Builder Distributed Generation Server

Back to Top

IBM WebSphere MQ version 7 and later.

Java Development Kit (JDK)

Back to Top

Native COBOL and Java Interoperability

Oracle's Java Platform, Enterprise Edition (Java EE) 7 or Java 8 is required to run the Eclipse IDE, to execute COBOL JVM code and for native COBOL and Java interoperability. The setup file installs Java 8 u51 32-bit. You can download Oracle's Java EE from Oracle's Web site and install it anywhere on your machine.

Compiling Java

Either the IBM or the Oracle Java Development Kit (JDK), version 1.5 or later, is required for compiling Java.

Interface Mapping Toolkit (IMTK)

Restriction: This feature applies only when the Enterprise Server feature is enabled.

The JDK is required for generating Java interfaces from the Interface Mapping Toolkit or the imtkmake command.

Java Beans

Your Java client needs to be compiled with JDK 1.6 or greater.

EJBs

Use the same JDK vendor and version that is used by the application server.

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

Consolidated Trace Facility

Back to Top

• The Microsoft .NET Framework 2.0 or later is required for the CTF Viewer. It is available from the Microsoft .NET downloads area.

Database Access

Back to Top

Before you can use Enterprise Developer to develop and deploy SQL applications that use COBSQL, HCO for DB2 LUW, HCO for SQL Server (HCOSS), SQL Option for DB2, or OpenESQL, ensure any third-party software prerequisites are installed and the environment is set properly.

Database Access - COBSQL (Pro*COBOL)

Back to Top

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:

• Sybase Open Client Embedded SQL/COBOL Version 11.1 or later
• Oracle Pro*COBOL Version 11.1 (11gR1) 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 11.1, 11.2, and 12.1.

Database Access - OpenESQL

Back to Top

Availability

Feature/Platform	Native and JVM Managed COBOL 32-bit	Native and JVM Managed 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 switch module is provided and is available on the same platforms as are indicated in the Availability section above. The SQL Server XA switch module is also provided.

To build the SQL Server XA module, you must have the Windows Software Development Kit (SDK) installed for your version of Windows.

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

JVM Managed 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 9.5 DB2 LUW 9.7 DB2 LUW 10.1 DB2 LUW 10.5	db2jcc4.jar (and db2jcc_license_cu.jar)
Oracle 11.1, 11.2 Oracle 12.1	ojdbc6.zip1 ojdbc7.zip1
Microsoft SQL Server 2008 R2 Microsoft SQL Server 2012 Microsoft SQL Server 2014	sqljdbc4.jar2
PostgreSQL 9.4
1Some 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 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:

• Oracle 11.1, 11.2 and 12.1
• DB2 LUW 9.5, 9.7,10.1,10.5
• SQL Server 2008 R2, 2012, 2014
• PostgreSQL 9.4

Note: Micro Focus provides compatibility for PostgreSQL but does not directly contribute to or support the PostgreSQL open source project. Any issues relating to PostgreSQL functionality should be addressed through an open source support vendor.

Database Access - HCO for DB2 LUW

Back to Top

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 9.5 or later
• IBM DB2 Connect Version 9.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 DB2 LUW 9.5, 9.7, 10.1, and 10.5.

HCO for SQL Server (HCOSS)

Back to Top

Microsoft SQL Server

SQL Server 2008 R2 or later, Developer or Enterprise Editions, including Microsoft SQL Server Management Studio.

Database Migration

• Microsoft .NET Framework 4.0
• Microsoft OLE DB Provider for DB2, available in the SQL Server 2008 R2 or later Feature Pack
  Note: Be sure to configure the OLE DB Provider to connect to the mainframe. See your Microsoft documentation for details.
• Mainframe DB2

Note:

• 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, you can install SQL Server Native Client 10.x (or later) for ODBC connectivity on your local machine instead of installing SQL Server. For SQL Server 2014 connectivity, you can install Microsoft ODBC Driver 11.0 for SQL Server. For information on configuring a deployment machine, see the section Deploying Native Applications below.

Deploying Native Applications

Development Machine

• Enterprise Developer for Eclipse
• If SQL Server 2008 R2 or 2012 is not installed, you must have Microsoft SQL Server 2008 R2 or 2012 Native Client installed. For SQL Server 2014, you must have Microsoft ODBC Driver 11.0 for SQL Server.

Development SQL Server Machine

SQL Server 2008 R2 or later

Note: This can be the same machine as the development machine, but is not required to be

Deployment Machine

• Enterprise Server or Enterprise Test Server installed
• If SQL Server 2008 R2 or 2012 is not installed, you must have Microsoft SQL Server 2008 R2 or 2012 Native Client installed. For SQL Server 2014, you must have Microsoft ODBC Driver 11.0 for SQL Server.

If you want to bind your application from the deployment machine, install the following software in addition:

• Microsoft .NET 3.5 framework, or later
• SQL Server 2008 R2 or later System CLR Types
• SQL Server 2008 R2 or later Shared Management Objects

Deployment SQL Server Machine

SQL Server 2008 R2 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 2008 R2, 2012, and 2014.

SQL Option for DB2

Back to Top

XA Switch Module

XDB XA switch modules are provided and are available for the Windows x86-64 32-bit platform.

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

IBM WebSphere MQ version 7 and later.