PM96230: PARSING ERROR IN ENVIRONMENT TREE CONSUMED BY FLOW DEBUGGER.

APAR status

• Closed as program error.

Error description

• When debugging a message flow that parses data into the
  environment tree, the message flow does not throw an exception
  when an invalid message is processed and debugged line by line
  through a message processing node.
  
  The exception is temporarily visible within the
  WMQI_DebugMessage tree in the flow debugger, but disappears when
  the next line of code is processed. The exception is not
  thrown, and the message flow continues as though the exception
  had not occurred.
  
  If you step over the message processing node, rather than
  stepping into source, then the exception is thrown as expected.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V8.0 and IBM Integration
  Bus V9.0 using the message flow debugger.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  This problem occurs when a message flow parses data into the
  environment tree. If an invalid message is input into the
  flow, and debugged line by line through a message processing
  node, using the message flow debugger, the message flow does not
  throw an exception.
  
  The exception is temporarily visible within the
  WMQI_DebugMessage tree in the message flow debugger, but
  disappears when the next line of code is processed. The
  exception is not thrown, and the message flow continues as
  though the exception had not occurred.
  
  If you step over the message processing node, rather than
  stepping into source, then the exception is thrown as expected.
  
  If you parse data into the main message tree, rather than the
  environment tree, then the exception is also thrown as 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 reports exceptions, caught by the message flow
  debugger and relating to the environment tree, back to the
  broker.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.1
  v8.0       8.0.0.4
  
  The latest available maintenance can be obtained from:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27009742
  
  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 MB Z/OS

• Fixed component ID

  5697P4400

Applicable component levels

• R800 PSY

     UP