IT14780: FILEINPUT NODE DOES NOT EMIT MONITORING EVENTS CORRECTLY

APAR status

• Closed as program error.

Error description

• The FileInput node emits extra or duplicate rollback events when
  there is an exception at downstream nodes which causes the
  message to rollback. It is also observed that the Transaction
  Start and End events are not generated during the backout
  processing of the file.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker v8.0 and IBM Integration
  Bus v9.0 & v10.0 using monitoring events.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The FileInput node emits duplicate rollback events when there is
  an exception downstream flow that results in message rollback.
  It is also observed that the Transaction Start and Transaction
  End events are not generated during the backout  processing of
  the file.
  
  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

• The FileInput node now generates correct set of monitoring
  events during Rollback and backout processing.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.6
  v8.0       8.0.0.8
  v9.0       9.0.0.6
  
  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEB MESSAGE BRO

• Fixed component ID

  5724J0520

Applicable component levels