| Oracle Procedural Gateway® for APPC Installation and Configuration Guide 10g Release 1 (10.1) for Microsoft Windows Part Number B13694-01 |
|
|
View PDF |
| Oracle Procedural Gateway® for APPC Installation and Configuration Guide 10g Release 1 (10.1) for Microsoft Windows Part Number B13694-01 |
|
|
View PDF |
This appendix provides a summary of changes in previous versions of the Oracle Procedural Gateway for APPC.
This appendix contains the following sections:
The following sections list changes and enhancements that were made to previous releases of the gateway.
The following section lists changes and enhancements that were made to Release 9.2.0.1.0 of the gateway:
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 Microsoft Windows, Release 9.2.0.1.0.
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.
The following section lists changes and enhancements that were made to Release 9.0.1.1.0 of the gateway:
Release 9.0.1.1.0 of the Oracle Procedural Gateway for APPC requires and Oracle9i release 9.0.1.1.0 (Oracle 9i database server 9.0.1) or higher Oracle Integrating Server.
If you are installing Oracle Procedural Gateway for APPC release 9.0.1.1.0 on the system for the first time, the ORACLE_HOME directory is C:\orant, by default.
The following section lists changes and enhancements that were made to Release 9.0.1.0.1 of the gateway:
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.
FDS_CLASS_VERSION parameter added: You will need to add the FDS_CLASS_VERSION parameter to your startup shell script file (initsid.ora). A default value is specified in initsid.ora.
The following section lists changes and enhancements that were made to Release 8.0.6.0.0 of the gateway:
The Oracle Procedural Gateway for APPC does not support Oracle7 server or earlier.
Heterogeneous Services architecture
This release of Oracle Procedural Gateway for APPC utilizes the Oracle Heterogeneous Services component within the Oracle8 server. Heterogeneous Services is the building block for the next generation of Oracle Open Gateways.
Performance enhancements
Oracle Procedural Gateway for APPC contains several internal performance enhancements. This product has shown major improvements over the version 4 gateways, particularly in response time and CPU utilization for all relevant address spaces for a variety of workloads. The actual performance improvement at your site may vary, depending on your installation type and workload.
PL/SQL V3 compatibility
Before Release 8 you had to set the PLSQL_V2_COMPATIBILITY parameter to "TRUE" to compile PGAU80-generated TIP specifications. This is no longer necessary.
Oracle server dependencies
This release of Oracle Procedural Gateway for APPC requires that the Oracle Integrating Server be an Oracle8 server Release 8.0.6.0.0 or later.
Gateway initialization parameters
In previous versions of the gateway the initialization parameters were stored in files named initsid.gtwboot and initsid.ora, both found in the gateway instance directories. With version 8, most parameters that were in initsid.gtwboot have been moved to the initsid.ora file. The syntax of initsid.ora has been simplified.
When migrating from previous releases of the gateway, be aware of these differences. Refer to "Parameter Changes for Version 4 to Release 9i Migration of Gateway" on page 7-3 for information about these parameters.
tnsnames.ora: The service name definition (from the Oracle Integrating Server to the gateway) must contain an extra parameter, (HS=(DRIVER)).
In this release of the Oracle Procedural Gateway for APPC for Microsoft Windows, the following names have changed:
PGAU80.EXE (known as PGAU80) has been changed to PGAU.EXE (known as PGAU).
PG4APPC80.EXE (known as PG4APPC80) has been changed to PG4APPC.EXE (known as PG4APPC)
With this release of the Oracle Procedural Gateway for APPC for Microsoft Windows, the gateway no longer runs as a Windows service. The process-based gateway provides faster performance because it does not need a management utility. Instead, each Oracle Integrating Server user session that accesses a particular gateway creates an independent process on Windows that runs the gateway server and executes SNA functions.
GTWSRV.EXE is no longer included
As a result of the process-based gateway, the Oracle Procedural Gateway for APPC package no longer includes the GTWSRV.EXE management utility.
The process-based gateway removes the restriction of a four-character limit for the SID name. Refer to the Oracle Net Administrator's Guide for more information about character limits for SID names.
The GTWCONF. EXE process is no longer included in the Oracle Procedural Gateway for APPC for Windows, beginning with this release.
Microsoft SNA Server Version 2 is no longer supported with this release of the Oracle Procedural Gateway for APPC for Microsoft Windows.
The following section lists changes and enhancements that were made to Release 4.0.1.1.0 of the gateway:
Gateway components now based on Oracle7 Server release 7.3.3
The gateway components are now built using the Oracle7 server release 7.3.3 product libraries as a base. All product components shipped with the gateway, including SQL*Net, are now at the release 7.3.2 level.
Gateway supports Oracle8 Server release 8.0.3
The gateway now supports Oracle8 server release 8.0.3 as an integrating server.
UTL_PG now shipped with Oracle Server
The scripts for installing the UTL_PG PL/SQL package are now shipped with the Oracle7 or Oracle8 server and are no longer shipped with the gateway.
Gateway no longer supports Oracle7 Server release 7.1.6 and 7.2
The gateway no longer supports Oracle7 server release 7.1.6 and 7.2 as integrating servers.
User ID and password overrides now supported by gateway (Enh. No. 423300)
A new TIP override is now available to allow the user ID and password sent by the gateway to the OLTP (online transaction processor) to be specified by the user. For complete information on using this override, refer to "Overriding TIP Initializations" in Chapter 2 of the Oracle Procedural Gateway for APPC User's Guide.
New "LENGTH IS" clause supported by PGAU (Enh. No. 428783)
A new "LENGTH IS" clause in COBOL data definitions is now recognized by PGAU and allows the definition of variable-length character fields without using OCCURS DEPENDING ON. For complete information on using this clause, refer to "Format Conversion" in Appendix G of the Oracle Procedural Gateway for APPC User's Guide.
Date/time stamp in trace output
All trace and debug output from the gateway server now contains a date/time stamp in the beginning of each line.
Installer improvements: The installer prompts not relevant to the gateway have been eliminated to streamline the installation process.
The following tables list the numbers and descriptions of each bug fixed in previous releases of the gateway.
Table D-1 lists the bugs that were fixed in Release 9.2.0.1.0 of the gateway, along with their descriptions:
Table D-1 Bugs Fixed in Release 9.2.0.1.0
| 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. |
Table D-2 lists the bugs that were fixed in Release 9.0.1.0.1 of the gateway, along with their descriptions:
Table D-2 Bugs Fixed in Release 9.0.1.0.1
| 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." |
Table D-3 lists the bugs that were fixed in Release 8.0.6.0.0 of the gateway, along with their descriptions:
Table D-3 Bugs Fixed in releases 8.0.6.0.0
Table D-4 lists the bugs that were fixed in Release 4.0.1.1.0 of the gateway, along with their descriptions:
Table D-4 Bugs Fixed in 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. |
| 521084 | ORA-3106 errors were generated by the gateway on Windows under heavy transaction load. |
The following section lists restrictions that were known to exist in previous releases of the gateway. A current list of problems is available online at:
If you have problems accessing this online information, then contact Oracle Support Services for assistance.
No known problems were documented in Release 9.2.0.1.0 of the Oracle Procedural Gateway for APPC.
The following problems in other products are known to affect the operation of products in this release:
UTL_PG Does Not Handle Numeric Data Values Between 0 and +1 (Bug No. 360427)
The UTL_PG.NUMBER_TO_RAW function erroneously issues messages ORA-08414 and ORA-08467 when converting an Oracle number between 0 and +1 into a COBOL numeric value. Contact Oracle Support Services to order the patch correcting this bug.
PGA Grows Excessively When Using Indexed PL/SQL Tables (Bug No. 373700)
When TIPs are executed that use large PL/SQL tables, the memory usage grows excessively. Contact Oracle Support Services to order the patch correcting this bug.
UTL_PG Does Not Handle Leading or Trailing Signs Correctly for DISPLAY Data (Bug No. 383510)
The UTL_PG.RAW_TO_NUMBER and UTL_PG.NUMBER_TO_RAW functions do not handle leading or trailing signs correctly for numeric data defined with USAGE IS DISPLAY. Contact Oracle Support Services to order the patch correcting this bug.
