Skip Headers

Oracle® Procedural Gateway for APPC Installation and Configuration Guide
Release 9.2.0.1.0 for UNIX

Part Number A96648-01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

C
Summary of Changes in Previous Versions

This appendix provides a summary of changes in previous versions of Oracle Procedural Gateway for APPC.

This appendix contains the following sections:

Changes and Enhancements in Previous Versions

The following sections list changes and enhancements that were made to previous releases of the gateway.

Release 9.0.1.0.1

PGA_TRACE Parameter No Longer Supported

With this release of Oracle Procedural Gateway for APPC, the PGA_TRACE parameter is no longer supported. If you are copying the initsid.ora file from an older version of the gateway, you must remove this parameter.

TRACE_LEVEL and LOG_DESTINATION Parameters Moved

With this release of Oracle Procedural Gateway for APPC, the TRACE_LEVEL and LOG_DESTINATION parameters have been moved from the pg4hoa1.sh file to the initsid.ora file.

FDS_CLASS_VERSION Parameter Added

You will need to add the FDS_CLASS_VERSION parameter to your startup shell script file (pg4hoa1.sh). A default value is specified in pg4hoa1.sh.

Release 8.0.4.1.0/ 8.0.6.1.0

Release 4.0.1.1.0

Release 4.0.0.1.0

Release 3.4.0.1.0

Release 3.3.1.0.1

Corrected Problems in Previous Versions

The following tables list the numbers and descriptions of each bug fixed in previous releases of the gateway.

Release 9.0.1.0.1

The following table lists the bugs that have been fixed in Release 9.0.1.0.1 of the gateway, along with their descriptions:

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."

Release 8.0.6.1.0

Bug Number Description

1329386

PGAU core dumped on large packages. When users tried to generate large packages with PGAU, they got a core dump.

561128

The PLSTYPE attribute of binary integers (COBOL COMP data items) had the wrong precision when the data was defined without COMPOPTS('TRUNC(BIN)') specified.

599696

PGAU COBOL parser did not accept OCCURS clause appearing before datatype as valid syntax.

603934

When COBOL data definitions contained OCCURS and REDEFINES, the PGAU-generated .pkb file was invalid.

689304

This bug occurred when a CICS transaction abended between the time that the Oracle server called the gateway to perform a commit and the time that the CICS transaction was successfully committed.

When this occurred, the Oracle recovery process (RECO) would call the gateway's recovery function (GTARECO) to resolve the transaction. The GTARECO function mistakenly relayed that it had successfully rolled back the CICS transaction, but in fact it had failed to delete the row from PGA_CC_PENDING.

Release 4.0.1.1.0

Bug Number Description

420391

PGAU generated invalid PL/SQL in the TIP when a COBOL definition contained an OCCURS clause and was defined as an IN OUT parameter. A PLS-103 error was generated when attempting to compile the TIP.

460960

ORA-9199 errors were generated by the gateway after some gateway exceptions due to a memory overlay.

473360

PGAU encountered a segment fault when executing a GENERATE command for a transaction with a very large number of fields defined in its COBOL data.

506777

An ORA-1017 error was generated by the gateway when RECO attempted to log onto the gateway during recovery of a distributed transaction, even though the gateway was running in READ-ONLY mode.

444471

The install of the gateway failed while linking the gateway executables if the C compiler was not installed on the UNIX system.

474889

The gateway server encountered a segment fault during installation verification if the patch for bug number 444771 was installed. The patch contained incorrect linker parameters.

Release 4.0.0.1.0

Bug Number Description

348132

COBOL PIC S9 (4) values greater than +9999 or less than -9999 were truncated to 4 digits by PGAU-generated TIPs.

359116

Error message ORA-3106 received when integrating server resided on a platform with different byte-ordering from the gateway platform.

359973

PL/SQL packages that called the gateway were marked invalid when one of them encountered an error during execution.

361966

PL/SQL procedures that called the gateway were marked invalid when other procedures that called the gateway were recompiled.

364538

SAVEPOINT caused error message ORA-3113 to be received from the gateway. The gateway server was taking a segmentation fault.

380431

Install did not copy sighold.o into $ORACLE_HOME/lib, resulting in a failure in the gensnalib shell script and subsequent failures on the linking of the gateway executables.

381305

PGAU-generated TIP specifications sent invalid COBOL data when SIGN LEADING SEPARATE or SIGN TRAILING SEPARATE was used with USAGE IS DISPLAY. The fix for PL/SQL bug 383510 is also required to correct problems in the UTL_PG PL/SQL package.

388162

PGAU-generated TIP specifications sent more than 32K of data, causing error message ORA-6502 to be received from UTL_RAW.OVERLAY.

405129

RPAD call used EBCDIC blank (x '40') as the pad character when converting data regardless of the local or remote character set setting.

Release 3.4.0.1.0

Bug Number Description

284743

PGAU GENERATE incorrectly rejected sequential OCCURS groups as being nested.

312840

PGAU GENERATE skipped generation of a unique nested OCCURS group that followed a duplicate nested OCCURS group.

318928

PGAU DEFINE TRANSACTION did not allow a fully-qualified LU name value in the LUNAME parameter.

320113

The sample SNAplus configuration file had the wrong partner LU in the SYM_DEST_NAME definition for IMSPGA61.

320635

PGAU GENERATE created a TIP with a missing output record descriptor when the input and output data definitions used the same COBOL copybook.

324540

PGAU-generated TIPs could not handle variable-length records and generated errors when the records were shorter than the maximum length.

329319

PGAU GENERATE corrupted COBOL 'REDEFINES WHEN' criteria with negative values.

337093

PGAU DEFINE TRANSACTION did not allow the TPNAME parameter to include path specification, even when enclosed in double quotes.

340832

The CICS FEPI demo COBOL source file pgadb2f.cob was corrupted.

Release 3.3.1.0.1

Bug Number Description

231644

PGAU core dumped if LANGUAGE environment variable was not set.

231768

PGAU did not handle COBOL variable names continued across multiple input lines.

231779

PGAU did not reject ambiguous references in COBOL definitions.

235026

PGAVSN procedure returned wrong version number.

236295

Misleading PGA-20910 message was issued when the remote transaction program de-allocated a conversation without sending expected data.

240908

Lowercase gateway SID was converted to uppercase when used in a log file name.

244606

PGAU converted the LUNAME specified in a DEFINE TRANSACTION statement to uppercase.

244612

PGAU converted the TPNAME specified in a DEFINE TRANSACTION statement to uppercase.

244654

PGAU converted the SIDEPROFILE specified in a DEFINE TRANSACTION statement to uppercase.

252135

PGAU failed to reject invalid trace options specified in the DIAGNOSE(TRACE()) parameter on a GENERATE statement.

257787

Message PGA-20905 was received from the gateway server if conversations were terminated in a different order than they were started.

257998

PGAADMIN roles could not be assigned to other users.

261238

PGAU incorrectly reported the SYNCLEVEL value for a transaction as 0 even when the DEFINE TRANSACTION statement specified SYNCLEVEL(1).

264615

PGAU encountered a segmentation violation when generating a TIP.

268122

PGAU generated incorrect PL/SQL if the COBOL REDEFINES WHEN construct was used.

274137

PGAU did not allow MODE or LU names to begin with $, #, or @.

278549

PGAU generated incorrect table keys for OCCURS group, resulting in an ORA-6502 message.

284247

PGAU encountered a segmentation violation when generating a TIP if a SIDEPROFILE was specified in the DEFINE TRANSACTION statement.

287169

PGAU GENERATE computed incorrect data offsets after multiple adjacent OCCURS groups.

312840

PGAU GENERATE skipped a unique nested group that followed a duplicate nested group.

Known Problems in Previous Releases

The following section lists problems that were known to exist in previous releases of the gateway.

Release 8.0.6.1.0

No known problems were documented in release 8.0.6.1.0.

Release 4.0.1.1.0

The following problems in other products are known to affect the operation of products in this release:


Go to previous page Go to next page
Oracle
Copyright © 1996, 2002 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Contents
Go To Index
Index