IBM Support

PM79660: MQ WORK WITH A SELECTOR DEFINED AS PART OF IT'S CLASSIFICATION FAILS TO BE CLASSIFIED BY WLM ON Z/OS

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When a selector is specified in a WebSphere MQ messaging
    provider classification, within the Workload classification
    file on z/OS, the selector fails to match any JMS Header
    Fields. As a result classification does not function as
    expected.
    
    The JMS Header Fields that should be allowed in a selector are
    as follows:
    JMSDeliveryMode, JMSPriority, JMSMessageID, JMSTimestamp,
    JMSCorrelationID, and JMSType
    
    An example of a failing workload classification is as follows:
    <WMQRAClassification default_transaction_class="ABCDE"
      schema_version="1.0">
    <wmqra_classification_info transaction_class="ABCDE"
      destination="queue:///MY.QUEUE"
     selector="JMSCorrelationID=&apos;ID:4d79436f7272656c61746f7240
    4040404040404040404040&apos;"
      description="CorrelId based selection"/>
    </WMQRAClassification>
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  V7.0, V8.0, and V8.5 using IBM WebSphere MQ *
    *                  as a messaging provider                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: z/OS workload classification using a    *
    *                      selector containing a JMS Header Field  *
    *                      fails for MQ                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A WMQRAClassification entry in the z/OS Workload
    Classification document can contain wmqra_classification_info
    entries that specify a 'selector'.
    The selector is intended to provide the JMS selection
    capabilities described in Section 3.8 of the Java Message
    Service specification Version 1.1.
    However, an attempt to classify messages based on a selector
    containing any JMS Header Field such as JMSCorrelationID fails.
    The selector instead behaves as if the JMS Header Field had a
    null value.
    

Problem conclusion

  • Updated the z/OS workload classification code for the
    WebSphere MQ resource adapter to function correctly for the
    following JMS Header Fields:
    JMSDeliveryMode, JMSPriority, JMSMessageID, JMSTimestamp,
    JMSCorrelationID, and JMSType
    
    APAR PM79660 is currently targeted for inclusion in Fix Packs
    7.0.0.29, 8.0.0.6 and 8.5.0.2 of WebSphere Application Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79660

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-21

  • Closed date

    2013-01-04

  • Last modified date

    2013-07-03

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

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK94926

       UP13/06/20 P F306

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.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM79660

Modified date: 03 July 2013