Description:
When upgrading to TIBCO Object Service Broker R5.2.0, users of the TIBCO Service Gateway for DB2 product using static SQL must regenerate, reassemble, and relink their static SQL modules.

Environment:
============
All users of TIBCO Service Gateway for DB2 5.2.0 using static SQL.

Symptoms:
=========
Excessive CPU usage in the DB2 Gateway address space.

Cause:
======
At R5.2.0 support is introduced for long names in DB2 field names.  Because of this, the format of the static load modules has changed. Old versions cannot be used and are repeatedly loaded and rejected leading to high Gateway CPU usage.

Resolution:
===========
Use the @STATICSQL tool to regenerate the source for the static modules then reassemble and relink. It is not necessary to recollect the data used by @STATICSQL as this should still be available in the MetaStor.

References:
===========
TIBCO Service Gateway™ for DB2 Installing and Operating Software Release 5.2.0
Symptoms:

Cause:

DB2 Static SQL must be regenerated at R5.2.0