2 Release Information

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

"Product Set"
"Changes and Enhancements, Release 10.1.0.2.0"
"Known Restrictions for the Gateway"

2.1 Product Set

The distribution CD for this release of the Oracle Procedural Gateway for APPC includes the following production components:

Oracle Procedural Gateway for APPC Release 10.1.0.2.0
Oracle Net Release 10.1.0.2.0

2.2 Changes and Enhancements, Release 10.1.0.2.0

The following sections detail the changes and enhancements in this release of the Oracle Procedural Gateway for APPC.

2.2.1 Changes

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

2.2.1.1 Bugs Fixed in Release 10.1.0.2.0

Table 2-1 lists the bugs that were fixed in Release 10.1.0.2.0 of the gateway.

Table 2-1 Bugs Fixed in Release 10.1.0.2.0 of the Gateway

Bug Number	Description
1310776	PG4APPC to support TCP/IP connectivity to IMS.
1472845	Receiving message ORA-1401: handling multiple items in one call to PGAXFER causes error.
1847587	Receiving message ORA-2047: executing procedures against read-only gateways.
1853035	The gateway generates the wrong message (PGA-20936) instead of generating message number PGA-20938.
1919413	Receiving an ORA-28528 error (Heterogeneous Services datatype conversion error) when sending a buffer of more than 4K of data to CICS.
1920013	Test case tgpsm#34 fails with error message PGA-20910, rc=219, and errno = 9 instead of PGA-20934.
2088612	Receiving message ORA-1401: inserted value too large for column.
2222386	Transferring more than 32760 bytes in a RAW field. Customer receives error message ORA-01401: "inserted value too large for column". When the gateway attempts to transfer 32760 or more bytes back to Oracle in a single transfer, the result is ORA-02055: "distributed update operation failed; rollback required".
2505566	PGDDVCHK.SQL doesn't require spooling file.
2526386	CMDEAL not called in certain error situations in PGAXFER.
2691119	ORA-06510: PL/SQL: Unhandled user-defined exception when using PGATRAC.
3067506	Savepoint and rollback savepoint are not supported by PG4APPC.

2.2.2 Enhancements

Components of the Oracle Procedural Gateway for APPC are based on Oracle Database 10g Server, Release 10.1.0.2.0 (the Oracle Integrating Server).

2.2.2.1 TCP/IP Support for Connecting the Gateway to IMS Connect Release 1.2

This release of the gateway includes TCP/IP support for IMS Connect. IMS Connect is an IBM product which allows TCP/IP clients to trigger execution of IMS transactions. The gateway can use a TCP/IP communication protocol to access IMS Connect, which triggers execution of IMS transactions. There is no SNA involvement with this configuration. Related to this new feature of the gateway is:

2.2.2.2 Improved Gateway Log File

The log file for the gateway remote application has been improved.

2.3 Known Restrictions

The following sections list the known restrictions for the Oracle Procedural Gateway for APPC and PGAU.

2.3.1 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 since version 3.4. 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 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.

2.3.2 Known Restrictions for PGAU

Restrictions with PGAU COBOL COPY REPLACE

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