2 Release Information

This chapter contains information that is specific to this release of the gateway. It contains the following sections:

Changes and Enhancements
Known Problems for 10g Release 2
Known Restrictions for 10g Release 2

2.1 Changes and Enhancements

The following changes and enhancements apply to all releases of release 2 (10.2.0) gateway products.

2.1.1 Changes and Enhancements for Release 10.2.0

The following sections describe the changes and enhancements included in this release.

2.1.1.1 Oracle Server Dependencies

This release of Oracle Procedural Gateway and Tools for WebSphere MQ requires the latest released patch set for Oracle Database 10g release 2 (10.2.0), or for the Oracle database release that you are using.

2.1.2 Changes and Enhancements for Release 10.2.0

The following changes and enhancements are for the previous release of the Oracle10g gateway products.

2.1.2.1 Support for Large Data Buffers

The PL/SQL RAW data type limitation is 32 KB (32767) bytes. For large loads, you must use the TABLE OF RAWS data type. For more information about support for large data buffers, refer to Appendix A.

2.1.2.2 PGM_UTL Procedures

The following table provides information about PGM_UTL procedures.

Procedure	V401	V804	V817 and V901	Oracle10g Release 2
`TO_RAW`	N.A.	`PGM_UTL.TO_RAW`	`PGM_UTL8.TO_RAW`	`PGM.TO_RAW`
`RAW_TO_MQMD`	N.A.	`PGM_UTL.RAW_TO_MQMD`	`PGM_UTL8.RAW_TO_MQMD`	`PGM.RAW_TO_MQMD`
`RAW_TO_MQPMO`	N.A.	`PGM_UTL.RAW_TO_MQPMO`	`PGM_UTL8.RAW_TO_MQPMO`	`PGM.RAW_TO_MQPMO`
`RAW_TO_MQGMO`	N.A.	`PGM_UTL.RAW_TO_MQGMO`	`PGM_UTL8.RAW_TO_MQGMO`	`PGM.RAW_TO_MQGMO`

Note:

For Oracle10g release 10.2.0, the PGM.TO_RAW, PGM.RAW_TO_MQMD, PGM.RAW_TO_MQPMO and PGM.RAW_TO_MQGMO procedures are added for backward compatibility.

2.1.2.3 PG4MQ API Prototype Changes

The following table provides information about PG4MQ application programming interface changes.

API	V401 Arguments	V804 Arguments	V817 & V901 Arguments	10g Release 2 Arguments
`MQOPEN`	`(MQOD,INT,INT)`	`(RAW,INT,INT)`	`(RAW,INT,INT)`	`(PGM.MQOD,INT,INT)`
`MQPUT`	`(INT,MQMD,MQPMO,RAW)`	`(INT,RAW,RAW,RAW)`	`(INT,RAW,RAW,RAW)`	`(INT,PGM.MQMD,PGM_MQPMO,RAW) or (INT, PGM.MQMD, PGM_MQPMO, PGM.MQPUT_BUFFER)`
`MQGET`	`(INT,MQMD,MQGMO,RAW)`	`(INT,RAW,RAW,RAW)`	`(INT,RAW,RAW,RAW)`	`(INT,PGM.MQMD,PGM_MQGMO,RAW) or (INT, PGM.MQMD, PGM.MQGMO, PGM_MQGET_BUFFER)`
`MQCLOSE`	`(INT,INT)`	`(INT,INT)`	`(INT,INT)`	`(INT,INT)`

Refer to Appendix A for details of APIs.

2.1.2.4 Heterogeneous Services Architecture

This release of Oracle Procedural Gateway for WebSphere MQ uses the Oracle Heterogeneous Services external procedure component within the Oracle10g server.

2.1.2.5 Performance Enhancements

Oracle Procedural Gateway for WebSphere MQ contains several internal performance enhancements. This product has shown major improvements in response time and CPU utilization for all relevant address spaces for a variety of workloads compared to version 4 gateways. The actual performance improvement at your site might vary depending on your installation type and workload.

2.1.2.6 New PG4MQ Packages

PGM and PGM_UTL8 packages are new in this release. These packages provide new features as well as ensure backward compatibility. Refer to Migration Tips for the details of upgrading your existing PL/SQL application programs to use Oracle10g PG4MQ features.

2.1.2.7 New PG4MQ Deployment Scripts

The following scripts are new in this release:

pgm.sql
pgmobj.sql
pgmdeploy.sql
pgmundeploy.sql

The gateway procedures in the PGM package are defined in pgm.sql and PGM_MQ* data type definitions used by the procedures are defined in pgmobj.sql. For complete information about PGM package, PG4MQ gateway procedures and data type definitions, refer to Appendix A.

2.1.2.8 Large Payload Support

PG4MQ 10g release 2 (10.2.0) supports large payloads or messages longer than 32767 bytes. For more information, refer to the putlongsample.sql and getlongsample.sql sample programs installed with the PG4MQ.

2.1.2.9 Database Link and Alias Library

A connection to the gateway is established through a database link. From PG4MQ 10g release 2 and later, this database link is no longer associated with each PG4MQ gateway procedural call (for example, PGM.MQPUT@dblink). From 10g release 2 and later, it needs to be defined only once in the MQOD data type used by MQOPEN, and this database link is registered in the object handle returned by the MQOPEN call. Refer to the sample programs installed with the gateway for details. By default, a public database link, pg4mqdepdblink, is created with your default SID when PG4MQ deployment scripts are executed.

2.2 Known Problems for 10g Release 2

The problems documented in this section are specific to the Oracle Procedural Gateway for WebSphere MQ and are known to exist in this release of the product. These problems will be fixed in a future gateway release. If you have any questions or concerns about these problems, contact Oracle Support Services.

A current list of problems is available online. Contact your local Oracle office for information about accessing this online information.

2.3 Known Restrictions for 10g Release 2

The following restriction is known to exist for this release.

Setting LD_ASSUME_KERNEL

There are known issues when running WebSphere MQ 5.3 on releases of RedHat Linux 32 bit operating systems. If you are able to resolve the problems by setting the LD_ASSUME_KERNEL environment variable, you need to do the same thing for this release, by setting LD_ASSUME_KERNEL in the listener.ora file used by PG4MQ. For example:

SID_LIST_LISTENER_pg4mq =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME=pg4mq)
      (ENVS=LD_ASSUME_KERNEL=2.4.1)
      (ORACLE_HOME=/products/pg4mq/oracle)
      (PROGRAM=pg4mqc)
    )
  )