X hits on this document

1374 views

0 shares

0 downloads

0 comments

209 / 236

IMS Waits

A DEDB area lock is always taken before the DMAC latch to avoid the possibility of a deadlock.

DEDB Segment

The collector found the thread waiting to obtain control of a resource in a data entry database (DEDB). The resource under control is a unit of work (UOW), and it is represented by an XCRB control block.

DMAC Latch

The collector found the thread waiting for the DMAC latch.

The DMAC latch is used to serialize updates to DEDB area datasets. Sync point processing modules require the DMAC latch. Updates are recorded in the log records. The physical update of the DEDB area does not take place until the updates are written to the IMS log.

DMAC Share Latch

The collector found the thread waiting for the DMAC share latch.

The DMAC share latch is used to serialize access to DMAC control blocks. Open and close area dataset processing modules require the DMAC share latch in exclusive mode.

DMBE Latch

The collector found the thread waiting for the DMBE latch. The DMBE latch is used to serialize the dynamic insertion and removal of control blocks associated with databases (DMBs).

Fast Path Buffer

The collector found the thread waiting for a Fast Path buffer. Buffer allocation for an IMS Fast Path Region (IFP) is under the maximum number of allowable buffers specified by the normal buffer allocation (NBA) execution parameter.

Fast Path IWAIT in Term

The collector found the Fast Path application program processing the thread IWAITing while the application program was terminating.

Fast Path Other Abend

The collector found the Fast Path application program processing the thread IWAITing and that the application program was terminating due to an abend.

Bottleneck Analysis Execution States

209

Document info
Document views1374
Page views1374
Page last viewedWed Jan 18 21:05:12 UTC 2017
Pages236
Paragraphs8116
Words69808

Comments