2 Release Information

Changes

The following sections provide information on changes to this release of the Oracle Procedural Gateway for APPC.

Known Restrictions for the Gateway

The following restrictions are known to exist in this release of the Oracle Procedural Gateway for APPC.

Multibyte Character Sets are Not Supported for Numeric Data and Clauses

The Oracle Procedural 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.

CICS Transactions Do Not Allow PF Key Emulation

When performing a CICS transaction using the Oracle Procedural Gateway for APPC, you cannot emulate CICS PF keys.

APPC PIP Data is Not Supported

You cannot define and transmit APPC PIP data in this release of the Oracle Procedural Gateway for APPC.

Floating Point Datatype Conversion is Not Supported

Conversion of the floating point data type is not supported by the Oracle Procedural Gateway for APPC.

Transaction Programs are Responsible for All Data Compression and Decompression

The Oracle Procedural 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.

Known Restrictions for PGAU

When COBOL input to the PGAU DEFINE DATA statement contains a COPY REPLACE clause, only the first replacement is made.