PM71896: CMAS REACHES MAXTASKS WITH MANY TSSJ TASKS WAITING FOR THE DATA REPOSITORY LOCK.

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 V3R1M0 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 the      *
*                 restarts do not need to be done 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
PM71896
Reported component name
CPSM CICS 3.1
Reported component ID
5655M1501
Reported release
100
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:

PM71931 PM71932 UK82141

Modules/Macros

```
   EYU9XLMC EYU9XLTR
```

Fix information

Fixed component name
CPSM CICS 3.1
Fixed component ID
5655M1501

Applicable component levels

R100 PSY UK82141
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.

Document Information

Modified date:
22 February 2023

Tips

PM71896: CMAS REACHES MAXTASKS WITH MANY TSSJ TASKS WAITING FOR THE DATA REPOSITORY LOCK.

A fix is available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R100 PSY UK82141

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.

Document Information

Share your feedback

Need support?