IBM Support

PI20898: WMQ z/OS: After PM97162, cluster objects in multiple clusters only appear to be in one of the clusters

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The code added by PM97162 incorrectly detects an error for
    cluster objects which have more than one cluster associated
    with them, i.e. overlapping clusters.
    .
    The result is that at start-up when the cluster cache is
    populated, only the first cluster associated with any cluster
    object will be restored when the cache is built. Since the
    order of the cluster objects is arbitrary, this causes the
    objects to appear to only be in one of the clusters at random.
    .
    The problem occurs even if the service parameter for PM97162
    has not been activated.
    .
    Additional Symptom(s) Search Keyword(s):
    .
    An MQPUT fails with reason 2270
    MQRC_NO_DESTINATIONS_AVAILABLE
    .
    And/or a CSQX053E with a snap for
    XFFSrrmCheckSubsForQueue
    Missing subscription.
    *        X...XFFSrrmCheckSubsForQ*
    *ueue............MOVR............*
    ..
    ..
    Another symptom:
    .
    +CSQX419I MQ1F3 CSQXREPO No cluster-receivers
       for cluster xxx.yyy.zzz
    .
    Looking at dump, you could see that there
    are CLUSRCVRs defined for each cluster
    associated with the CSQX419I error message,
    but the channel had a namelist with several
    clusters defined.
    .
    

Local fix

  • For the "MQPUT fails with reason 2270"
    MQRC_NO_DESTINATIONS_AVAILABLE: A dummy alter of the CLUSRCVR
    (which receives MQRC 2270) may temporarily clear the issue.
    Alternatively the CLUSNL attribute (which is defined on the
    CLUSSDR that is defined on the QMGR that has lost visibility to
    cluster objects) may be removed, and then re-instated to
    circumvent this issue. If neither local fix action has an
    effect then a REFRESH CLUSTER(*) (on the QMGR that has lost
    visibility to objects) should be done.
    Note:
    Before the next queue manager restart,
    you will need to back out PM97162 or
    apply PI20898 to prevent the error
    from occurring again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: After applying PM97162, PTF UI12014,    *
    *                      cluster objects defined in multiple     *
    *                      clusters using namelists will now only  *
    *                      be available in a single cluster.       *
    *                      Applications may get return code RC2270 *
    *                      (MQRC_NO_DESTINATIONS_AVAILABLE) on     *
    *                      MQPUT calls.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In the routine rebuilding the cluster cache at restart, the code
    added by PM97162 incorrectly tests a return code after adding
    the first cluster record to a cluster object in the cache.
    This causes the routine to exit early, without adding the
    remaining cluster records to the cluster object. Thus the
    cluster object is only available in a single cluster.
    

Problem conclusion

  • The code was changed to correctly check the return code and add
    all the cluster records to the cluster object.
    100Y
    CSQXRFIC
    CSQXRFXC
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI20898

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-26

  • Closed date

    2014-07-10

  • Last modified date

    2014-08-05

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

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

    UI19505

Modules/Macros

  • CSQXRFIC CSQXRFXC
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI19505

       UP14/07/22 P F407 «

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:
05 August 2014