DFHFC0169    date time applid termid userid. Transaction tranid with transaction number trannum encountered an RLS retained lock held on data set dsname by unit of work X'uowid' within CICS with applid applid2.

Explanation

An attempt was made to update a record which is currently held locked by a retained RLS lock.

Message inserts are as follows:

  • applid2 is the applid of the CICS system which owns the lock.

  • uowid is the identifier of the unit of work that owns the lock.

  • dsname is the name of the data set against which the lock is held.

This message is issued to aid in problem diagnosis. It identifies the owner of the lock that is causing a request to fail with a 'LOCKED' response.

System action

The application request which encountered the error receives a 'LOCKED' response.

User response

If repeated LOCKED responses are causing a problem, note the name of the CICS system and the identifier of the unit of work and attempt to find why this unit of work is holding a retained lock. There are three reasons why a unit of work can hold a retained lock.

  1. The unit of work was running in a CICS system that has failed. If this CICS system is restarted, the lock is normally released.

  2. The unit of work has gone indoubt. Indoubt failures occur as a result of a failure in communication between two CICS systems, neither of which need be the CICS system that is encountering the 'LOCKED' response.

    From a terminal connected to the CICS system with applid applid2, issue the command

    CEMT I UOW(
    uowid)

    or

    CEMT I UOWDSNFAIL

    to identify the applid of the CICS system that is coordinating the distributed unit of work. Then attempt to reestablish contact between the coordinating CICS and the system that owns the lock.

  3. The unit of work has failed backout. From a terminal connected to the CICS system with applid applid2, issue the command

    CEMT INQUIRE
    UOWDSNFAIL DATASET(
    dsname)

    to determine the reason why unit of work uowid failed backout while processing data set dsname. There are several reasons why a unit of work can fail backout, each identified by a different reason code from CEMT INQUIRE UOWDSNFAIL. See the Troubleshooting and support section for guidance on how to resolve each of these types of backout failure.

Module

DFHFCRS

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. termid
  5. userid
  6. tranid
  7. trannum
  8. dsname
  9. X'uowid'
  10. applid2

Destination

CSFL



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