PI54505: TRACKING INCORRECTLY INCLUDES IMS LOG RECORDS THAT ARE UNRELATEDTO THE TRANSACTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When merging log files from multiple systems, transaction
  tracking incorrectly selects records from another system that
  are not related to the transaction being tracked. This occurs
  when the only tracking token available in the record is the
  region PST ID. Tracking is not taking into account that the same
  PST ID can be active on more than one system. An example of this
  is when x'18' BMP extended checkpoint records are being included
  in the tracking result set of an MPP transaction. The x'18'
  records are for a BMP that executed on another system at the
  same time, and in no way related to the MPP transaction being
  tracked.
  
  Keywords: Function TX track PSTID
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Problem Investigator V2.4       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Tracking incorrectly includes IMS log   *
  *                      records that are unrelated to the       *
  *                      transaction.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When merging log files from multiple systems, transaction
  tracking incorrectly selects records from another system
  that are not related to the transaction being tracked.
  This occurs when the only tracking token available in the
  record is the region PST ID. Tracking is not taking into
  account that the same PST ID can be active on more than
  one system. An example of this is when x 18  BMP extended
  checkpoint records are being included in the tracking
  result set of an MPP transaction. The x 18 records are
  for a BMP that executed on another system at the same time,
  and in no way related to the MPP transaction being tracked.
  

Problem conclusion

• Tracking is changed for IMS log records whose only tracking
  token is the region PST ID to take into account the IMS
  system they belong to. These records will now only be
  selected when another record in the same log file has
  already established the correlation between the PST ID
  and the transaction's recovery token. Records with the
  the same PST ID but in another log file (belonging to
  to another system) will no longer 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:

  UI35216

Modules/Macros

• ALZTRACK ALZTUTRK ALZ1DZ   ALZ55A   ALZ55B
  ALZ55C   ALZ55D   ALZ55E   ALZ6701A ALZ6701B ALZ6701C ALZ6701D
  ALZ6701E ALZ6705A ALZ6705B ALZ6705C ALZ6705D ALZ6705E
  

Fix information

• Fixed component name

  IMS PROBLEM INV

• Fixed component ID

  5655K5000

Applicable component levels

• R240 PSY UI35216

     UP16/02/11 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.