The DEADLOCK command prints information regarding stacks that hold locks or are waiting for a lock. The following items are analyzed:

If a stack is waiting on any of these items, the stack number is printed. In addition, any of the locks that the stack holds are listed.

All EVENTs and EVENT ARRAYs declared in the MCP outer block [D0] are considered, but hard locks (tag of 0) are not reported.

A stack is reported as waiting for a unit or path only when the stack is actually waiting, and not when the stack simply has I/O operations requested.

Syntax

             ┌◄───────────────────────┐
── DEADLOCK ─┴─/1\─┬────────────────┬─┴────────────────────────────────┤
                   ├─ CRITICAL ─────┤
                   └─<stack number>─┘

Explanation

The following text describes the meaning of each construct. Refer to “Basic Constructs” earlier in this section for information about the <number> construct.

DEADLOCK

Lists by stack number all stacks that either hold locks or are waiting for a lock, along with the names of the events or locks.

DEADLOCK CRITICAL

Lists only the stacks that hold locks and are also waiting on locks. CRITICAL deadlocks might indicate an MCP problem.

DEADLOCK <stack number>

Lists only the locks for the stack identified by the number.

Example

The following example shows the information that is printed regarding stacks that either hold locks or are waiting for locks.

INPUT: DEADLOCK


LOCK AND WAITING STACK ANALYSIS


STACK 033  WAITING FOR EVENT G 032C ANABOLEVENT
STACK 037  WAITING FOR EVENT G 0B93 NET_EVENTSW[0005]
           WAITING FOR EVENT G 0B93 NET_EVENTSW[0001]
           WAITING FOR EVENT G 09AC PSE[000F]
           WAITING FOR EVENT G 09AC PSE[000F]
STACK 038  WAITING FOR EVENT G 09AC PSE[0006]
           WAITING FOR EVENT G 09AC PSE[0005]
           WAITING FOR EVENT G 09AC PSE[0006]
           WAITING FOR EVENT G 09AC PSE[0005]
STACK 04C  WAITING FOR EVENT G 1B98 SLOGMONITOREVENT