DFHFC0168    date time applid tranid trannum termid userid.{ An exclusive | A shared} lock on key X'keyid' in data set dsname is causing {true | false} contention but the owner of this lock is unknown.

Explanation

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

Message DFHFC0168 is issued whenever VSAM RLS is unable to determine the owner of a lock. This is an abnormal condition. It may indicate that a processor in the sysplex is stopped.

dsname is the name of the data set against which the lock is held. keyid 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.

The message identifies whether the lock is held as an exclusive lock or a 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.

A lock causes true contention if the request was for a lock against the locked key. A lock causes false contention if the request was for a lock against a different key but the lock requests clashed as a result of hashing algorithms used in creating RLS keys.

System action

Processing continues.

User response

None. The message is issued to assist in problem determination.

Module

DFHFCRS

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. tranid
  5. trannum
  6. termid
  7. userid
  8. Value chosen from the following options:
  9. X'keyid'
  10. dsname
  11. Value chosen from the following options:

Destination

CSFL



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