Resolution:
Description:
============
Error: "S6BD2036E {serverid session module}: SQLCODE -818 THE PRECOMPILER-GENERATED TIMESTAMP {timestamp} IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP {timestamp} BUILT FROM THE DBRM {module}"

may result if the TIBCO Service Gateway™ for DB2 interface is not correctly bound to DB2 when the product is installed or maintenance is applied.


Environment:
============
* DB2 for z/OS
* TIBCO Service Gateway™ for DB2 using STATIC SQL
* z/OS

Symptoms:
=========
When the TIBCO Service Gateway™ for DB2 is initialized and a DB2 table request is scheduled from a TIBCO Object Service Broker user session, the request will fail with the error:

"S6BD2036E {serverid sessionid moduleid}: SQLCODE -818 THE PRECOMPILER-GENERATED TIMESTAMP {timestamp} IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP {timestamp} BUILT FROM THE DBRM {module}"

Cause:
======
The cause of the timestamp mismatch is likely due to an incorrectly performed BIND operation for the TIBCO Service Gateway™ for DB2 interface modules: HDB2SREQ, HDB2SEL, HDB2ISRT, HDB2REPL, HDB2DLET and HDB2STPR. Follow the instructions in the TIBCO Service Gateway™ for DB2 Installing and Operating Software Release 5.2.0 manual, chapter 1, section "Binding the Gateway Plan".


Resolution:
===========
Re-BIND the plan using the supplied TIBCO Service Gateway™ for DB2 DBRMLIB and LOAD libraries. JCL to accomplish this can be found in: $HLQNONV$.$INSTVER$.JCL(BINDDB2S)


References:
===========
DB2 for z/OS Codes
DB2 for z/OS Command Reference
TIBCO Service Gateway™ for DB2 Installing and Operating Software Release 5.2.0
TIBCO® Object Service Broker Messages With Identifiers Software Release 5.2.0

S6BD2036E module: SQLCODE -818 error code may result if BIND PLAN not correctly performed after installation of new release or maintenance.