A fix is available
APAR status
Closed as program error.
Error description
ABEND0C4 may occur in the common collector, the collector recovers from the abend however some audit information may be missing. This APAR addresses the following S0C4 abends: ABEND0C4-11 at offset x'B5A' in ADHMES91 at the PM45013 level. ABEND0C4-38 at offset x'4554' in ADHGUARZ at the PM45013 level. ABEND0C4-4 at offset x'2946' in ADHGUARZ at the PM45013 level. ABEND0C4-11 at offset x'2962' in ADHGUARZ at the PM45013 level. ABEND0C4-4 at offset x'B60' in ADHMES91 at the PM45013 level. ABEND0C4-38 at offset x'28CC' in ADHGUARZ at the PM45013 level. ABEND0C4-11 at offset x'2940' in ADHGUARZ at the PM45013 level. NOTE: The DB2 Query Monitor V3.1 Collector started task shares code with the InfoSphere Guardium S-TAP V8.1 Collector started task. Customers running the Collector with both DB2 Query Monitor and InfoSphere Guardium S-TAP may experience this problem in Guardium S-TAP
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 Query MOnitor. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 may occur in the common * * collector, the collector recovers from * * the abend however some audit * * information may be missing. This APAR * * addresses the following S0C4 abends: * * ABEND0C4-11 at offset x'B5A' * * in ADHMES91 at the PM45013 level. * * ABEND0C4-38 at offset x'4554' * * in ADHGUARZ at the PM45013 level. * * ABEND0C4-4 at offset x'2946' * * in ADHGUARZ at the PM45013 level. * * ABEND0C4-11 at offset x'2962' * * in ADHGUARZ at the PM45013 level. * * ABEND0C4-4 at offset x'B60' * * in ADHMES91 at the PM45013 level. * * ABEND0C4-38 at offset x'28CC' * * in ADHGUARZ at the PM45013 level. * * ABEND0C4-11 at offset x'2940' * * in ADHGUARZ at the PM45013 level. * * NOTE: The DB2 Query Monitor V3.1 * * Collector started task shares code * * with the InfoSphere Guardium S-TAP * * V8.1 Collector started task. Customers * * running the Collector with both DB2 * * Query Monitor and InfoSphere Guardium * * S-TAP may experience this problem in * * Guardium S-TAP. * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PM49554
Reported component name
DB2 QUERY MONIT
Reported component ID
5655E6701
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-10-06
Closed date
2011-10-26
Last modified date
2011-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK73263
Modules/Macros
CQMMES81 CQMMES91
Fix information
Fixed component name
DB2 QUERY MONIT
Fixed component ID
5655E6701
Applicable component levels
R310 PSY UK73263
UP11/11/02 P F111
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":"BU048","label":"IBM Software"},"Product":{"code":"SSAURY","label":"Db2 Query Monitor for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
08 August 2024