DFHFC7130 date time applid tranid trannum termid userid. Unit of work X'uowid' running in region owner-applid in MVS system MVSid holds a lock on key X'keyid' in coupling facility data table tablename in pool CFDTpool, which caused this request to wait.

Explanation

This message is issued to aid problem determination when a transaction that has accessed, or attempted to access, a coupling facility data table is about to terminate abnormally with an AFCY abend code.

The message is issued when a request to a coupling facility data table times out waiting on a lock. A request that requires a lock on a coupling facility data table has been issued, but was forced to wait because the record was locked by another unit of work. The wait has been purged by one of the following actions:

  • The timeout time for the transaction has been exceeded.

  • CICS has purged transactions in an attempt to alleviate a short-on-storage (SOS) condition.

  • The transaction has been purged by an operator request.

The name of the transaction that has failed is tranid and it is running under task number trannum, at terminal termid, for user userid.

The message inserts identify the owner of the lock that caused this transaction to timeout:

  • uowid is the local UOW id of the unit of work running in the region that owns the lock.

  • owner-applid is the applid of the region that owns the lock.

  • MVSid is the name of the MVS system in which the region that owns the lock is running.

  • keyid identifies the key that is locked. As it is not always possible to display keys in character form, the key is displayed in hexadecimal notation.

  • tablename is the name of the coupling facility data table against which the lock is held.

  • CFDTpool is the name of the coupling facility data table pool in which the CF data table tablename resides.

The locks held against coupling facility data tables are always exclusive locks, and can only have one holder. Therefore, this message uniquely identifies the owner of the required lock.

System action

The transaction is abended with an AFCY abend code.

User response

This message identifies the unit of work that is holding the required lock and the region in which it is running. Examine this unit of work to see why it is not releasing the lock; for example:

  • The unit of work may be holding CF data table locks and waiting for terminal input.

  • The unit of work may be trying to access both coupling facility data table resources and resources owned by another resource manager, creating an inter-resource manager deadlock.

Module

DFHFCDR

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. tranid
  5. trannum
  6. termid
  7. userid
  8. X'uowid'
  9. owner-applid
  10. MVSid
  11. X'keyid'
  12. tablename
  13. CFDTpool

Destination

CSFL