A fix is available
APAR status
Closed as program error.
Error description
A problem scenario can occur in query monitor whereby a normal SQL call processed in CQM's backend processor might take a wrong branch allowing a SETFRR add without a corresponding SETFRR delete (multiple FRR stack entries for CQM modules). Thus, causing an FRR stack full condition and abend07D rc00 followed by abend06D or abend05D and end of memory condition ( memterm ) abend0DC rc08 and subsequent DB2 message DSNV086E "DB2 Abnormal Termination" reason 00F30408 and DB2 fall over. ADDITIONAL SYMPTOMS INCLUDE ABENDS0C4 RC10 in CQMMSQ81 (DB2 V8.1) or CQMMSQ91 (DB2 V9.1) due to wrong AMODE when a BSM 0,15 instruction is executed. Home asid will be DSNDBM1, primary asid will be CQMMSTR, and secondary ASID will be DSNDBM1. R15 will have a valid address but since the AMODE bit is not on the high order byte of the address is ignored causing an abend0C4. Small exposure incorrout abends0c4 in query parallelism monitoring if an internal error is detected and error exit processing occurs due to lack of obtaining a work block. Other symptoms could be an ABEND0C1 if the 24 bit address is valid and contains all hex zeros. ABENDS07D followed by ABENDS0DC causes DB2 to terminate with DSNV086E -DBII DB2 ABNORMAL TERMINATION REASON=00F30408. ABENDS0C4 S0C4 ABEND0C4 0C4 ABENDS0C1 S0C1 ABEND0C1 0C1
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 Query Monitor Users * **************************************************************** * PROBLEM DESCRIPTION: A small exposure, for DB2 Query * * Monitor, to incorrout abends0c4 in * * query parallelism monitoring if an * * internal error is detectedand error * * exit processing occurs due to lack of * * obtaining a workblock. * * * * ABEND0C4 in CQMMSQ81 (DB2 V8.1) or * * CQMMSQ91 (DB2 V9.1)1Vand VD8.1) due * * to wrong AMODE when a BSM 0,15 * * instruction is executed. Home asid * * will be DSNDBM1, primary asid will be * * CQMMSTR, and secondary ASID will be * * DSNDBM1. R15 will have a valid address * * but since the AMODE bit is not on the * * high order byte of the address is * * ignored causing an abend0C4. * * * * Additional symptoms could be an * * ABEND0C1 * * if the 24 bit addressis valid and * * contains all hex zeros. * * hex zeros. * * * * ABENDS0C4 S0C4 * * ABEND0C4 0C4 ABENDS0C1 S0C1 ABEND0C1 * * 0C1 * **************************************************************** * RECOMMENDATION: * **************************************************************** APPLY PTF
Problem conclusion
APPLY PTF
Temporary fix
Comments
APAR Information
APAR number
PK98209
Reported component name
DB2 QUERY MONIT
Reported component ID
5655E6701
Reported release
230
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-10-08
Closed date
2009-11-19
Last modified date
2010-01-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK52141
Modules/Macros
CQMMAB81 CQMMAB91 CQMMCM81 CQMMCM91 CQMMESQX CQMMES81 CQMMES91 CQMMPR81 CQMMPR91 CQMMSQ81 CQMMSQ91 CQMMSSQX
Fix information
Fixed component name
DB2 QUERY MONIT
Fixed component ID
5655E6701
Applicable component levels
R230 PSY UK52141
UP09/12/03 P F912
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
08 August 2024