A fix is available
APAR status
Closed as program error.
Error description
User reports, during workload testing, the Advanced Message Security task generates messages CSQ0215E CSQ0217E and CSQ0607E indicating that insufficient storage is available. MQ Development finds, in reviewing LE heappool trace, that a storage leak is occurring during unprotect processing, when getting from a queue protected with a confidentiality policy that does not allow key reuse, depending on the size of an internal buffer obtained/cached for the lifetime of the handle. Impact is seen in storage subpool 2 key 7. SP2 K7 . CSQ0215E CSQ0CPUT Message protection failed, return code 8, reason 04491004 . CSQ0217E CSQ0CPUT Failed to process object 'protected buffer' . CSQ0607E CSQ0DLCL Insufficient storage available
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 2 Modification 0 and * * Release 3 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Storage leak in the xxxxAMSM address * * space when getting messages from a * * queue that is protected by a * * Confidentiality policy with Key Reuse=0 * * * * Symptoms can include: * * - Message CSQ0607E reporting * * insufficient storage available. * * - Other CSQ0xxxE error messages, * * including, but not limited to CSQ0215E, * * CSQ0214E and CSQ0217E. * * - Error CEE0813S reporting insufficient * * storage to satisfy a get request in the * * xxxxAMSM SYSOUT DD. * * - MQI calls failing with various MQRC * * errors including: * * MQRC_SECURITY_ERROR (MQRC 2063), * * MQRC_STORAGE_NOT_AVAILABLE (MQRC 2071), * * or MQRC_CONNECTION_NOT_AUTHORIZED * * (MQRC 2217). * **************************************************************** When getting a protected message from a queue with a Confidentiality policy with Key Reuse=0, an area of storage is obtained for caching information about the message but is not subsequently used due to the Key Reuse value of 0. When the queue is subsequently closed, this area of storage is not always freed correctly, and can be leaked. Over time an accumulation of these areas can lead to storage exhaustion (SOS) in the xxxxAMSM address space, and prevent further MQI calls succeeding.
Problem conclusion
The leaked area of storage is no longer obtained when getting from a queue where the policy specifies Key Reuse=0;
Temporary fix
Comments
APAR Information
APAR number
PH49928
Reported component name
IBM MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-09-30
Closed date
2022-11-09
Last modified date
2022-12-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI83192 UI83193
Modules/Macros
CSQ0DUNP
Fix information
Fixed component name
IBM MQ Z/OS V9
Fixed component ID
5655MQ900
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"200","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 December 2022