PI17378: MESSAGE PROPERTY ISSUES BETWEEN MESSAGESIGHT CLIENTS AND MQ

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Interoperability issues involving message properties on a
  MessageSight client and a V710 queue manager.
  
  MQMSGPROP/K
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Some clients, including IBM             *
  *                      MessageSight may result in errors when  *
  *                      getting messages with message           *
  *                      properties.                             *
  *                                                              *
  *                      This includes MQGET on a                *
  *                      message with MQTYPE_INT16 properties    *
  *                      from a client resulting in FFST's and   *
  *                      errors in the client.Additionally       *
  *                      an MQGET of some messages may not       *
  *                      return the messages properties.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Due to an issue in the routine used to convert MQTYPE_INT16
  properties, the NameLength field of the property returned is
  unexpectedly returned in a little endian form. This can result
  in errors in the client, that can also be in the form of an FFST
  when it attempts to convert the field from little to big endian.
  
  In some cases when a client puts a message, with message
  properties, the message handle used can be merged. This merged
  handle is passed during the MQPUT call along with an empty
  new handle. To prevent the merge occuring multiple times, only
  one handle is used. This can result in only the empty handle
  being used during the put.
  

Problem conclusion

Temporary fix

Comments

• The code has been updated to correct the conversion of
  MQTYPE_INT16 properties, and that the correct passed message
  handle is used. This corrects the issues with client and
  MessageSight applications with message properties.
  
  MQMSGPROP/K
  

APAR Information

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

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

  UI20239

Modules/Macros

• CMQKTORA CSQMPUTV CSQMTPUV
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R100 PSY UI20239

     UP14/08/30 P F408

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.