IBM Support

IT12125: MESSAGE FLOW STATISTICS SHOWS MESSAGES WITH ERROR EVEN WHEN THERE HAS NOT BEEN AN ERROR

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

  • When using a message flow containing an MQInput node and message
    flow statistics is enabled, then it is possible that the
    statistics output will report a "messages with error" count even
    when there has not been an error.
    
    This occurs when the MQInput node tries to MQGET a message and
    the buffer provided on the MQGET call is not large enough. The
    MQInput node handles the error returned from this by increasing
    its buffer size and trying again. This is not an error scenario
    and should not result in an increase in the "messages with
    error" (field MFLERMG in SMF117 records on zOS) in the message
    flow statistics.
    
    This is particularly visible when using the statistics display
    in the web user interface to look at errors, when you might
    occasionally see a "messages with error" count greater than 0
    displayed.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V8.0 and IBM Integration
    Bus V9.0 who use the MQInput node and enable message flow
    accounting and statistics.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using a message flow containing an MQInput node and message
    flow statistics is enabled, then it is possible that the
    statistics output will report a "messages with error" count even
    when there has not been an error.
    
    This occurs when the MQInput node tries to MQGET a message and
    the buffer provided on the MQGET call is not large enough. The
    MQInput node handles the error returned from this by increasing
    its buffer size and trying again. This is not an error scenario
    and should not result in  an increase in the "messages with
    error" (field MFLERMG in SMF117 records on zOS) in the message
    flow statistics.
    
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT12125

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-05

  • Closed date

    2016-06-14

  • Last modified date

    2016-08-23

  • 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

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020