DFHFC0177    date time applid tranid termid userid. Transactional VSAM unit of recovery id X'urid' running in jobname/TVSInstance 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 units of recovery exist in the deadlock chain.

Message DFHFC0177 is issued once for each unit of recovery in the deadlock chain and includes the resource that unit of recovery holds and which resource it is waiting for.

The message inserts are as follows:

  • urid is the unit of recovery ID which owns a lock and is waiting for another lock.

  • jobname/TVSInstance is the job name and TVS instance in which this unit of recovery is running.

  • dsname1 is the name of the data set against which this unit of recovery 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 unit of recovery is attempting to acquire a lock.

  • key2 identifies the key which this unit of recovery is attempting to lock. If the message indicates that the unit of recovery 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 unit of recovery 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. X'urid'
  8. jobname/TVSInstance
  9. mvsid
  10. Value chosen from the following options:
  11. X'key1'
  12. dsname1
  13. Value chosen from the following options:
  14. X'key2'
  15. dsname2

Destination

CSFL



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