IT15992: PARSING ERRORS WHEN PROPAGATING BETWEEN APPLICATION AND SHARED LIBRARIES

APAR status

• Closed as program error.

Error description

• If an input node in an application is wired directly to a
  subflow in a shared library, and that input node requires XML
  or DFDL schemas in the application, parsing errors may be seen
  in the subflow in the shared library. The parsing errors
  indicate that the XML or DFDL schemas cannot be found, and the
  error will point towards the wrong container. For example, if a
  DFDL message is propagated from an HTTPInput node in
  an application to a subflow in a shared library, and that
  HTTPInput node is configured to use the DFDL domain with DFDL
  schemas in that application, then the following error will be
  seen in the subflow in the shared library:
  
  BIP5854E: The DFDL serializer could not locate a message model
  for the shared library 'SharedLibrary1'.
  
  The problem occurs because the message loses context about
  where that message was created when it passes between an
  application and a shared library, or a shared library to
  another shared library, and cannot properly locate the XML or
  DFDL schemas. The problem only occurs when
  the "Parse timing" property of the node is set to "On Demand",
  and does not occur when "Parse timing" is set to "Immediate" or
  "Complete".
  
  A similar problem occurs when a request node in a subflow in a
  shared library, such as an MQGet node, propagates a message
  directly
  out of the subflow back to an application or another shared
  library.
  
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• Set the "Parse timing" property of all affected nodes to
  "Immediate" or "Complete" instead of "On Demand".
  An affected node is either an input or a request node that
  propagates directly to the output terminal of a subflow.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of shared libraries in IBM Integration Bus V10.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If an output terminal of an input node in an application is
  connected directly to a subflow in a shared library, then
  parsing errors may occur in that shared library if the DFDL,
  XMLNSC, or SOAP message domains are in use. The parsing errors
  may include BIP5057/BIP5058 (XMLNSC) or BIP5828/BIP5854 (DFDL)
  saying that no message model could be found for the specified
  container (application or shared library), or that the specified
  type does not exist. The parsing errors may also be seen if a
  new message is propagated from a subflow in a shared library
  (for example, from a read/receive node) back to a main flow in
  an application.
  
  The parsing errors occur because the parser loses information
  about the container (application or shared library) that created
  the parser. This information is required in order to locate the
  XML or DFDL Schema files that should be in scope for that
  parser. Without this information, it defaults to using the XML
  or DFDL Schemas in the container (application or shared library)
  that is performing the parsing - not the one that created the
  parser.
  
  The problem can be worked around by changing the "Parse timing"
  property to "Immediate" or "Complete". This forces the parsing
  to occur in the container (application or shared library) that
  creates the parser, rather than a downstream node that may be in
  a different container.
  
  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 parser and subflow infrastructure has been modified to
  handle container transitions (application to shared library,
  shared library to application, or shared library to shared
  library) correctly.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels

• RA00 PSY

     UP