IBM Support

IT22312: ESQL SELECT STATEMENT LOSES REVERSE NAVIGATION DURING OPTIMIZATION

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

  • If an ESQL SELECT statement similar to the following is used
    
    SET OutputRoot.XMLNSC.Test1.result =
      (SELECT ref1.field1[>].field1 AS first,
              ref1.field1[<].field2 AS last FROM ref1);
    
    where a field reference uses the backwards navigation notation
    '<' then this is not carried through optimization.
    Then when the SELECT statement is executed, the field reference
    is evaluated from the start of the list rather than from the end
    leading to the wrong element being returned.
    
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of ESQL who perform SELECT operations.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If an ESQL SELECT statement similar to the following is used
    
    SET OutputRoot.XMLNSC.Test1.result =
      (SELECT ref1.field1[>].field1 AS first,
              ref1.field1[<].field2 AS last FROM ref1);
    
    where a field reference uses the backwards navigation notation
    '<' then this is not carried through optimization. Then when the
    SELECT statement is executed, the field reference is evaluated
    from the start of the list rather than from the end leading to
    the wrong element being returned.
    

Problem conclusion

  • The ESQL SELECT optimization code has been updated to correctly
    distinguish field references with backwards navigation notation.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.11
    v9.0       9.0.0.10
    
    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

    IT22312

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-07

  • Closed date

    2017-11-28

  • Last modified date

    2017-11-28

  • 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

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 November 2017