Resolution:
A S0C4 abend may result when processing a DB2 table using TIBCO Object Service Broker for z/OS 5.0.0 in conjunction with TIBCO Service Gateway™ for DB2 5.0. IMS and IDMS gateway servers may also be affected.

Environment:
z/OS running TIBCO Object Service Broker for z/OS 5.0.0 sessions accessing DB2, IMS or IDMS table data.

Products affected:
1) TIBCO Object Service Broker for z/OS 5.0.0
2) TIBCO Service Gateway™ for DB2 5.0
3) IBM DB2 Universal Database for z/OS
4) IBM IMS
5) CA IDMS™

Symptoms:
Rule failure with: ERROR=S0C4  S6BDRSES.TAMT01  +013EE VERSION=12/17/08 09.14 V5R0M1152


Cause:
IMS, DB2 and IDMS Gateway code has a buffer-length calculation issue whereby under certain conditions the data in a buffer may overrun by 1 byte and, depending on what follows the data buffer, unpredictable results may be produced including a S0C4 abend in module S6BDRSES.TAMT01.

Resolution:
Apply the latest hotfix to your gateway servers as follows:
*DB2: Hotfix 01 AP12199 /* Fix S0C4 in S6BDRSES caused by strg ovlay - DB2 */
*IMS: Hotfix 01 AP12201 /* Fix S0C4 in S6BDRSES caused by strg ovlay - IMS */
*IDMS: Hotfix 01 AP12200 /* Fix S0C4 in S6BDRSES caused by strg ovlay - IDMS */

Please note: The above hotfixes refer to the TIBCO "Service Gateway" products and not to the base TIBCO Object Service Broker for z/OS base product. You will need to download the specific hotfix datasets for each service gateway that you have installed.

For further information on obtaining these fixes, please open a service request with TIBCO Support and reference CR 1-8NKTMF.

References:
1) Problem Report CR 1-8NKTMF