IT14940: MAPPING SUBMAP ELEMENTS IN DIFFERENT NAMESPACES

APAR status

• Closed as program error.

Error description

• Additional Symptom(s) Search Keyword(s):
  When a submap contains elements that will be defining the same
   namespace prefix to different URIs, a runtime error may occur.
  
  This will typically only relate to calling a submap transfrom
  with multiple inputs that originate from different XML documents
  that are being merged, for example if one or more XML documents
  are placed in the Environment tree to be mapped from. The submap
  can be created in the Map Editor but may fail in the runtime
  with an error containing the root cause:
     IXJXE0466E: sequence contains two or more namespace nodes
  that map the same prefix to different namespace URIs.
  Note that the issue will typically be that the default (no-name
  prefix) namespaces of used in the XML documents are different.
  

Local fix

• Convert the submap into the main map (Refactor from Submap menu)
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  IBM Integration Bus users using Mapping node with a multiple
  input submap transforming elements from separate XML document
  with different namespaces.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a submap contains elements that will be defining the same
   namespace prefix to different URIs, a runtime error may occur.
  
  This will typically only relate to calling a submap transfrom
  with multiple inputs that originate from different XML documents
  that are being merged, for example if one or more XML documents
  are placed in the Environment tree to be mapped from. The submap
  can be created in the Map Editor but may fail in the runtime
  with an error containing the root cause:
     IXJXE0466E: sequence contains two or more namespace nodes
  that map the same prefix to different namespace URIs.
  Note that the issue will typically be that the default (no-name
  prefix) namespaces of used in the XML documents are different.
  
  
  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 provides a fix in which this error no longer
  occurs.  To enable this fix, the following environment variable
  has to be set to any value:
  
  MQSI_MAP_ENABLE_SUBMAP_MULTIDEFAULTNS
  
  Note that when this fix mode is enabled the XPath function
  fn:in-scope-prefixes() becomes non conformant with regards to
  the default (no-prefix) namespace.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.5
  
  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