PM58159: RECURSIVE DS0002 ABENDS UPON PURGE OF TASK IN TSMAINLIMIT_SUSPEND.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Error Description￘
  In the design file for DFHTSMN, when a TSMAINLIMIT condition is
  found, we enter a loop at label check_tsmainlim. We stay in the
  loop while tsa_tsmain_inuse+iteml > tsa_tsmain_limit.
  .
  While in the loop, we make the call to TSSQ to suspend the task.
  After the return from the suspend, we check the TSSQ_RESPONSE
  to see if it is TSSQ_PURGED. If it is, that would break us
  out of the loop.
  .
  However, even though the task was purged, and we see the
    DSSR  EXIT  SUSPEND/PURGED
  trace entry on exit from the Dispatcher suspend, that doesn't
  get propagated back through, and we come out of TSSQ with
    TSSQ  EXIT  SUSPEND_REQUEST/OK
  Since we didn't get a TSSQ_PURGED response, we stay in
  the loop and enter the suspend again. I think this is the
  problem  -- TSSQ needs to propagate the 'purged' status back
  through so we can exit out of the loop.
  
  Additional Symptom(s) Search Keyword(s): KIXREVxxx
  

Local fix

• Local Fix￘
  APPLY THE APAR
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Recursive DS0002 abends when a task in  *
  *                      a suspend for TSMAINLIMIT is purged.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A task was suspended due to main temporary storage use reaching
  its size limit for the region. While in the TSMAINLIMIT suspend,
  a purge was issued against the task. This resulted in a
  recursive DS0002 abend, with severe error (code x'0070'), along
  with high CPU consumption. The region was eventually
  cancelled to recover from the situation.
  KEYWORDS: DFHDS0002 DFHDSSR DS 0002
  

Problem conclusion

• DFHTSSQ has been changed to ensure that the dispatcher and lock
  manager calls use separate parameter lists for their storage.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK77013

Modules/Macros

•    DFHTSSQ
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R700 PSY UK77013

     UP12/04/11 P F204

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.