z/OS MVS Programming: Sysplex Services Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Understanding Lock Contention and the Notify Exit

z/OS MVS Programming: Sysplex Services Guide
SA23-1400-00

An unconditional request for a lock that is held by another connection or by the system, causes a condition known as contention. A conditional request does not cause contention; the system simply fails the request and returns control to the calling program.

In a serialized list structure, there are only two cases where contention is created:
  • A lock is held by a connection (or by the system) and another connection issues an unconditional SET request (without LOCKCOMP) for the lock.
  • A lock is held by a connection (or by the system) and another connection issues an unconditional NOTHELD request for the lock.
Parent topic: Understanding the Serialized List Structure

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014