IBM Support

PI43703: WMQ CLUSTER TOPIC NOT PROPAGATED FROM WMQ FULL REPOSITORY IN Z/OS TO PARTIAL REPOSITORIES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When it is created a Topic in a Cluster, the info is only
    propagated to the Full Repositories in the Cluster, but not to
    the Partial Repositories. The two Full Repositories are located
    in a WMQ in z/OS, and the Partial Repositories are located also
    in WMQ in z/OS and WMQ in Distributed Platforms.
    
    The dump shows that QMGR does not have a hash (#) subscription,
    and that is the problem. A REFRESH CLUSTER on that partial
    should have caused the # subscription to be sent to QMGR but it
    is still not there. It has either not been sent, or QMGR is
    rejecting it.
    

Local fix

  • No local fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Clustered topics are not correctly      *
    *                      propagated to partial repository queue  *
    *                      managers.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When topics are defined in a cluster, a special subscription
    (SUBSCRIPTION_FOR_ALL_CLTS) is created and used to cause the
    topic definitions to be distributed to all queue managers in the
    cluster. This subscription includes characters that are variant
    in EBCDIC, and it is possible that when the command message sent
    to create the subscription is converted in to a given queue
    manager's ccsid, these special characters are at a different
    code point to that expected. When this occurs, the subscription
    is not processed correctly and any cluster topic
    definitions/updates will not be correctly propagated around the
    cluster.
    

Problem conclusion

  • The code responsible for handing the SUBSCRIPTION_FOR_ALL_CLTS
    subscription is updated to account for the inclusion of variant
    characters, so that any future definitions and/or updates to
    clustered topics are correctly propagated around the cluster.
    100Y
    CMQXRECO
    CMQXRMNT
    CSQXRRMF
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI43703

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-25

  • Closed date

    2015-11-18

  • Last modified date

    2016-09-15

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

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

    PI51003 UI33056

Modules/Macros

  • CMQXRECO CMQXRMNT CSQXRRMF
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI33056

       UP15/12/15 P F512 ¢

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 September 2016