IBM Support

IT32667: Sender channel does not stop as expected

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

  • A sender channel does not stop as expected by issuing "STOP
    CHANNEL(ChannelName) STATUS(INACTIVE)", in the following case.
    
    Queue Manager: QMGR1 - Channel: CH1(SDR)
    Queue Manager: QMGR2 - Channel: CH2(RQSTR)
    
    Steps:
    1. Stop the RQSTR channel CH2, then AMQ9558 ("Remote Channel is
    not currently available") occurs on QMGR1
    2. Issue "STOP CHANNEL(CH1) STATUS(INACTIVE)" on QMGR1
    
    Result:
    The "STOP CHANNEL" command itself succeeds (AMQ8019: Stop IBM
    MQ channel accepted), but the status of the SDR channel remains
    "RETRYING" and not moved to INACTIVE.
    
    When the "STOP CHANNEL" is issued again, the status is moved to
    INACTIVE immediately.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of MQ channels between queue managers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an outbound MQ channel such as a SDR, CLUSSDR, RQSTR or SVR
    channel ends unsuccessfully, it might schedule itself to retry
    later.  If an MQ administrator issued a STOP CHANNEL command for
    the channel at the same time it was ending, there was a timing
    window in which the stop request would be accepted, but the
    channel still scheduled itself to retry later.  DISPLAY CHSTATUS
    will showed STATUS(RETRYING) STOPREQ(YES) during this period,
    and the channel stopped when the next retry occurs.
    

Problem conclusion

  • MQ code has been modified to minimise the timing window where
    this problem could occur. Status checks were also added to
    process STOP requests during retry processing.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.13
    v9.1 LTS   9.1.0.10
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.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

    IT32667

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-28

  • Closed date

    2021-11-25

  • Last modified date

    2021-11-25

  • 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 M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
26 November 2021