IBM Support

IT30610: Cluster channel is put into STOPPED state after running command REFRESH CLUSTER REPOS(YES)

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

  • REFRESH CLUSTER REPOS(YES) should stop and restart active
    channels.
    However, running the command moved a channel into STOPPED state
    and the channel is not restarted automatically.
    

Local fix

  • REFRESH CLUSTER REPOS(NO) can be used as it does not attempt to
    stop channels. Alternatively, manually start the affected
    channel(s) after the REFRESH CLUSTER operation.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using REFRESH CLUSTER REPOS(YES) command
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The REFRESH CLUSTER REPOS(YES) command stops and restarts the
    cluster channels during
    cluster refresh. A defect in the MQ cluster refresh code meant
    that channel status was not set to INACTIVE for a channel that
    had been stopped during refresh. This caused affected the
    channel to remain in STOPPED state until the user restarted the
    channel manully using the START CHANNEL command.
    

Problem conclusion

  • The IBM MQ queue manager code has been modified to resolve the
    cluster channel problem during cluster refresh.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.14
    v9.0 LTS   9.0.0.9
    v9.1 CD    9.1.5
    v9.1 LTS   9.1.0.5
    
    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

    IT30610

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-16

  • Closed date

    2020-01-13

  • Last modified date

    2020-01-13

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

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

    PH20948

Fix information

  • Fixed component name

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

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":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
13 January 2020