PM82340: WMQ Z/OS: CSQX208E RC=00000461 MESSAGE FROM MQ CLIENT WHEN SHARECNV > 0 AND MESSAGE SIZE > 4016

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The problem occurs when a message that was
  put at V6 is got by a client with
  SHARECNV > 0 (SHARECNV greater than 0) and
  the size of the message is greater than 4016.
  .
  The queue-manager will obtain a new
  get-buffer for the client as the size of
  the default get-buffer is not large enough
  for the message.
  However, if a message from V6 is being
  processed, CSQIMGE5 does not update its
  pointers to address the new get-buffer.
  This results in the client being returned
  incorrect message data.
  .
  +CSQX208E ?xx CSQXRESP ERROR RECEIVING DATA,
   CHANNEL ChannelName,
   CONNECTION xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxxx)
   (QUEUE MANAGER ????)
   TRPTYPE=TCP RC=00000461 (ECONNRESET)
   REASON=00000000
  

Local fix

• Code SHARECNV=0
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Websphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A client issued MQGET may return        *
  *                      incorrect message data when getting     *
  *                      large (over 4016 byte) persistent       *
  *                      messages that were PUT by a V600 queue  *
  *                      manager.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Persistent messages over 4016 bytes in size, that were put to a
  queue prior to a migration from V600 may return incorrect
  message data. The buffer returned to the client application
  may not contain the message that was initially put to the queue.
  
  A larger buffer has to be obtained to service the MQGET of the
  large messages held on the queue. Due to the messages being
  originally put by a V600 queue manager, when the large message
  is retrieved, the buffer returned to the client does not contain
  the correct message data. Once a new buffer is obtained it is
  used while large messages continue to be retrieved and
  subsequent client MQGET requests will return the correct message
  data. As such this scenario may only occur on the first request
  for a larger message.
  

Problem conclusion

• The internal call used when a client application attempts to
  retrieve a message through a MQGET in this circumstance has been
  changed to ensure the new buffer is referenced after being
  obtained. As such the buffer returned to the calling client
  will contained the correct message data.
  010Y
  CSQIMGE5
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  PM82857 UK91839

Modules/Macros

• CSQIMGE5
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK91839

     UP13/02/28 P F302 Ž

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.