PH44182: SMF TYPE 116 SUBTYPE 10 FIELD QCSTSLCN CONTAINS BAD DATA

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When channel initiator accounting data collection is enabled,
  and a channel with STATCHL enabled goes inactive or ends, a
  copy of its channel status data is copied away. This channel
  status data is then parsed by a long-running SMF task at the
  next interval. It parses the channel status data and extracts
  the required information into a QCST block. This QCST block is
  then written to the SMF trace destination.
  
  The problem occurs when processing the data for fields QCSTSLSN
  and QCSTSLCN, which hold the serial number from SSLPEER and the
  CN from SSLCERTI respectively. The copy of the channel status
  data doesn't actually contain this data, only a pointer to this
  data in a cell pool. The problem is that the cells containing
  the SSLPEER and SSLCERTI data are freed to the cell pool
  shortly after making the copy of the channel status entry.
  
  When the long-running SMF task comes to process these fields
  during the next SMF interval, it will be reading from logically
  freed cells in the cell pool. It follows that the contents
  which it reads and extracts into QCSTSLSN and QCSTSLCN are
  inconsistent, and will depend on if the cells have been reused
  or not.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 1 Modification 0, Release 2          *
  *                 Modification 0 and Release 3 Modification 0. *
  ****************************************************************
  * PROBLEM DESCRIPTION: SMF type 116 subtype 10 fields QCSTSLCN *
  *                      and QCSTSLSN contain bad data.          *
  ****************************************************************
  When channel initiator accounting data collection is enabled,
  and a channel with STATCHL enabled goes inactive or ends, a
  copy of its channel status data is copied away. This channel
  status data is then parsed by a long-running SMF task at the
  next interval. It parses the channel status data and extracts
  the required information into a QCST block. This QCST block is
  then written to the SMF trace destination.
  The problem occurs when processing the data for fields QCSTSLSN
  and QCSTSLCN, which hold the serial number from SSLPEER and the
  CN from SSLCERTI respectively. The copy of the channel status
  data doesn't actually contain this data, only a pointer to this
  data in a cell pool. The problem is that the cells containing
  the SSLPEER and SSLCERTI data are freed to the cell pool
  shortly after making the copy of the channel status entry.
  When the long-running SMF task comes to process these fields
  during the next SMF interval, it will be reading from logically
  freed cells in the cell pool. It follows that the contents
  which it reads and extracts into QCSTSLSN and QCSTSLCN are
  inconsistent, and will depend on if the cells have been reused
  or not.
  

Problem conclusion

• SMF modules csqxsmfc and csqxsmft have been updated to save and
  reference the actual channel status data for fields QCSTSLSN and
  QCSTSLCN, rather than pointers to it.
  

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:

  UI92313 UI92314 UI92315

Modules/Macros

• CSQXSMFC CSQXSMFT CSQXTRTB
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R100 PSY UI92315

     UP23/07/15 P F307

• R200 PSY UI92314

     UP23/07/15 P F307

• R300 PSY UI92313

     UP23/07/15 P F307

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.