PM67917: WMQ V7: USING MESSAGE SELECTOR "IS NULL" WORKS FOR "JMSTYPE" AND OTHER FIELDS, BUT DOES NOT WORK FOR JMSCORRELATIONID.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A WebSphere MQ V7 queue manager stored a message with
  JMSCorrelationID:
  ID:000000000000000000000000000000000000000000000000
  .
  However it is not strictly a NULL value in WMQ V7.
  When trying to use message selector to get messages
  by specifying "JMSCorrelationID IS NULL", the message with
  JMSCorrelationID:
  ID:000000000000000000000000000000000000000000000000
  will not be returned.
  .
  If the message selector is set to
  "JMSCorrelationID IS NOT NULL", this message will be returned.
  .
  When using message selector "IS NULL" for "JMSType"
  it works fine.
  

Local fix

• As a workaround, try using the selection string
  JMSCorrelationID =
  'ID:000000000000000000000000000000000000000000000000'
  which should return messages correctly.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1 and WebSphere MQ    *
  *                 for z/OS Version 7 Release 1 Modification 0. *
  ****************************************************************
  * PROBLEM DESCRIPTION: A JMS client attempting a MQGET on a    *
  *                      queue with a selector on JMSMessageID,  *
  *                      JMSCorrelationID or JMSXGroupID, with   *
  *                      the criteria 'IS NULL' will not return  *
  *                      messages that meet the criteria.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Using the 'IS NULL' criteria in a selection string for the
  message properties JMSXGroupID, JMSMessageID and
  JMSCorrelationID in a JMS client will not result in messages
  with NULL properties being returned from MQGET. These properties
  may be stored in messages with a NULL string value, such as
  'ID:000000000000000000000000000000000000000000000000' for
  JMSCorrelationID, when the values are set as NULL before an
  MQPUT. The selector does not equate the NULL string value to
  NULL. As such when the selector is applied against the value,
  the criteria will not be met and the message will not be
  returned by the MQGET.
  

Problem conclusion

• The properties returned to the selection processing for these
  message properties has been changed to ensure the selector
  equates the NULL string values to NULL. The properties
  JMSMessageID, JMSCorrelationID and JMSXGroupID are now compared
  to a NULL character string, such as MQGI_NONE for JMSXGroupID.
  If the comparison is successful, the property value returned to
  the selector is a NULL pointer, this ensures the selector
  equates the property to NULL, allowing the 'IS NULL' selection
  criteria to return the appropriate messages on a MQGET.
  010Y
  100Y
  CMQZRFPA
  

Temporary fix

Comments

APAR Information

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

  IV18623

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

  UK90344 UK90345

Modules/Macros

• CMQZRFPA
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK90344

     UP13/02/05 P F302

• R100 PSY UK90345

     UP13/02/05 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.