A fix is available
APAR status
Closed as program error.
Error description
After an ABEND ASRA in BMZR, CMAS task XNDR fails to release the BAS Association Management Map lock. Three tasks are waiting on lock. CPSM API requests had been issued: 'CREATE of a PGMINGRP resource and CREATE of a CSGLCGCG (Group-in-Group)' The CREATE for the PGMINGRP already holds the Data Repository lock for the CMAS to update the repository. The TSSJ tasks are all waiting for shared access to the Data Repository lock. As more and more TSSJ tasks build up over time, the CMAS eventually hits MXT and becomes unresponsive.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V3R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: You observe one of your CMASes at * * MAXTASK because of the number of TSSJ * * tasks suspended waiting in method XSWX * * (EYU0XSWX - Common Services External * * Wait) called from module EYU0XSLA * * (XSLA - Acquire Local Resource Lock). * * You take a console dump of the CMAS * * and find that the lock is held by a * * task which is no longer in the region. * * Examination of the CMAS job log shows * * that the task which is holding the lock * * ended several hours before, after it * * received several abends in methods run- * * ning under the task. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes must be recycled * * to pick up the new code. Note that regions * * do not need to be brought down and restarted * * at the same time. * **************************************************************** When a task abends without having established a recovery entry point, control returns to the kernel linkage method call interface module EYU9XLMC (XLMC). If the ending method was the first method in an Overflow Stack Segment Block (OSSB), the block is added to the free OSSB chain. Then the outstanding lock count in the stack header is checked to see if lock reco- very is required for the abending method. However since the OSSB containing the abending method's stack frame is no longer active, the lock count for the calling method is checked. This means that locks held by the abended method will not be freed.
Problem conclusion
Modules EYU9XLMC and EYU9XLTR (XLTR - Kernel Linkage Method Transfer) were modified to test for outstanding locks and per- form lock recovery for an ended method before checking to see if the OSSB can be added to the free OSSB chain for reuse.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM71931
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
50M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-30
Closed date
2012-09-26
Last modified date
2012-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK82142
Modules/Macros
EYU9XLMC EYU9XLTR
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R50M PSY UK82142
UP12/09/29 P F209
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":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 October 2012