DFHFC0175    date time applid tranid trannum termid userid. Transactional VSAM unit of recovery X'urid' running in job jobname on Transactional VSAM instance TVSInstance in MVS mvsid holds {add to end lock | internal lock | exclusive lock on key | shared lock on key } X'keyid' in data set dsname causing {true | false} contention.

Explanation

This message and the preceding message DFHFC0164 or DFHFC0174 are issued to assist in problem determination when transactions abend with the AFCV or AFCW abend codes, or when applications receive the RECORDBUSY condition.

Normally this message appears after VSAM returns a timeout response to CICS. However, it may also appear after VSAM returns a deadlock response to CICS when that deadlock arises as a result of a failure to promote a lock. When this message is associated with a timeout response from VSAM, it is preceded by message DFHFC0164. When this message is associated with a deadlock response from VSAM it is associated with message DFHFC0174.

There is one occurrence of message DFHFC0175 for each unit of recovery currently owning the required lock.

The name of the transaction that has failed is tranid and it has task number trannum.

The message inserts that identify the owner of the lock which caused this transaction to time out are as follows:

  • urid is the unit of recovery id running in the Transactional VSAM instance which owns the lock.

  • jobname is the job name of the CICS system that owns the lock.

  • TVSInstance is the name of the Transactional VSAM instance whose job name was given by the previous insert.

  • mvsid is the name of the MVS in which this Transactional VSAM instance is running.

  • 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. If the message indicates that the transaction is waiting for an add to end lock or an internal lock, no key information is displayed.

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 because of the RLS key hashing algorithm which is used when the key length exceeds 16 characters.

System action

This message is preceded by DFHFC0164 or DFHFC0174. See the description of DFHFC0164 or DFHFC0174 for a description of the system action associated with this message.

User response

This message is preceded by DFHFC0164 or DFHFC0174. See the description of DFHFC0164 or DFHFC0174 for a description of the user actions associated with this message.

Module

DFHFCRS

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. tranid
  5. trannum
  6. termid
  7. userid
  8. X'urid'
  9. jobname
  10. TVSInstance
  11. mvsid
  12. Value chosen from the following options:
  13. X'keyid'
  14. dsname
  15. Value chosen from the following options:

Destination

CSFL



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