Skip Headers
Oracle® Database Gateway for APPC Installation and Configuration Guide
11g Release 1 (11.1) for AIX 5L Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), Solaris Operating System (SPARC 64-Bit), and Linux x86

E10076-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Release Information

This chapter provides information about this release of the Oracle Database Gateway for APPC. It contains the following section:

2.1 Known Restrictions

This section list the known restrictions for the Oracle Database Gateway for APPC and PGAU.

2.1.1 Known Restrictions for the Gateway

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

Multibyte Character Sets are Not Supported for Numeric Data and Clauses

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.

CICS Transactions Do Not Allow PF Key Emulation

When performing a CICS transaction using the Oracle Database 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 Database Gateway for APPC.

Floating Point Datatype Conversion is Not Supported

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

Transaction Programs are Responsible for All Data Compression and Decompression

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.

IBM VS COBOL II Compiler Desupported

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.

2.1.2 Known Restrictions for PGAU

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