IBM Support

PI54093: CLUSTER WORK LOAD BALANCE ISSUE WHEN USING IGQ ENABLED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the application putting the messages to
    the cluster queue is connected to a queue-manager
    with IGQ enabled, the messages are getting
    workload-balanced twice (by the queue-manager which
    the application is connected to, and then by
    the queue-manager receiving the
    already-workload-balanced messages via IGQ).
    .
    This situation should not be occurring
    (the messages should only be workload-balanced by
    the queue-manager that the application is connected to).
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Messages are not distributed as         *
    *                      expected to cluster queues if the       *
    *                      putting application is connected to a   *
    *                      queue manager which has Intra-group     *
    *                      queuing enabled.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When messages are sent to remote cluster queues using IGQ
    and the local instance of the cluster queue is defined with
    BIND(NOTFIXED) then they are put to the
    SYSTEM.QSG.TRANSMIT.QUEUE with RemoteQmgrName blank in the XQH.
    On the receiving side these messages are considered to be
    eligible for workload balancing and many of them will be
    erroneously distributed a second time. IGQ should ensure
    that these messages are not redistributed in this situation.
    Additional keyword: PK32886
    

Problem conclusion

  • CSQMPUTV has been changed to detect if the messages arrived via
    IGQ and not redistribute them.
    000Y
    CSQMPUTV
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI54093

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-14

  • Closed date

    2016-03-29

  • Last modified date

    2016-06-02

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

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

    UI36553

Modules/Macros

  • CSQMPUTV
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI36553

       UP16/05/04 P F605

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 June 2016