IBM Support

IT25063: NO RESULTS RETURNED WHEN USING XSL KEY AND NODE-SET IN XSLT NODE

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

  • No results are returned when accessing a generated temporary
    tree using the xsl:key function in an XSL stylesheet with the
    XSLTransform node.
    The correct output is generated when the transformation is
    invoked from the IIB Toolkit.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise v11 and IBM Integration
    Bus v10 using the XSLTransform node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    No results are returned when accessing a generated temporary
    tree using the xsl:key function in an XSL stylesheet with the
    XSLTransform node. The correct output is generated when the
    transformation is invoked from the IIB Toolkit.
    
    The problem is due to the XSLTransform node using the older
    Xalan-Java XSL transformation engine rather than the newer
    transformation engine now provided with the JRE.
    
    Another problem that users might see is that while processing
    large style sheets, the XMLTransformation Node throws a
    "DTMException: No more DTM IDs are available" error. This occurs
    along with a BIP4447E message.
    
    The environment variable MQSI_XSLT_USE_JRE_PROCESSOR was
    provided in IBM Integration Bus v9 under APAR IC99957 to allow
    users to switch to use the JRE transformation engine. This
    environment is not available in IBM Integration Bus v10 because
    the JRE processor should be the default XSL transformation
    engine, however the xalan classes are still being used.
    

Problem conclusion

  • The product now uses the JRE XSL processor by default to
    transform documents within the XSLTransform node using XSL
    stylesheets.
    To use the older style xalan processor it is possible to set
    environment variable MQSI_XSLT_USE_XALAN_PROCESSOR=true.
    
    ---------------------------------------------------------------
    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

    IT25063

  • 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

    2018-05-25

  • Closed date

    2020-04-02

  • Last modified date

    2020-04-02

  • 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:
02 April 2020