A fix is available
APAR status
Closed as program error.
Error description
This issue can be caused when there are several LPARs and they all have Db2 subsystems with identical names. For example, there are 3 LPARs: L1, L2 and L3. All of these LPARs have the same Db2 subsystem defined, D1. All of these LPARs have a CQM system, a monitoring agent and D1 is monitored on L1/L2/L3. When an alert is generated for any threshold problem and getSqlText() function was specified in action to be executed, the user will get "IllegalArgumentException: Ambiguous identification information" error while getting the Static SQL text from backstore datasets. For dynamic SQL, text works correctly because dynamic text is obtained directly from Db2 catalog.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM Db2 Query Monitor for z/OS 3.3.0 * * users of component * * - CAE server * **************************************************************** * PROBLEM DESCRIPTION: The user receives "Exception retrieving * * static SQL text: java.lang. * * IllegalArgumentException: Ambiguous * * identification information." error * * while trying to get static SQL text * * via mail action. * **************************************************************** * RECOMMENDATION: Apply the PTF * **************************************************************** This issue can be caused when there are several LPARs and they all have Db2 subsystems with identical names. For example, there are 3 LPARs: L1, L2 and L3. All of these LPARs have the same Db2 subsystem defined, D1. All of these LPARs have a CQM system, a monitoring agent and D1 is monitored on L1/L2/L3. When an alert is generated for any threshold problem and getSqlText() function was specified in action to be executed, the user will get "Exception retrieving static SQL text: java.lang. IllegalArgumentException: Ambiguous identification information." error while getting the static SQL text from backstore datasets.
Problem conclusion
This APAR will fix the "Exception retrieving static SQL text: java.lang. IllegalArgumentException: Ambiguous identification information." The user will be able to see static SQL text in the action response if several Db2s with the same name but on different LPARs are monitored by CQM. Search Keywords: CAE Alerts, Action
Temporary fix
Comments
APAR Information
APAR number
PH15570
Reported component name
DB2 QUERY MONIT
Reported component ID
5655E6701
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-08-13
Closed date
2019-08-15
Last modified date
2019-09-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI64758
Modules/Macros
CQMCAEPT CQMJAR
Fix information
Fixed component name
DB2 QUERY MONIT
Fixed component ID
5655E6701
Applicable component levels
R330 PSY UI64758
UP19/08/20 P F908
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020