IBM Support

IZ01185: TEPS GENERATES INVALID SQL, RC=350

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The TEPS will generate an invalid SQL statement under the
    following circumstances:
     - On row 1, the first column contains a substitutable parameter
    (ie. $AGENT$), and other conditions in one or more columns
     - On row 2, there are conditions in one or more columns
     - The client does not pass a value for the substitutable
    parameter
    Under these conditions, the SQL statement generated will have an
    extra closing parenthesis after the conditions specifiedon the
    first row.
    Detailed Recreation Procedure:
    - Make a copy of the "Current Managed System Status" query
    - On the first row, add these conditions:
       Name != 'AAAA'
       Product != 'AAAA'
    - On the second row, add these conditions:
       Name != 'BBBB'
    - Click OK to save the query
    - Assign the query to a table view. It will fail with RC=350
    Related Files and Output:
    Trace: ERROR (UNIT:ctdatabus INPUT ERRROR) UNIT:ctsql ALL)
    (UNIT:ctreport ALL)
    
    You will see the following message in the log prior to the SQL
    error:
    
    Performance Warning: Report subsitution value <param> not
    provided.
    
    where <param> is the substitutible parameter name for which no
    value was
    supplied by the client.
    

Local fix

  • If it is not needed, the substitutible parameter can be removed
    from the query definition to allow the query to work as desired.
    For example,for the Managed System Status query, remove the
    "$AGENT$" parameter from the Managing System column, then save
    the query.It will return rows based on all the other conditions
    specified.
    

Problem summary

  • Problem Description:
    View on a custom navigator node shows no data, displays error
    rc=350.
    
    Problem Summary:
    The TEPS will generate an invalid SQL statement under the
    following circumstances:
    
    - On row 1, the first column contains a substitutable parameter
      (ie. $AGENT$), and other conditions in one or more columns
    - On row 2, there are conditions in one or more columns
    - The client does not pass a value for the substitutable
      parameter
    
    Under these conditions, the SQL statement generated will have an
    extra closing parenthesis after the conditions specifiedon the
    first row.
    

Problem conclusion

  • Added a function to properly adjust parentheses if parameters
    are dropped from a query.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
     | interim fix | 6.1.0.6-TIV-ITM-IF0005
     | fix pack | 6.1.0-TIV-ITM-FP0007
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ01185

  • Reported component name

    TEPS

  • Reported component ID

    5724C04PS

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-09

  • Closed date

    2008-02-29

  • Last modified date

    2008-02-29

  • 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

    TEPS

  • Fixed component ID

    5724C04PS

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMQ","label":"ITM Tivoli Enterprise Portal Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 February 2008