When to use Locking reports

Use Locking reports when you need more information than can be supplied by the Accounting or Statistics reports and traces to resolve concurrency problems.

You can also use a Locking trace, for example, to monitor the effect of a new application introduced into a production system.

There is no correlation between the number of deadlock events shown in Locking reports and traces and the number of deadlocks shown in Accounting and Statistics reports. Accounting and Statistics reports count all deadlock occurrences regardless of how they resolve. Locking reports count only those deadlocks that were resolved by DB2. DB2 can resolve a deadlock either by making a process roll back, thereby releasing the locks it holds on resources, or by requesting a process to terminate.