This chapter provides information about this release of the Oracle Database Gateway for APPC. It contains the following sections:
The following product components are included in the product installation media:
Oracle Database Gateway for APPC, release 11.2
Oracle Net, release 11.2
The following sections describe the changes and enhancements unique to the 11g release of the gateway:
The Gateway Password Encryption tool (
tg4pwd) has been replaced by a generic feature that is now part of Heterogeneous Services. Refer to Chapter 15, "Security Considerations" in Oracle Database Gateway Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64 or Oracle Database Gateway Installation and Configuration Guide for Microsoft Windows for details.
There is full IPv6 support between Oracle databases and the gateway but IPv6 is not yet supported between the gateway and IMS Connect.
The following sections list the known restrictions for the Oracle Database Gateway for APPC and PGAU.
The Oracle Database Gateway for APPC has supported multibyte character set data for COBOL PIC G data types from version 3.4 onwards. However, the non-numeric character data (such as $, (,), +, -,.) that is allowed in
DISPLAY data types and PIC 9 edit masks must still be specified in EBCDIC. The non-numeric character data is not subject to MBCS translation.
When performing a CICS transaction using the Oracle Database Gateway for APPC, you cannot emulate CICS PF keys.
You cannot define and transmit APPC PIP data in this release of the Oracle Database Gateway for APPC.
Conversion of the
floating point data type is not supported by the Oracle Database Gateway for APPC.
The Oracle Database Gateway for APPC does not provide exits for compression and decompression facilities. All data exchanged between the gateway and the transaction must be in uncompressed format.
The IBM VS COBOL II compiler has been desupported. However, the string "
IBMVSCOBOLII" is still used as the value of the compiler name parameter to represent any COBOL compiler you choose to use. The value
IBMVSCOBOLII should still be used and does not create a dependency on any specific version of the compiler.