IT34846: MONITORING EVENT FOR TERMINAL IS NOT EMITTED IF NODE'S OUT TERMINALS ARE NOT WIRED

APAR status

• Closed as program error.

Error description

• If a monitoring event is configured for a node's out terminal
  but that terminal is not actually wired up to any downstream
  node then a monitoring event is not emitted.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise using monitoring events.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Monitoring events of type  'out' terminals are not being
  generated when the terminal is not connected.
   This Apar is applicable to only those nodes (message processing
  nodes) that propagate message to 'out' terminal even if the
  terminal is not wired. For example 'Trace' node, compute node,
   Filter node etc..
  

Problem conclusion

• The product now generates monitoring events for  the 'out'
  terminal  when the message is propagated to the 'out' terminal
  of message processing node regardless of  whether it is wired to
  downstream nodes or not.
  
  This Apar is not applicable to the nodes that are of  type
  'Output',  like MQOutput node,  Http Reply Node, FileOutput node
  etc..  These nodes being of  the type 'output',  terminate the
  transaction and do no propagate the message further down the
  'out' terminal if they are not wired further. If there is no
  propagation to out terminal,  the event of type 'out' terminal
  will not be emitted by these 'output' nodes.  This is expected
  behaviour.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.12
  
  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

  APP CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels