PI54507: TRACKING INCORRECTLY INCLUDES MQ LOG RECORDS THAT ARE UNRELATED TO THE TRANSACTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When merging the IMS and MQ logs, transaction tracking
  incorrectly selects multiple MQ PUT log records that are not
  related to the transaction being tracked. The problem occurs
  when the MQ Bridge sends multiple transaction messages to IMS
  prior to issuing a commit (the completion of the MQ
  unit-of-work). The MQ records are being correlated by their MQ
  URID token and hence included in the tracking result set, even
  though each result is in a distinct and independent IMS
  transaction.
  
  Keywords: Function TX track
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Problem Investigator V2.4       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Tracking incorrectly includes MQ log    *
  *                      records that are unrelated to the       *
  *                      transaction                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When merging the IMS and MQ logs, transaction tracking
  incorrectly  selects multiple MQ PUT log records that are not
  related to the transaction being tracked. The problem occurs
  when the MQ Bridge sends multiple transaction messages to IMS
  prior to issuing a commit (the completion of the MQ unit-of-
  work). The MQ records are being correlated by their MQ URID
  token and hence included in the tracking result set, even
  though they each result in a distinct and independent IMS
  transaction.
  

Problem conclusion

• Tracking is changed to only include MQ log records in the result
  set of an IMS transaction when the MQ message belongs to that
  transaction. The MQ URID will no longer be used as a tracking
  token when an IMS log record is used to start tracking. Only the
  OTMA logon token will be used to correlate the IMS log to the MQ
  log. The result will be that only MQ PUT and GET log records
  that are directly related to the transaction s input and output
  messages will be included in the tracking result set.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI35444

Modules/Macros

• ALZTRACK ALZTUTRK
  

Fix information

• Fixed component name

  IMS PROBLEM INV

• Fixed component ID

  5655K5000

Applicable component levels

• R240 PSY UI35444

     UP16/02/19 P F602

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.