Platform Coverage

This document covers the following topics:

Scope of EntireX Version 9.9

This version of EntireX has been released on the following platforms:

  • z/OS

  • SUSE Linux Enterprise Server for IBM System z (64-bit)

  • Red Hat Enterprise Linux for IBM System z (64-bit)

  • Red Hat Enterprise Linux for Amazon EC2 (64-bit)

  • Solaris SPARC (64-bit)

  • HP-UX for Itanium 2

  • AIX Power (64-bit)

  • SUSE Linux Enterprise Server for AMD64 and EM64T (x86-64)

  • Red Hat Enterprise Server Linux for AMD64 and EM64T (x86-64)

  • Windows (32-bit, 64-bit)

Detailed information regarding supported operating system versions, General Availability (GA), platform retirement, End of Maintenance (EOM), and End of Sustained Support (EOSS) dates for your products can be found under Products & Documentation > Product Version Availability on Software AG's Empower website https://empower.softwareag.com.

Note:
Software AG provides EntireX support for the operating/teleprocessing system versions supported by their respective manufacturers. In general, when an operating/teleprocessing system provider stops supporting a version of an operating/teleprocessing system, Software AG will stop supporting that operating/teleprocessing system version.

List of Components per Platform

 

graphics/zos.gif

graphics/vse.gif

graphics/bs2.gif

graphics/zvm.gif

graphics/suseibmz.gif

graphics/redhatMf.gif

graphics/solaris.gif

graphics/hpuxItanium.gif

graphics/aix.gif

graphics/ovms.gif

graphics/i.gif

graphics/sles64.gif

graphics/redhatPc.gif

graphics/win32.gif

graphics/win64.gif
EntireX Broker x(4) x(6) x   x x x x x     x x x x
EntireX Workbench                       x x x x
EntireX RPC                              
Batch RPC Server x x x                        
CICS RPC Server x x                          
IMS RPC Server x                            
COBOL Server/Client x x x                        
Micro Focus RPC Server/Client         x x x x x     x x x x
PL/I Server/Client x                            
C RPC Server/Client     x(5)   x x x x x   x x x x x
Java RPC Server/Client x(3)       x x x x x     x x x x
XML/SOAP RPC Server/Client x(3)       x x x x x     x x x x
WebSphere MQ RPC Server x(3)       x x x x x     x x x x
WebSphere MQ Listener x(3)       x x x x x     x x x x
DCOM RPC Client (1)                           x x
.NET RPC Server/Client (2)                           x x
RPC-ACI Bridge x(3)       x x x x x     x x x x
CICS ECI RPC Server x(3)       x x x x x     x x x x
IMS Connect RPC Server x(3)       x x x x x     x x x x
EntireX ACI                              
Broker Stubs x x x x x x x x x x x x x x x
Java ACI x       x x x x x     x x x x
ActiveX Control/TOR Editor                           x x
System Management Hub         x x x x x     x x x x
Broker Agent x       x x x x x     x x x x
JMS Support         x x x x x     x x x x
Attach Manager         x x x x x     x x x x
Application Monitoring Data Collector         x x x x x     x x x x

In accordance with the license agreement you concluded with Software AG, your EntireX license includes either full functionality or specific EntireX components.

Notes:

(1) Application wizard for Visual Studio .NET also provided in installation kit for Windows 32-bit only.
(2)

Application wizard for Visual Studio .NET also provided in installation kit for Windows 32-bit and Windows 64-bit.

(3) Batch only. These components included as a TAR file in the z/OS installation kit and must be copied to your z/OS UNIX environment. See Installing EntireX Java Components under z/OS UNIX.
(4) Batch only. "Broker" here refers to the broker kernel, also known as broker nucleus. In all versions of EntireX under z/OS, the EntireX broker kernel runs in batch mode only, either as a job or a started task. It does not run under TSO, CICS, Com-plete or any other online environment.
(5) Only servers are supported; a server example is delivered.
(6) Batch only. "Broker" here refers to the broker kernel, also known as broker nucleus. In all versions of EntireX under z/VSE, the EntireX broker kernel runs in batch mode only. It does not run in any online environment.
IPv6 is not supported on this platform. Establishing an SSL connection on z/VSE requires BSI's Automatic Transport Layer Security (ATLS).

Supported RPC Protocols

RPC Protocol(1) Feature(2) EntireX EntireX Adapter for Integration Server PI Adapter for EntireX Natural More Information
Mainframe ONE Open Systems
2000 IDL unbounded arrays 5.4 7.1 4.1.0 4.1.3 8.1 6.1.1 PL13 Unbounded arrays are arrays with variable upper bounds, see array-definition under Software AG IDL Grammar in the IDL Editor documentation. For the programming language COBOL they can be defined with an upper maximum and mapped to COBOL data items with the DEPENDING ON clause. See COBOL Tables with Variable Size - DEPENDING ON Clause.

