| Oracle Procedural Gateway® for APPC Installation and Configuration Guide 10g Release 2 (10.2) for Microsoft Windows Part Number B16211-01 |
|
|
View PDF |
| Oracle Procedural Gateway® for APPC Installation and Configuration Guide 10g Release 2 (10.2) for Microsoft Windows Part Number B16211-01 |
|
|
View PDF |
This chapter provides information about this release of the Oracle Procedural Gateway for APPC. It contains the following sections:
The distribution CD for this release of the Oracle Procedural Gateway for APPC includes the following production components:
The following sections detail the changes and enhancements in this release of the Oracle Procedural Gateway for APPC.
The following sections provide information on changes to this release of the Oracle Procedural Gateway for APPC:
If the gateway cannot find the initsid.ora file, then an error should be returned.
For this release, a tool called tg4pwd has replaced pg4pwd. Refer Section 11.6, "Passwords in the Gateway Initialization File" for more information.
The following sections list the known restrictions for the Oracle Procedural Gateway for APPC and PGAU.
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 datatypes since version 3.4. However, the non-numeric character data (such as $, (,), +, -,.) that is allowed in DISPLAY datatypes 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 Data Type Conversion Is Not Supported
Conversion of the floating point datatype 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.
