IRLM - Db2 activity trace
IRLM uses the z/OS® component trace (CTRACE) to trace the flow of activity between IRLM and Db2.
- SLM
- All calls to and from the system lock manager are traced.
- XCF
- All calls to and from the cross system coupling facility are traced.
- XIT
- Asynchronous interactions with the system lock manager are traced.
- DBM
- All calls to and from the DBMs are traced.
- INT
- IRLM traces member and group status events.
- EXP
- IRLM traces all exception events that occur during execution.
The XIT, EXP, and INT traces start automatically when you start the IRLM startup procedure.
The TRACE=YES parameter of the IRLM startup procedure lets you capture trace data to wraparound buffers at IRLM startup time. When you specify TRACE=YES, IRLM starts all traces.
You can use the z/OS TRACE CT command to start or stop specific traces and to specify whether the trace data wraps in the trace data sets. You cannot stop the EXP and INT traces using the TRACE CT command. This z/OS command requires that load module DXRRL183 be place in the linklib.
IRLM traces are vital in resolving many of the problems in IRLM and Db2 that are related to lock requests. You should always activate these traces in a test or development environment. It is strongly recommended that you activate these traces in a production environment. To activate IRLM traces, specify TRACE=YES in the IRLM address space (IRLMPROC) startup procedure. The traces are written to internal wrap-around buffers.
MODIFY irlmproc,SET,TRACE=nnn