If a COBOL server is wrapped with the COBOL Wrapper or extracted with the IDL Extractor for COBOL, a server mapping file (EntireX Workbench file with extension .cvm or .svm) (3) is automatically created for IDL unbounded arrays.
IDL types PU, NU 5.4 7.1 4.1.0 4.1.3 8.1 6.1.1 PL13 The data types packed and unpacked decimal unsigned support the programming languages COBOL and PL/I. See IDL Data Types under Software AG IDL File in the IDL Editor documentation.
IDL structs 5.4 7.1 4.1.0 4.1.3 8.1 6.1.1 PL13 An IDL struct describes a user-defined type for reusability. For RPC server with a CICS channel container interface, it describes the layout of container. See structure-definition under Software AG IDL Grammar.
IDL aligned attribute 5.4 7.1 4.1.0 n/a n/a n/a The aligned attribute is relevant for the programming languages COBOL and PL/I and the server side. For other languages it is not relevant. See attribute-list under Software AG IDL Grammar.
IDL parameters with more than 3 indices (all indices up to the parent on level 1 counted) 5.4 7.1 4.1.0 n/a n/a n/a See array-definition under Software AG IDL Grammar in the IDL Editor documentation.
IDL library or IDL program longer than 8 characters 5.4 7.1 4.1.0 4.2.6 8.1 6.3.7 Long IDL library and program names are a challenge for languages such as COBOL and Natural, which restrict program names to 8 characters. These long IDL names are nevertheless supported by EntireX.

If a Natural server is wrapped with Natural Wrapper or extracted with IDL Extractor for Natural with a long IDL program name, this forces a client-side mapping file (EntireX Workbench file with extension .cvm) (4) and protocol 2030.

If a COBOL server is wrapped with COBOL Wrapper or extracted with IDL Extractor for COBOL with a long IDL program name, this forces a server mapping file (EntireX Workbench file with extension .cvm or .svm) (3) to be created.
Reliable RPC 8.0 7.2 4.1.1 4.2.5 8.1 6.3.6 Reliable RPC.
CICS Channel Container 8.2.2 7.1 4.1.0 n/a n/a n/a If a COBOL server with interface type CICS with Channel Container Calling Convention is wrapped with the COBOL Wrapper or extracted with the IDL Extractor for COBOL, a server mapping file (EntireX Workbench file with extension .cvm or .svm) 3 is automatically created.

Natural RPC clients generated with the Natural Wrapper can call COBOL programs using CICS with Channel Container Calling Convention.
Mixed case RPC passwords 8.2.2 8.2.2 no 4.1.4 8.1 6.1.1 PL21 Allow RPC passwords with lowercase characters. See Natural Security under Common Features of Wrappers and RPC-based Components.
2010 Natural optional parameters n/a n/a n/a 4.1.3 8.1 6.1.1 PL13 Optional parameters are a special Natural feature. See Natural documentation.
2020 IDL types U, UV 7.3 7.1 4.1.1 4.2.1 8.1 6.2.1 The Unicode data types support all programming languages with separate Unicode and character types such as COBOL, Natural and C. See IDL Data Types under Software AG IDL File in the IDL Editor documentation.
Up to 99 IDL Levels 7.3 7.1 4.1.1 4.2.1 8.1 6.2.1 IDL levels are used in conjunction with parameter grouping. Parameters are either scalar or a member of the immediately preceding group that has been assigned a lower level number. See simple-parameter-definition under Software AG IDL Grammar.
2030 Natural Redefine, client-side mapping file for Natural, and other features 8.2 8.2 4.1.2 4.2.7 and 8.2.2 8.2.4 6.3.9 REDEFINEs are supported by IDL Extractor for Natural on the server side and force a client-side mapping file (EntireX Workbench file with extension .cvm) (4) to be created. See When is a Server Mapping File Required? in the EntireX Workbench documentation for full list of features.
Client-side mapping file for COBOL 9.7 9.7 4.1.2 n/a n/a n/a If a COBOL server is wrapped with the COBOL Wrapper or extracted with the IDL Extractor for COBOL, a server mapping file (EntireX Workbench file with extension .cvm or .svm) (3) is automatically created if one is required. See When is a Server Mapping File Required? in the EntireX Workbench documentation.

Natural RPC clients generated with the Natural Wrapper can send client-side mapping (containing COBOL mapping or Natural mapping) to the target RPC server.
2040 Increased precision for IDL types N, NU, P, PU 9.7 9.7 no 8.2.2 8.4.1 8.4.1 If more than 7 digits after the decimal point or more than 29 digits in total (before and after the decimal point) are used.

For EntireX, the maximum number of supported digits depends on language and operating system. See notes for data types N, NU, P and PU in section Mapping IDL Data Types to target language environment C | CL | COBOL | DCOM | .NET | Java | Natural | PL/I | RPG | XML.

n/a = not applicable
no = not supported

Notes:

  1. To enable communication it is not required that both partners (RPC client and RPC server) support the same level of RPC protocol. There is a handshake to negotiate the highest protocol level supported by both ends. The RPC protocols 1110 thru 1140 (which are not documented here) may occur in communications as well if older RPC components are used.
  2. To enable communication the feature used must be supported by both partners (RPC client and RPC server), otherwise communication is not possible.
  3. If a client-side mapping file (.cvm) is used, protocol 2030 is forced. If a server-side mapping file is used, the protocol level is not increased. For more information see Server Mapping Files for COBOL and How to Set the Type of Server Mapping Files in the EntireX Workbench documentation.
  4. For more information see Server Mapping Files for Natural in the EntireX Workbench documentation.