The LOCKS command analyzes all events, event arrays, and interlocks that are declared in the MCP output block, and lists the abnormal ones. Hard locks are not reported. An abnormal event is one that is procured or has a stack waiting on it. not reported.
Syntax
── LOCKS ──────────────────────────────────────────────────────────────┤
| Note: | You can locate the MCP global events and event arrays by using BINDINFO data in the MCP code file. If the analyzed code file does not match the dumping MCP code file, the event analysis might be incorrect. |
Example
The following example shows output for the LOCKS command.
INPUT: LOCKS
MCP EVENTS (PROCURED OR WITH WAITERS)
G F82 2 000000 000330 2 000000 000000 PSTAT_ERRQ_EVENT
(WAITING: STK 033)
G 92D 2 000000 100310 2 000000 000000 WORKERQ_INSERT
(WAITING: STK 031)
G 712 2 000000 2002C0 2 000000 000000 ALE[0004]
(WAITING: STK 02C)
G 192 2 000000 1004C0 2 000000 000000 OLAYSPACEWANTED
(WAITING: STK 04C)
G 342 2 000000 000300 2 000000 000000 ANABOLEVENT
(WAITING: STK 030)
G C6E 2 000000 4002E0 2 000000 000000 NET_EVENTSW[0002]
(WAITING: STK 02E)
2 000000 000550 2 000000 000000 NET_EVENTSW[0004]
(WAITING: STK 055)
2 000000 1007E0 2 000000 000000 NET_EVENTSW[0006]
(WAITING: STK 07E)
2 000000 5002E0 2 000000 000000 NET_EVENTSW[000A]
(WAITING: STK 02E)