1
Release Information

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

• Product Set

• Changes and Enhancements Release 9.2.0.1.0

• Known Restrictions

Product Set

The following table lists the production components included on the distribution CD for Oracle Procedural Gateway for APPC:

Component	Release
Oracle Procedural Gateway for APPC Procedural Gateway Administration Utility AIX only: Resource Recovery Manager	9.2.0.1.0 9.2.0.1.0 9.2.0.1.0
Oracle Net	9.2.0.1.0

Changes and Enhancements Release 9.2.0.1.0

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

Changes

The following sections provide information on changes.

Oracle Call Interface

Because of changes to the Oracle Call Interface (OCI), Oracle Procedural Gateway for APPC internal codes for calling COMMIT/CONFIRM have changed. This does not affect user functions.

APPC Log File

The Oracle Procedural Gateway for APPC log file is improved, and provides more information about transactions. For a sample of the new log file, refer to Chapter 6 of the Oracle Procedural Gateway for APPC User's Guide for UNIX.

Enhancements

Components of the Oracle Procedural Gateway for APPC are based on Oracle9i Server release 9.2.0.1.0 (the Oracle Integrating Server).

Password Encryption Utility for Gateway Initialization File

This release of the gateway includes a utility to support encryption of plain-text passwords in the gateway initialization file. For more information, refer to Chapter 5.

AIX-Only: Password Encryption Utility for Resource Recovery Manager

This release of the gateway includes another utility to support encryption of plain text passwords, which is called LOG_PASS in the initialization file for local LU. For more information, refer to "AIX-Based Systems Only: Using the pg4rrmpwd Utility" .

Bugs Fixed in Version 9i

The following table lists the bugs that have been fixed in version 9i of the gateway, along with their descriptions.

Table 1-1 Bugs Fixed in version 9i

Bug Number	Description
1276298	When using an invalid value for receive parameter for the pgaxfer procedure, the user receives an ORA 28511 error message.
1302253	Oracle Procedural Gateway for APPC procedure statements executed on the Oracle integrating servers would hang in SQL*Plus, without giving any messages.
1336805	When the PGA_SECURITY_TYPE parameter was set to PROGRAM and the PGA_CAPABILITY parameter was set to COMMIT_CONFIRM, the user received an authentication error but could not see who was complaining about it.
1404454	The pg4appc log file should be improved and have the received buffer in the log file.
1411694	The user receives message ORA-28527 when the PGA_CAPABILITY is set to READ_ONLY.
1472800	Multi-row queries failed on the following error messages: ORA-01401 and ORA-06512.
1519088	User received sporadic abends when inserting CICS records to VSAM file.
1677939	Oracle Procedural Gateway for APPC would partially transfer low values to VSAM files.
1722467	When the PGA_SECURITY_TYPE parameter was set to PROGRAM and the user specified the user ID and password through database link explicit CONNECT information, the query failed with message PGA-20910 RC=6.
1724988	When the programmer used RPC PGAINIT_SEC, no matter what synclevel was being used, the following message was received: "invalid SYNCHLEVEL, 152, specified; valid range is 0:1."
2092204	When using PGATCTL procedure with specifying the function code as "D", the user receives the message PGA-20932 with an invalid function code.
2128785	Oracle Server Heterogeneous Services place unwanted trace files into /tmp directory.

Known Restrictions

The following restrictions are known to exist in this release of the product.

AIX-Based Systems Only: Two-Phase Commit Provides No Automatic Recovery With CICS/ESA

When an update transaction with CICS/ESA at LU6.2 Sync level 2 fails, CICS always rolls back or commits the transaction (based on the INDOUBT parameter of the CICS transaction definition), making automatic recovery by the Oracle integrating server impossible.

Multibyte Character Sets are Not Supported for Numeric Data and Clauses

As of version 3.4, the Oracle Procedural Gateway for APPC supports multibyte character set data for IBM VS COBOL II PIC G datatypes. 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 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 Oracle Procedural Gateway for APPC and the transaction must be in uncompressed format.

PGAU USAGE(NULL) on DEFINE/REDEFINE DATA Not Implemented

The USAGE(NULL) keyword on the DEFINE or REDEFINE DATA PGAU statements is not yet implemented, even though it is documented.

PGAU Does Not Process COBOL COPY REPLACE Correctly

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

Refer to Appendix B, "TIP Internals" in Oracle Procedural Gateway for APPC User's Guide for a complete list of Oracle Procedural Gateway for APPC restrictions.