IBM Support

IT17577: COMMON SCHEMAS CLASH WHEN BUILDING BINARYIR FOR XMLNSC

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When deploying schemas the broker runtime will build a
    "binaryIR" file for all schemas in the application for the
    XMLNSC parser. If any libraries contain duplicate schemas, and
    the hash of the files does not match then this will cause a
    deployment error.
    
    In many cases the schemas causing a clash are either IBM
    Defined or part of a well known model such the SAP adapters
    ECI_DC40 schema. In these cases minor differences in the schema
    files, such as the presence of source control tags embedded in
    comments or re-ordering or attributes on elements can cause the
    hash of the files to be the same even through the content is
    syntactically identical leading to a deploy error.
    
    Additionally at version 9 it was possible to bypass schema
    compilation by setting the env var
    MQSI_DISABLE_SCHEMA_COMPILATION,
    this env var no longer works at V10.
    
    Additional Symptom(s) Search Keyword(s): Schemas, binaryIR
    XMLNSC SAP Adapters
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11 using XML schema files.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">When deploying
    schemas the broker runtime will build a </span><span
    style="background-color:rgb(255, 255, 255)">"binaryIR" file for
    all schemas in the application for the </span><span
    style="background-color:rgb(255, 255, 255)">XMLNSC parser. If
    any libraries contain duplicate schemas, and  </span><span
    style="background-color:rgb(255, 255, 255)">the hash of the
    files does not match then this will cause a </span><span
    style="background-color:rgb(255, 255, 255)">deployment error.
                                                 </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">In many cases
    the schemas causing a clash are either IBM </span><span
    style="background-color:rgb(255, 255, 255)">Defined or part of a
    well known model such the SAP adapters </span><span
    style="background-color:rgb(255, 255, 255)">ECI_DC40 schema. In
    these cases minor differences in the schema </span><span
    style="background-color:rgb(255, 255, 255)">files, such as the
    presence of source control tags embedded in </span><span
    style="background-color:rgb(255, 255, 255)">comments or
    re-ordering or attributes on elements can cause the </span><span
    style="background-color:rgb(255, 255, 255)">hash of the files to
    be the same even through the content is </span><span
    style="background-color:rgb(255, 255, 255)">syntactically
    identical leading to a deploy error.             </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">Additionally
    at version 9 it was possible to bypass schema </span><span
    style="background-color:rgb(255, 255, 255)">compilation by
    setting the env var </span><span
    style="background-color:rgb(255, 255,
    255)">MQSI_DISABLE_SCHEMA_COMPILATION, </span><span
    style="background-color:rgb(255, 255, 255)">this env var no
    longer works at V10.                           </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    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

  • This APAR adds the following options which affect the processing
    of schema files during deploy. These are enabled via environment
    variables which must be set to a non-null value prior to the
    start of the Integration Node / Server.
    
    <span style="background-color:rgb(221, 255,
    221);font-size:10.6667px;font-family:monospace">MQSI_XLXP_DISCAR
    D_DUPLICATE_SPECIAL_SCHEMAS</span>
    
    When set to any non-null value this causes all subsequent copies
    of the same IBM Defined schema to be ignored when generating the
    binary IR file.
    
    <span style="background-color:rgb(221, 255,
    221);font-size:10.6667px;font-family:monospace">MQSI_XLXP_OVERRI
    DE_SCHEMAS_PATH</span>
    
    When set to a fully qualified directory, or list of directories
    separated by the path separator (: on unix platforms, ; on
    windows platforms) this allows the user to specify a directory
    containing schema files that will be used in preference to all
    other schemas of the same name when resolving IBM Defined
    schemas.
    
    Additionally the environment variable <span
    style="background-color:rgb(255, 255,
    255)">MQSI_DISABLE_SCHEMA_COMPILATION now disables all binary IR
    compilation. Note that this is only suitable for use if no XML
    validation or XML based mapping is required.</span>
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.20
    v11.0      11.0.0.8
    
    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 number

    IT17577

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-19

  • Closed date

    2020-03-10

  • Last modified date

    2020-03-10

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
27 March 2020