Tuxedo 11gR1PS1 (11.1.1.2.0): tpbeing() May Receive An XAER_PROTO Error After Abend In CICS Call Through Tuxedo Mainframe Adapter (TMA) For SNA. (Doc ID 1589323.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Goal

From times to times a DB2 transaction generated a "TPEPROTO" error after a "TMA" autotran service (DPL program) call failed with a TPESVCFAIL.

This mis-behavior would be link to IBM DB2's interpretation of the XA standard which implies an XAER_PROTO on xa_rollback() because DB2 has interpreted the XA standard to say that rollback is not allowed if a participant is currently registered (checked by ax_reg()) with a suspended association.

Here after an Ulog sample with ax_reg returns -1:

 

152436.677.boxname!servername.17729.2943713024.0: gtrid x0 x522973ee x210: TRACE:at: } tpfree
152436.679.boxname!servername.17729.2943713024.0: gtrid x0 x522973ee x210: TRACE:xa: { ax_reg(0, 0x0x7fffffffc520, 0)
152436.679.boxname!servername.17729.2943713024.0: TRACE:xa: } ax_reg = -1
152436.680.boxname!servername.17729.2943713024.0: TRACE:at: { tx_info(0x0x7fffffffc8f0)
152436.680.boxname!servername.17729.2943713024.0: TRACE:ia: { tpgetlev()
152436.680.boxname!servername.17729.2943713024.0: TRACE:ia: } tpgetlev = 0
152436.680.boxname!servername.17729.2943713024.0: TRACE:at: } tx_info = 0
152436.680.boxname!servername.17729.2943713024.0: TRACE:at: { tpalloc("CARRAY", "", 30820)
152436.680.boxname!servername.17729.2943713024.0: TRACE:at: } tpalloc = 0x0x6d5a58

 


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms