IBM Support

IT40956: DISPLAY CHSTATUS for a SDR channel contained LONGRTS(0) SHORTRTS(0) but the channel had not retried many times

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

  • DISPLAY CHSTATUS for a SDR channel contained a STOPPED channel
    status with LONGRTS(0) SHORTRTS(0).
    
    Later the MQ administrator changed this channel to INACTIVE
    state.  Thereafter, if the SDR channel failed to start on the
    first trigger, it then went immediately into STOPPED status
    again without entering RETRYING.
    

Local fix

  • Issue START CHANNEL commands when the reason for channel abend
    has been resolved.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ SDR-RCVR channels who run STOP CHANNEL(channelname)
    STATUS(STOPPED) and then restart the queue manager.  After
    moving the channel to INACTIVE status, the user is then relying
    on automatic RETRYING behaviour if the channel cannot be started
    immediately.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Saved Channel Status had remembered a zero value for LONGRTS
    and SHORTRTS (number of long retries, and number of short
    retries, respectively).
    
    This was due to a defect within the MQ channels code that runs
    during STOP CHANNEL(channelname) STATUS(STOPPED), not due to the
    retries actually being attempted.
    

Problem conclusion

  • The reason for the LONGRTS(0) SHORTRTS(0) state has been
    identified and corrected.
    
    If requesting a fix for this issue, then a fix for IT40296
    should be requested at the same time.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.7
    v9.3 LTS   9.3.0.2
    v9.x CD    9.3.1
    
    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

    IT40956

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-16

  • Closed date

    2022-08-23

  • Last modified date

    2022-12-09

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

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

Document Information

Modified date:
09 December 2022