X hits on this document

910 views

0 shares

0 downloads

0 comments

208 / 236

IMS Waits

IMS Waits

Introduction

While executing in a CICS region or a batch message processing region, a thread can be blocked by contention for resources managed by IMS (rather than by MVS), such as an IMS latch. The individual execution states in this group show you when and where threads are slowed down by resources managed by IMS.

ACTL Latch

The collector found the thread waiting for the ACTL (statistics logging) latch.

IMS uses the ACTL latch to serialize access to the DC Monitor log buffers and control blocks. When the DC Monitor is active, the control region and all parallel DL/I tasks compete for this latch.

ADSC Directory Latch The collector found the thread waiting for the ADSC directory latch.

AUTH Latch

The ADSC directory latch is used to serialize access to the ADSC directory. This is a wait built on top of the dynamic control block (CBTS)latch. The ADSC directory latch is obtained in the open and close data entry database (DEDB) modules, and Fast Path command processing modules.

CBTS Latch

The collector found the thread waiting for the AUTH latch. The AUTH latch is the authorized processing latch.

DBBP Latch

The collector found the thread waiting for the CBTS latch. IMS uses the CBTS latch to serialize alterations to dynamic control block chains (IPAGES) within dynamic storage management.

The collector found the thread waiting for the DBBP latch. The DBBP latch serializes accesses to database buffers and their associated control blocks.

DEDB Area Lock

The collector found the thread waiting for the DEDB area lock.

The DEDB area lock serializes updates to a DEDB area dataset. There is a different lock for each area. The DEDB area lock is obtained in sync point processing.

208

OMEGAMON II for DBCTL Historical Component (EPILOG) Reference Manual Version 510

Document info
Document views910
Page views910
Page last viewedTue Dec 06 09:32:46 UTC 2016
Pages236
Paragraphs8116
Words69808

Comments