PK56754: EEE538E EXPLAIN OF SUPPLIED SQL-STATEMENT FAILED, SQLCODE -104

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SQL statement gets the following error:
  EEE538E  EXPLAIN of supplied SQL-statement failed, SQL-code:
  -104
  DSNT408I SQLCODE = -104, ERROR:  ILLEGAL SYMBOL "<END-OF-
  STATEMENT>". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: SET
  DSNT418I SQLSTATE   = 42601 SQLSTATE RETURN CODE
  This was circumvented by indenting the second line of the
  statement by one character.
  ADDITIONAL SYMPTOMS:
  1)  Accessing SQL/PA using the TSO/ISPF interface and connecting
     to a DB2 v7 subsystem a user will experience some performance
     issues when processing the various input sources.
  2)  Customization utility was not displaying an error message
    when provided an invalid DB2 subsystem id or the DB2 subsystem
    id provided is not up and running (started).
  3)  When specifying the DB2 subsystem id as an argument to the
    SQL/PA startup clist the ISPF variable holding the DB2 exit
    library was not getting re-initialized correctly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 SQL Performance Analyzer.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: SQL statement gets the following error: *
  *                      EEE538E  EXPLAIN of supplied            *
  *                      SQL-statement failed, SQL-code: -104    *
  *                      DSNT408I SQLCODE = -104, ERROR:         *
  *                      ILLEGAL SYMBOL "<END-OF-STATEMENT>".    *
  *                      SOME SYMBOLS THAT MIGHT BE LEGAL ARE:   *
  *                      SET DSNT418I SQLSTATE   = 42601         *
  *                      SQLSTATE RETURN CODE                    *
  *                      1. Accessing SQL/PA using the TSO/ISPF  *
  *                      interface and connecting to a DB2 v7    *
  *                      subsystem a user will experience some   *
  *                      performance issues when processing the  *
  *                      various input sources.                  *
  *                      2. Customization utility was not        *
  *                      displaying an error message when        *
  *                      provided an invalid DB2 subsystem id    *
  *                      or the DB2 subsystem id provided is     *
  *                      not up and running (started).           *
  *                      3. When specifying the DB2 subsystem    *
  *                      id as an argument to the SQL/PA         *
  *                      startup clist the ISPF variable holding *
  *                      the DB2 exit library was not getting    *
  *                      re-initialized correctly.               *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

  UK33348 UK33349

Modules/Macros

• ANLCHECK ANLCIGO  ANLCV3R2 ANLHEX3  ANLMAIN
  ANLPGM31 ANLPLAN  ANLPRC3C ANLPRC3R ANLPRE3C ANLPRE3R ANLQMF31
  ANLSERV  ANLSQ2M  ANLTABS  ANLVER8
  

Fix information

• Fixed component name

  DB2 SQL PERF AN

• Fixed component ID

  5697F5701

Applicable component levels

• R310 PSY UK33348

     UP08/02/01 P F801

• R320 PSY UK33349

     UP08/02/01 P F801

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.