PI58173: TRACKING A CICS CMF TRANSACTION DOES NOT FIND THE CORRESPONDING DB2 ACCOUNTING RECORDS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Tracking the CICS CMF transaction to its corresponding DB2
  accounting records relies on the accounting token that is
  present in both records.
  The accounting token is a concatenation of two parts, the
  NETNAME and the NETUOWID.
  The problem occurs when the NETNAME second qualifier is less
  than 8 characters long.
  In CICS the name is padded with hex zero low values. In DB2 the
  name is padded with blanks.
  This difference causes the tokens to be mismatched when used by
  tracking.
  
  Summary of changes
  The CICS CMF accounting token used by tracking now pads the
  NETNAME with blanks.
  This allows tracking to match the CICS CMF transaction to its
  associated DB2 accounting records.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Transaction Analysis Workbench           *
  *                 Version 1 Release 3 users                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Tracking a CICS CMF transaction does    *
  *                      not find the corresponding DB2          *
  *                      accounting records.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Tracking the CICS CMF transaction to its corresponding DB2
  accounting records relies on the accounting token that is
  present in both records.
  The accounting token is a concatenation of two parts, the
  NETNAME and the NETUOWID.
  The problem occurs when the length of the NETNAME second
  qualifier is less then 8 characters.
  In CICS the name is padded with hex zero low values.
  In DB2 the name is padded with blanks.
  This difference causes the tokens to be mismatched when
  used by tracking.
  

Problem conclusion

• The CICS CMF accounting token used by tracking
  now pads the NETNAME with blanks.
  This allows tracking to match the CICS CMF transaction
  to its associated DB2 accounting records.
  
  Additional issues have also been resolved:
  1. CICS-DBCTL tracking from CMF to the IMS log now selects the
     one required transaction only.
  

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:

Modules/Macros

•    FUWTRACK FUWTUTRK FUW01V   FUW6E13Z FUW780BZ
  FUW7809Z
  

Fix information

• Fixed component name

  IBM TRANS ANALY

• Fixed component ID

  5697P3700

Applicable component levels

• R130 PSY UI36382

     UP16/03/23 P F603

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.