The ANALYSIS command detects
a number of the most common problems
that result in PDSE or PDSE1 breakage. The analysis is performed for
a single system. If information for more than one system is required,
the ROUTE command should be used.
The following errors can be
detected:
- ASRBASCB Hash table latch held
- Prevents the PDSE1 address space from restarting. Also may prevent jobs from using PDSEs in a
new initiator or the shutting down of an address space.
- ASRBULCH
latch held
- Serializes recovery processing for a user address
space.
- Contention message to another system
is outstanding
- Indicates that another system is failing to
perform its required
role in the sharing of PDSEs or PDSE1s across the sysplex. Whenever
this error occurs, the most common problem source will be the system
that has not responded to the message.
- BMIBREPAIR
- Prevents certain repair functions for the I/O subsystem.
- CONTROL BLOCK BROKEN
- The system encountered
an invalid control block in running this
command.
- DIB Hash Table latch held
- Prevents
the opening and closing of a subset of the PDSEs or
PDSE1s on this system.
- DIB latch held
- Prevents the selected PDSE or PDSE1 from being opened or closed
on this system.
- DIRECTORY OR FORMAT WRITE
LOCK HELD OR WAITING
- Detects that a job has held or that a
job waited for a Directory
or Format Write lock for an excessive amount of time.
- FIBHashTableLATCH latch held
- Serializes member
processing for a single PDSE.
- FIB_LATCH
latch held
- Serializes a single member for a PDSE.
- H1LB Hash table latch held
- Prevents the opening
and closing of a subset of the PDSEs or
PDSE1s on this system.
- HL1B latch held
- Prevents locks for this data set from either being gotten or
released. It also blocks lock negotiation with other systems.
- HL1BPLCH latch held
- Prevents locks
for this data set from either being gotten or
released. It also blocks lock negotiation with other systems.
- LATCH BROKEN
- The data structures for
a latch have been overlaid.
- LATCH NULLIFIED
- The PDSE or PDSE1 code has made the latch not available. The
code usually does this when it closes the PDSE or PDSE1 for the last
time on a system. This is an unexpected situation.
- LICBASRBCHAINLATCH latch held
- Serializes PDSE
user address space tracking and recovery.
- LSDLDELT
and LSD_LATCH
- Prevents I/O to PDSE directories or members.
- LSDLTDW and LADELTDW
- Prevents connecting
or disconnection to PDSE directories or
members.
- XCM latch held
- When the
XCM latch is not released, the system is unable to
negotiate with other systems. Over time this prevents all other systems
from accessing any PDSEs or PDSE1s that this system has locked exclusive.
The latch is only acquired by tasks that run in the SMXC address space.