IT03180: MONITORING EVENTS FAIL WITH DATETIME PAYLOAD ELEMENTS

APAR status

• Closed as program error.

Error description

• When creating monitoring events for a message flow, you can
  create one or more Event Payload elements based on locations in
  the message tree. These are specified using XPath expressions.
  If one of these XPath expressions resolves to a location
  containing a datetime element, the monitoring event may fail to
  publish. This occurs if the element's value is stored within the
  message tree as a GMTTIMESTAMP datatype. For example, the
  following element within the LocalEnvironment structure exhibits
  this problem:
  
  $LocalEnvironment/File/LastModified
  
  When the monitoring event fails, the following messages are
  observed in the local error log:
  
  BIP3915I: Message flow '''' failed to emit a
  monitoring event from event source ''''.
  BIP2328E: A value of SQL datatype ''GMTTIMESTAMP'' encountered
   when datatype ''TIMESTAMP'' expected.
  

Local fix

• To work around this issue, you can specify the enclosing
  subtree rather than a specific element.
  In the previous example, this XPath expression will
  successfully result in monitoring events being published:
  $LocalEnvironment/File
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V9.0 who create monitoring
  events with Event Payload parts pointing to specific elements in
  the message tree.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When creating monitoring events for a message flow, you can
  create one or more Event Payload elements based on locations in
  the message tree. These are specified using XPath expressions.
  If one of these XPath expressions resolves to a location
  containing a datetime element, the monitoring event may fail to
  publish. This occurs if the element's value is stored within the
  message tree as a GMTTIMESTAMP datatype. For example, the
  following element within the LocalEnvironment structure exhibits
  this problem:
  
  $LocalEnvironment/File/LastModified
  
  When the monitoring event fails, the following messages are
  observed in the local error log:
  
  BIP3915I: Message flow '''' failed to emit a
  monitoring event from event source ''''.
  BIP2328E: A value of SQL datatype ''GMTTIMESTAMP'' encountered
   when datatype ''TIMESTAMP'' expected.
  
  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 product now successfully allows timestamps to be specified
  as monitoring event payload elements, regardless of whether they
  are stored as TIMESTAMP or GMTTIMESTAMP.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.3
  
  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

  INTEGRATION BUS

• Fixed component ID

  5724J0530

Applicable component levels

• R900 PSY

     UP