PM46439 - DB2 contexts confused if ARSSOCKD uses DB2 API and CLI
The Content Manager OnDemand for Mutliplatforms server added the use of a DB2 API to retrieve the database codepage during initialization with changes made to fix APAR PM37940 in fix pack V22.214.171.124. This change caused the DB2 contexts used for client connections to treat the OnDemand server as a DB2 API application instead of a DB2 CLI application.
The changes made to correct APAR PM37940 in Content Manager OnDemand for Multiplatforms 126.96.36.199 added a DB2 API db2CfgGet call during initialization to retrieve the codepage of the database to be used in determining the correct codepage for the OnDemand server. This DB2 API call changed the initialization sequence of the DB2 client contexts being used by the OnDemand server's database connections.
The calling sequence change caused the OnDemand server to be treated as a DB2 API or embedded SQL application. These types of applications use single context to access the DB2 database. This causes all the OnDemand database server connections to be synchronized and only one connection to the database was active. This behavior causes severe performance degradation, database deadlocks, and intermittent crashes of DB2.
To correct this issue, the Content Manager OnDemand for Multiplatforms server has been changed to be a purely CLI application. This was accomplished by moving DB2 API calls to a separate process or replacing them with SQL submitted via a CLI connection.
Content Manager OnDemand for Multiplatforms customers using DB2 are requested to upgrade to fix pack V188.8.131.52 to correct this issue.
More support for:
Content Manager OnDemand for Multiplatforms
Software version: 8.5
Operating system(s): Platform Independent, Windows
Software edition: All Editions
Reference #: 1515063
Modified date: 02 April 2012
Translate this page: