A fix is available
APAR status
Closed as program error.
Error description
Message CQM1055E erroneously issued as a result of logic error that can occur when disable summary reporting set for a thread started before CQM was started, that is in a fetch loop. Sample error message occurs even though PK62420 is APPLYd: CQM1055E DB2 QUERY MONITOR DQMB IS EXPERIENCING STORAGE CONSTRAINTS, DATA LOSS MAY OCCUR, REASON=01000000 This APAR also corrects a -925 SQLCODE erroneously issued on a statement with an explicit commit, while the QM collector is running. Sample error message: DSNT408I SQLCODE = -925, ERROR: COMMIT NOT VALID IN IMS, CICS OR RRSAF ENVIRONMENT OTHER KEYWORDS: SQLCODE925 925 SQL925 CQM1055
Local fix
The storage constraint can be relieved by stopping the workload or restarting CQM, as described below. Workaround option A (requires stopping/restarting the looping DB2 thread): The storage constraint can be relieved by stopping the thread and restarting it after CQM has installed its monitor for that DB2. Workaround option B (requires stopping/restarting the Query Monitor Collector): An alternative workaround requires setting the monitoring profile parameter DISABLE SUMMARY REPORTING to 'N', for all workloads (for each profile line in the active profile), and restarting the Query Monitor Collector. Note that DISABLE SUMMARY REPORTING 'Y' requires INCLUDE/EXCLUDE to be set to 'E'. Example: INCLUDE/EXCLUDE E (I=Include, E=Exclude) Disable Summary Reporting Y (Y/N) Gather Host Variables N (Y/N) . .
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 Query Monitor. * **************************************************************** * PROBLEM DESCRIPTION: Message CQM1055E erroneously issued as * * a result of logic error that can occur * * when disable summary reporting set for * * a thread started before CQM was * * started, that is in a fetch loop. * * Sample error message occurs even * * though PK62420 is APPLYd: * * CQM1055E DB2 QUERY MONITOR DQMB IS * * EXPERIENCING STORAGE CONSTRAINTS, * * DATA LOSS MAY OCCUR, REASON=01000000 * * This APAR also corrects a -925 SQLCODE * * erroneously issued on a statement with * * an explicit commit, while the QM * * collector is running. * * Sample error message: * * DSNT408I SQLCODE = -925, ERROR: * * COMMIT NOT VALID IN IMS, CICS OR * * RRSAF ENVIRONMENT * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PK69639
Reported component name
DB2 QUERY MONIT
Reported component ID
5655E6701
Reported release
230
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-07-25
Closed date
2008-08-18
Last modified date
2008-09-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK39044
Modules/Macros
CQMMESQX CQMMSQ81 CQMMSQ91 CQMMSSQX
Fix information
Fixed component name
DB2 QUERY MONIT
Fixed component ID
5655E6701
Applicable component levels
R230 PSY UK39044
UP08/08/23 P F808
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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"}]
Document Information
Modified date:
31 March 2021