IBM Support

IT25687: MQINPUT NODE WITH RESET BROWSE TIMEOUT DOES NOT BROWSE THE MESSAGES CORRECTLY FOR THE FIRST TIME AFTER FLOW START.

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 customer has configured an MQInput node with 'Browse Only'
    set and 'Reset browse timeout' set to a small positive value.
    The intention here is to ensure that in the event of a
    downstream exception that the same message is browsed
    repeatedly. This all works as expected *until* they restart the
    flow. In v10, instead of browsing the first message repeatedly,
    MQGMO_BROWSE_FIRST, (until the exception has been fixed), each
    message in turn is browsed before then returning to the first
    message and browsing it repeatedly.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and IBM App Connect
    Enterprise V11 using MQInput node to browse MQ messages.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The user has configured an MQInput node with 'Browse Only'
    option and has 'Reset browse timeout' set to a small positive
    value.  The intention here is to ensure that the first message
    is browsed repeatedly till its removed. This all works as
    expected until they restart the flow. After restart, instead of
    browsing the first message repeatedly, each message in turn is
    browsed before then returning to the first message and browsing
    it repeatedly.
    

Problem conclusion

  • The MQInput node is fixed to browse the messages correctly,
    based on  browse timeout value, after the flow restart.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.14
    v11.0      11.0.0.2
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25687

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-13

  • Closed date

    2018-09-19

  • Last modified date

    2018-09-19

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 September 2018