IT15661: ALLOW MAPPING INPUT XML SUBTREES WITH NAMESPACE PREFIX CLASHES

APAR status

• Closed as program error.

Error description

• When using the Mapping node to transform input data which
  includes folders that are copied from separate input documents
  it is possible that the same namespace prefix could be used in
  these folders for different namespace URIs. This can lead to
  the Mapping node failing with:
  
  "IXJXE0466E: sequence contains two or more namespace nodes
  that map the same prefix to different namespace URIs"
  
  when a multiple input mapping, such as submap, is invoked with
  elements from the folders.
  

Local fix

• The issue only occurs when invoking a multiple input transform
  from elements from the separate folders that cause the clashing
  namespace prefix to be in scope. It might be possible to
  restructure the transformation to avoid this.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V10.0 who use the Mapping node
  with Graphical Data Maps that include multiple input mappings
  from folders that originate from separate XML documents.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using the Mapping node to transform input data which
  includes folders that originate from separate input documents it
  is possible that the same namespace prefix could be used in
  these folders for different namespace URIs. This can lead to the
  Mapping node failing with:
  
  "IXJXE0466E: sequence contains two or more namespace nodes that
  map the same prefix to different namespace URIs"
  
  when a multiple input mapping, such as submap, is invoked with
  elements from these folders.
  
  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_RELABEL_CLASH_IP_NS_PREFIX
  
  Note that when this fix mode is enabled the XPath function
  fn:in-scope-prefixes() becomes non conformant since any clashing
  namespace prefixes will be reported using an internally renamed
  prefix.
  
  Note that this fix is also enabled if the environment variable
  
  MQSI_MAP_ENABLE_SUBMAP_MULTIDEFAULTNS
  
  has been set to enable related APAR IT14940 <a
  href="https://jazza03.hursley.ibm.com:9443/ccm/resource/itemName
  /com.ibm.team.workitem.WorkItem/60116">MAPPING SUBMAP ELEMENTS
  IN DIFFERENT NAMESPACES (60116)</a>
  
  ---------------------------------------------------------------
  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