IBM Support

IT30267: After REFRESH CLUSTER the DISPLAY CLUSQMGR output lists more queue managers than it should

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The user runs REFRESH CLUSTER and notices soon afterwards that
    queue managers continue to be listed in DISPLAY CLUSQMGR output
    for a long time, even though the channels to them have ended.
    In this state they should have been removed from the list output
    from DISPLAY CLUSQMGR.
    

Local fix

  • Restarting the queue manager, or waiting one hour, should be
    enough to clear these items from the list.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users in the scenario described, who run REFRESH CLUSTER and
    inspect the output from DISPLAY CLUSQMGR.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In the scenario described, the channels code was notifying the
    cluster repository manager of the channel-ending condition too
    soon, before the channel program had fully ended.
    
    The cluster repository manager checked and saw that the channel
    program was still running, so decided to postpone the state
    update, and wait an hour.  In most circumstances this is good
    enough, but if an administrator looks at the status and sees the
    queue manager still listed in DISPLAY CLUSQMGR for up to an
    hour, they may not understand the internal reasons for this, and
    become concerned.
    

Problem conclusion

  • The channels code has been changed so that it notifies the
    cluster repository manager of the channel-ending condition a
    little later, when the program has fully ended.  This means the
    cluster repository manager will clean up properly much sooner
    than one hour (in normal circumstances, probably less than one
    second) after the channel ends.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 CD    9.1.4
    v9.1 LTS   9.1.0.4
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30267

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-12

  • Closed date

    2019-09-24

  • Last modified date

    2019-09-24

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

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

Document Information

Modified date:
24 September 2019