A fix is available
APAR status
Closed as program error.
Error description
Execution of an SQL statement is not collected or reported by Guardium appliance if the SQL statement receives a sqlcode904. Additional symptoms addressed: If CQM is started, stopped and not restarted prior to starting S-TAP or CQR, Audit and Capture events may not be collected due to a bug in the SQL collection routine that incorrectly identifies CQM as still being active. 2. ABEND04E 00E20017, Missing SQL call collection data ( ABENDS04E S04E ) NOTE: The DB2 Query Monitor Collector started task shares code with the DB2 Audit Management Expert Collector and the InfoSphere Guardium S-TAP Collector started tasks. Customers running the Collector with DB2 Query Monitor and DB2 Audit Management Expert, or InfoSphere Guardium S-TAP may experience this problem.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 Query Monitor. * **************************************************************** * PROBLEM DESCRIPTION: Execution of an SQL statement is not * * collected or reported by Guardium * * appliance if the SQL statement * * receives a sqlcode904. * * Additional symptoms addressed: * * If CQM is started, stopped and not * * restarted prior to starting S-TAP * * or CQR, Audit and Capture events may * * not be collected due to a bug in the * * SQL collection routine that incorrectly * * identifies CQM as still being active. * * NOTE: The DB2 Query Monitor Collector * * started task shares code with the DB2 * * Audit Management Expert Collector and * * the InfoSphere Guardium S-TAP Collector * * started tasks. Customers running the * * Collector with DB2 Query Monitor and * * DB2 Audit Management Expert, or * * InfoSphere Guardium S-TAP may * * experience this problem. * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PM76689
Reported component name
DB2 QUERY MONIT
Reported component ID
5655E6701
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-07
Closed date
2012-12-10
Last modified date
2013-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK90202
Modules/Macros
CQMMESA1 CQMMES81 CQMMES91
Fix information
Fixed component name
DB2 QUERY MONIT
Fixed component ID
5655E6701
Applicable component levels
R310 PSY UK90202
UP12/12/19 P F212
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.1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020