Why is it that Packages displayed under CICS correlation id (TRANID) on 'DETECTOR Key Package/DBRM Display' screen do not match the packages that are used by that CICS transaction?

Document ID : KB000024384
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction: 

This document states why Packages displayed under CICS correlation id (TRANID) on the 'DETECTOR Key Package/DBRM Display' screen may not match the packages that are used by that CICS transaction.

Question: 

Why is it that Packages displayed under CICS correlation id (TRANID) on the 'DETECTOR Key Package/DBRM Display' screen do not match the packages that are used by that CICS transaction?

Environment:  

z/OS 1.11 and above.

Answer: 

If sign on reuse occurs by a thread using a primary authorization ID which remains constant across multiple transactions (for example, by using AUTHID(name) in DB2CONN), only one sign on will occur. In this instance the tttt in the correlation ID does not match the running transaction ID. It is the ID of the transaction for which the initial sign on occurred. This is normal during thread reuse situations. 

To resolve this either:

Define ACCOUNTREC(TXID) or,

Define a unique DB2ENTRY and DB2CONN in CICS Resource definition, so that a sign on occurs for the new transaction.

Additional Information:

There are performance considerations in choosing ACCOUNTREC(TXID). Please see IBM documentation on this subject.