DFHFC0167    date time applid tranid termid userid. Transaction transid(tasknum) with unit of work id X'uowid' running in jobname/applid2 in MVS mvsid holds {add to end lock | internal lock | exclusive lock on key | shared lock on key } X'key1' on data set dsname1 and is waiting for {add to end lock | internal lock | exclusive lock on key | shared lock on key } X'key2' on data set dsname2.

Explanation

This message and the preceding DFHFC0166 message are issued to assist in problem determination when transactions abend with AFCW abend codes.

The preceding message DFHFC0166 reports that a deadlock has been detected and includes how many transactions exist in the deadlock chain.

Message DFHFC0167 is issued once for each transaction in the deadlock chain and includes the resource that transaction holds and which resource it is waiting for.

The message inserts are as follows:

  • transid(tasknum) is the transaction name and the associated task number of a transaction that owns a lock and is waiting for another lock. If this participant in the deadlock chain is not a CICS system, this will appear as ????(?????).

  • uowid is the unit of work ID associated with task transid(tasknum). The unit of work is also used by VSAM as the logical unit of work ID (luwid).

  • jobname/applid2 is the job name and applid of the CICS system in which this transaction is running.

  • mvsid is the name of the MVS in which this CICS job is running.

  • dsname1 is the name of the data set against which this transaction holds a lock.

  • key1 identifies the key which is locked. As it is not always possible to display keys in character form, the key is displayed in hexadecimal notation. If the message indicates that an add to end lock or an internal lock is held then no key information is displayed.

  • dsname2 is the name of the data set against which this transaction is attempting to acquire a lock.

  • key2 identifies the key which this transaction is attempting to lock. If the message indicates that the transaction is attempting to obtain an add to end lock or an internal lock then no key information is displayed.

The message identifies whether the lock is held as an exclusive lock or a shared lock and whether the transaction is attempting to acquire an exclusive or shared lock.

  • A lock is exclusive if it can only have one holder. For example, exclusive locks are used to protect update operations.

  • A lock is shared if it can have many holders. Shared locks are used to protect repeatable and consistent read operations.

System action

The application request which encountered the error receives an AFCW abend.

User response

See the description of message DFHFC0166.

Module

DFHFCRS

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. tranid
  5. termid
  6. userid
  7. transid(tasknum)
  8. X'uowid'
  9. jobname/applid2
  10. mvsid
  11. Value chosen from the following options:
  12. X'key1'
  13. dsname1
  14. Value chosen from the following options:
  15. X'key2'
  16. dsname2

Destination

CSFL



DFHFC0167.html | Timestamp icon Last updated: Sunday, 4 June 2017