PI91899: DEADLOCK TIMING ISSUE WHEN TASK WAITING ON TDEPLOCK GETS PURGED

APAR status

• Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)

Error description

• CICS tasks are deadlocked.  A task waiting on the TDEPLOCK lock
  is force purged.
  
  It seems there may be a problem with the task_purged routine in
  Transient Data which runs when a task waiting on TDEPLOCK gets
  purged (FORCEPURGED).  TASK_PURGED routine tries to remove
  itself from the chain of waiters.
  However, if it just got promoted to lock owner in parallel with
  a FORCEPURGE, it won't be on the waiters list. There is nothing
  in TASK_PURGED which deals with the purged task being the new
  lock owner.  This is a very tight timing issue.
  
  
  
  Additional Symptom(s) Search Keyword(s): KIXREVRJL
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is being closed with a code of RET (returned for
  documentation).
  The Change Team have been unable to successfully recreate the
  problem scenario here so the Customer has been asked to supply
  further documentation to help clarify the circumstances which
  led to the problem occurring.
  

APAR Information

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

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

Fix information

Applicable component levels