Example of a member-scope Locking report
Locking reports are helpful in monitoring the locking of page sets.
If you want to monitor deadlocks and timeouts on shared databases, and if you want this information grouped by individual members, generate a Lockout report for every member. Because group-scope reports are available in the Locking report set, this report is called a member-scope report.
Member-scope reports also provide group-scope information because holders and waiters of lockups are shown. Member scope and group scope only influence the summarization of the report.
To generate a member-scope Locking report, specify the following command stream:
⋮
LOCKING
REPORT
LEVEL (LOCKOUT)
ORDER(DATABASE-PAGESET)
⋮
Member-scope report is the default, so you are not required to specify the SCOPE subcommand option. To order the report by page set within a database, specify the ORDER subcommand option.
The following example shows a member-scope Locking report for group DSHGRPXX, which has two members, FIRST and SECOND. The report is two pages long because a new page is started when the member that is being reported changes.
Member-scope Locking Lockout report, page 1
The first page of the report shows the locking activity of the threads that have executed in member FIRST.
LOCATION: SYDNEY OMEGAMON XE for DB2 Performance Expert (V5R4M0) PAGE: 1-1
GROUP: DSHGRPXX REQUESTED FROM: NOT SPECIFIED
MEMBER: FIRST LOCKING REPORT - LOCKOUT TO: NOT SPECIFIED
SUBSYSTEM: DB22 ORDER: DATABASE-PAGESET ACTUAL FROM: 05/15/15 12:15:00.21
DB2 VERSION: V10 SCOPE: MEMBER TO: 05/15/15 13:27:56.09
DATABASE --- L O C K R E S O U R C E --- --------------- A G E N T S ---------------- BLOCKER/
PAGESET TYPE NAME TIMEOUTS DEADLOCKS MEMBER PLANNAME CONNECT CORRNAME CORRNMBR HOLDER WAITER
------------------ --------- ----------------------- -------- --------- -------- -------- -------- -------- -------- ------ ------
DBASE9 ROW PAGE=X'000021' 0 3 FIRST D3APP01 BATCH RUNPR01 'BLANK' 2 1
TSPACEXX ROW =X'03' SECOND D3APPBB BATCH RUNPRBB 'BLANK' 1 1
SECOND D3APPDD BATCH RUNPRDD 'BLANK' 0 2
INDEXPAGE PAGE=X'002393' 0 1 FIRST D3APP02 BATCH RUNPR02 'BLANK' 0 1
SUBP=X'01'
** LOCKOUTS FOR TSPACEXX ** 0 4
** TOTAL - DBASE9 ** 0 4
DBASE10
TSPACEZZ DATAPAGE PAGE=X'000055' 0 3 FIRST D3APP03 BATCH RUNPR03 'BLANK' 2 1
FIRST D3APP05 BATCH RUNPR05 'BLANK' 0 3
** LOCKOUTS FOR TSPACEZZ ** 0 3
** GRAND TOTAL ** 0 7
Member-scope Locking Lockout report, page 2
The second page of the report shows the locking activity of the threads that have executed in member SECOND.
LOCATION: SYDNEY OMEGAMON XE for DB2 Performance Expert (V5R4M0) PAGE: 2-1
GROUP: DSHGRPXX REQUESTED FROM: NOT SPECIFIED
MEMBER: SECOND LOCKING REPORT - LOCKOUT TO: NOT SPECIFIED
SUBSYSTEM: DB22 ORDER: DATABASE-PAGESET ACTUAL FROM: 05/15/15 12:15:00.21
DB2 VERSION: V10 SCOPE: MEMBER TO: 05/15/15 13:27:56.09
DATABASE --- L O C K R E S O U R C E --- --------------- A G E N T S ----------------
PAGESET TYPE NAME TIMEOUTS DEADLOCKS MEMBER PLANNAME CONNECT CORRNAME CORRNMBR HOLDER WAITER
------------------ --------- ----------------------- -------- --------- -------- -------- -------- -------- -------- ------ ------
DBASE9 ROW PAGE=X'000021' 0 4 FIRST D3APP01 BATCH RUNPR01 'BLANK' 2 1
TSPACEXX ROW =X'03' FIRST D3APP02 BATCH RUNPR02 'BLANK' 1 1
SECOND D3APPAA BATCH RUNPRAA 'BLANK' 0 2
SECOND D3APPBB BATCH RUNPRBB 'BLANK' 1 1
** LOCKOUTS FOR TSPACEZZ ** 0 4
DBASE10 ROW PAGE=X'000021' 0 4 FIRST D3APP01 BATCH RUNPR01 'BLANK' 1 0
TSPACEZZ ROW =X'03' FIRST D3APP02 BATCH RUNPR02 'BLANK' 0 1
SECOND D3APPCC BATCH RUNPRCC 'BLANK' 2 1
SECOND D3APPEE BATCH RUNPREE 'BLANK' 0 2
INDEXPAGE PAGE=X'000033' 0 5 SECOND D3APPBB BATCH RUNPRBB 'BLANK' 1 1
SUBP=X'03' SECOND D3APPCC BATCH RUNPRCC 'BLANK' 1 0
SECOND D3APPDD BATCH RUNPRDD 'BLANK' 0 2
** LOCKOUTS FOR TSPACEZZ ** 0 5
** GRAND TOTAL ** 0 9