PH10645: CSQX053E XFFSXCSFREEOWNEDBUFFERS DIDN'T FREE THEIR BUFFER. SUBSEQUENT CONVERSATIONS USING SAME BUFFER ISSUE THE FFST AGAIN.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a conversation ended, xcsFreeOwnedBuffers detected that the
  conversation owned a buffer that had not been freed and issued
  CSQX053E message.
  
  The CSQSNAP shows:
  *        X...XFFSxcsFreeOwnedBuff*
  *ers.............MOVR.........!..*
  *X...XINS........Owner didn't fre*
  *e their buffers.................*
  *................................*
  
  Each time the conversation was reused, when it ended the same
  buffer was detected and the FFST was issued again.
  

Local fix

• Restarting the chinit will clear the error state.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 8       *
  *                 Release 0 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: During end of conversation processing,  *
  *                      we attempt to locate conversation       *
  *                      buffers which haven't been freed. If    *
  *                      we detect any, we issue a snap dump to  *
  *                      store their contents in a CSQSNAP       *
  *                      dataset. The logic in the code results  *
  *                      in the same buffer being dumped each    *
  *                      time the conversation is reused.        *
  ****************************************************************
  When determining whether to issue an FFST and a snap dump for a
  conversation buffer, there is not a check for whether the buffer
  has been dumped previously. This can result in repeated FFSTs
  being issued for the same buffer each time the conversation is
  reused. This could give the impression of a reoccurring problem
  rather than a single instance of a buffer not being freed.
  

Problem conclusion

• The code has been changed to not issue an FFST for conversation
  buffers which have already been dumped. Additionally, when a
  conversation buffer is detected as having not been freed, a
  system dump is taken in addition to the snap dump.
  

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:

  PH23759 UI70159

Modules/Macros

• CSQXBPC2 CSQXBPCS CSQXXFST
  

Fix information

• Fixed component name

  IBM MQ Z/OS V8

• Fixed component ID

  5655W9700

Applicable component levels

• R000 PSY UI70159

     UP20/08/08 P F008

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.