APAR status
Closed as program error.
Error description
When the disk space is full or the MQ log file becomes full, MQ queue manager may fail to update the channel scratchpad file with the following error: ****** AMQ9588: Program cannot update queue manager object. EXPLANATION: The attempt to update object 'x' on queue manager '<qmgr name>' failed with reason code 2195. ****** Then, the corresponding channel cannot be started unless it is recreated. In addition to the above, MQ First Failure Symptom Report (FDC) files will be produced with the following characteristics: Probe Id :- AQ122001 Component :- aqqRecoverQueue Major Errorcode :- STOP MQM Function Stack zlaMainThread zlaProcessMessage zlaProcessSPIRequest zlaSPIQueryScratchPad zsqSPIQueryScratchPad kpiSPIQueryScratchPad apiQueryScratchPad aqmQueryScratchPad aqsStartQOp aqsRecoverQOp aqhRecoverQueue aqqRecoverQueue xcsFFST Alternatively, if the scenario that preceded this problem was the MQ log becoming full, then additional FDC's may be produced with the following characteristics: Probe Id :- HL010004 Application Name :- MQM Component :- hlgReserveLogSpace Program Name :- amqzlaa0 Major Errorcode :- hrcE_LOG_FULL Probe Id :- HL006009 Application Name :- MQM Component :- hlgWriteLogRecord Program Name :- amqzlaa0 Major Errorcode :- hrcE_LOG_FULL and the following errors will appear in the MQ error logs: 	AMQ6709: The log for the queue manager is full. 	AMQ9999: Channel '<CHNAME>' to host '<HOSTNAME> (<IPADDRESS>)' ended abnormally. 	AMQ9589: Program cannot query queue manager object.
Local fix
Delete and recreate the channel.
Problem summary
**************************************************************** USERS AFFECTED: Users of IBM MQ that experience low disk resources or a log full condition Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: After the file system full or log full condition which caused the channel to end abnormally, an internal state was not checked correctly during the recovery process. This meant that the transaction details were not associated and the scratchpad file was not recovered correctly.
Problem conclusion
This programming error has been resolved to ensure the queue recovery process may complete. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.9 v9.0 CD 9.0.5 v9.0 LTS 9.0.0.4 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT23552
Reported component name
IBM MQ BASE M/P
Reported component ID
5724H7261
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-21
Closed date
2018-01-31
Last modified date
2021-06-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
IBM MQ BASE M/P
Fixed component ID
5724H7261
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]
Document Information
Modified date:
16 June 2021