A fix is available
APAR status
Closed as program error.
Error description
This APAR address 3 issues related to the use of EXPLAIN in Db2 Admin Tool: 1) Doing an EXPLAIN from the SQ display on panel ADB21KSE defaults the schema of the PLAN_TABLE to the OWNER of the package rather than to the QUALIFIER. This may cause SQL error -204 on statements where a referenced object is not qualified: SQLCODE = -204, ERROR: >schema<.PLAN_TABLE IS AN UNDEFINED NAME 2) Doing an explain via panel ADB222 may result in a misleading 'No rows returned' message when the current schema and sqlid differ. Admin Tool successfully inserts rows into one PLAN_TABLE, but then queries a different one. 3) Because of a special customer setdup, Admin Tool may use the HLQ used to create datasets as the schema for the PLAN_TABLE, not the current SQLID. Keywords: SQLCODE204N
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: Users of the Db2 Administration Tool for * * z/OS EXPLAIN function. * **************************************************************** * PROBLEM DESCRIPTION: 1. When you run the EXPLAIN function * * from the Extracted SQL (ADB21KSE) * * panel, the default value of the schema * * is the OWNER rather than the QUALIFIER * * for the package. * * * * 2. Running the EXPLAIN function from * * the Execute SQL Statements (ADB22) * * panel when the current schema and * * SQLID are different, results in a * * misleading 'No rows returned' message. * * * * 3. When running EXPLAIN, Db2 Admin * * Tool might not honor the the z/OS * * user ID instead of the current SQLID. * **************************************************************** 1. Not using the package qualifier results in SQLCODE -204 for statements where a referenced object is not qualified. 2. When the current schema and SQLID differ, and you run the EXPLAIN function from panel ADB22, Db2 Admin Tool inserts rows into PLAN_TABLE, but then queries a different PLAN_TABLE. This behavior results in the 'No rows returned' message. 3. Using the z/OS user ID instead of the current SQLID might result in Db2 Admin Tool using an alias or different SQLID than intended, depending on the user's z/OS environment.
Problem conclusion
The problems have been resolved.
Temporary fix
Comments
APAR Information
APAR number
PH26950
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-07-01
Closed date
2020-07-31
Last modified date
2020-09-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI70855
Modules/Macros
ADB21K ADB21KS0 ADB21KSQ ADB21L ADB21M ADB21P ADB22SQL ADB2ELI
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
RC10 PSY UI70855
UP20/08/04 P F008
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":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.1.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 February 2021