A fix is available
APAR status
Closed as program error.
Error description
If OLM EXPLAIN option 9.4 (SQL text entered by ISPF editor) is used all table names in the SQL stmt must be qualified like "UPDATE qual.DMS_DOC_VA" or "FROM qual.HYP_DOC". If this qualifier "qual" is identical to the current SQLID (see panel DGOMYPMN Explain Menu: Current SQLID) the qualification of the table names must not be done. This behaviour was mentioned by the customer (no error when using qualified tables). Nevertheless, message FPEM760 is not correct. If a table is not found by DB2 then SQLCODE -204 should occur and displayed as message. Sample: DSNT408I SQLCODE = -204, ERROR: qual.DMS_DOC_VA IS AN UNDEFINED NAME * Explanation for msg FPEM760: The source text of the SQL stmt "UPDATE DMS_DOC_VA SET ... SELECT ... FROM HYP_DOC ..." is changed to "UPDATE DMS_DOC_VA SET ... SELECT ... FROM .HYP_DOC ..." which is a syntax errror (just a dot before the table name) and results to SQLCODE = -104 and then to msg FPEM760.
Local fix
use qualifier for all tables
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component * * - Explain * **************************************************************** * PROBLEM DESCRIPTION: EXPLAINing SQL statement text entered * * by OLM option 9.4 and having a stmt * * structure "UPDATE table1 ... SELECT ... * * FROM table2 ..." results in message * * FPEM760 (The SQL statement is not * * recognized or cannot be explained). * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: EXPLAINing SQL statement text entered by OLM option 9.4 and having a stmt structure "UPDATE table1 ... SELECT ... FROM table2 ..." results in message FPEM760 (The SQL statement is not recognized or cannot be explained). PROBLEM CONCLUSION: Code was changed to display a SQL error panel if the object table1 or table2 can not be found in the database. KEYWORDS: EXPLAIN SQLTEXT FPEM760 UNQUALIFIED-TABLE
Problem conclusion
Code was changed to display a SQL error panel if the object table1 or table2 can not be found in the database. KEYWORDS: EXPLAIN SQLTEXT FPEM760 UNQUALIFIED-TABLE
Temporary fix
Comments
APAR Information
APAR number
PK90085
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-29
Closed date
2009-06-29
Last modified date
2009-08-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK47879
Modules/Macros
DGO@YEDY DGO@YX00 DGOMYEDY DGOMYX00
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK47879
UP09/07/03 P F907
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 August 2009