A fix is available
APAR status
Closed as program error.
Error description
Queue Manager suffers a progressive increase of WMQ storage until message CSQY222E is issued. Dumps obtained shows a high allocation in subpool 229, Key 7, with a high allocation in MTMA. GTF trace and dumps shows the cause of the problem. It occurs when browse-marks are timed-out by CSQMMTIN. It releases the MTME storage, but not the associated MTMA(s). Note that this problem will only be seen when there are more than 64 threads getting from the queue in question (in the customer's case a shared queue had 80 instances of a particular client channel that was processing the queue). . Additional Keywords: SP229 KEY7
Local fix
No local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 0 Modification 1 and Release 1 * * Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Gradual increase in storage usage when * * >64 applications use message marking * * (for example WSAS MDBs) when browsing a * * shared queue simultaneously. * * * * Over time the accumulation of storage * * in the MTMA phb can lead to performance * * degradation, and can cause a short on * * storage (SOS) condition to be detected. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a message is marked by multiple applications using message marking (MQGMO_MARK_BROWSE_HANDLE/MQGMO_MARK_BROWSE_COOP), the MTMA array embedded within the MTME for the message is updated to show which handles have marked the message. The embedded MTMA can only record the mark for 64 handles, so additional MTMA control blocks are acquired and chained to the MTME if more than 64 handles are marking messages on the queue. If a marked message is removed from a shared queue by expiry processing, or a different queue manager in the queue sharing group, CSQEMTIN detects that the MTME is no longer valid and flags it for deletion. However when CSQMMTIN processes the MTME, it only frees the MTME itself, and fails to free any additional MTMA control blocks that were chained to it.
Problem conclusion
CSQMMTIN is changed to correctly free any chained MTMA control blocks prior to freeing the MTME. 010Y 100Y CSQMMTIN
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI37696
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
010
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-03-25
Closed date
2015-06-25
Last modified date
2015-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI43317 UI28826 UI28827
Modules/Macros
CSQMMTIN
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
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":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2015