IBM Support

IT31027: After applying maintenance channel reports AMQ9514 even though AdoptNewMCA function is enabled

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

  • After applying a version of MQ containing a fix for APAR IT27810
    the AdoptNewMCA capability stopped working, the consequence of
    this is that MQ could not automatically recover and successfully
    restart a channel where the receiving MCA had hung.
    
    A channel that is attempting to restart as a result of a network
    error reports AMQ9514 (channel is in use), even though the
    AdoptNewMCA setting is configured to allow the new channel
    instance to take over.
    

Local fix

  • TCP/IP Keepalive and/or channel heartbeats may be effective
    where network connectivity has been lost.
    
    If a responding channel agent is otherwise hung, for example
    blocked in a channel exit, issuing a STOP CHANNEL(channel_name)
    MODE(FORCE) STATUS(INACTIVE) on the responding end of the
    connection should allow a subsequent restart from the initiating
    side of the channel to be successful.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users that rely on Adopt MCA are potentially affected.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Adopt MCA function enables IBM MQ to cancel a receiver
    channel and start a new one in its place. Additional checks were
    added by APAR IT27810 to ensure only only a single channel
    pairing could run between two queue managers which prevents the
    Adopt MCA function from working correctly.
    

Problem conclusion

  • The order of the checks is corrected to permit the Adopt MCA
    function, if configured to cancel a receiver channel.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.15
    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

    IT31027

  • 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-11-20

  • Closed date

    2020-02-18

  • Last modified date

    2020-06-01

  • 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

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 June 2020