0% found this document useful (0 votes)
122 views5 pages

What To Look For in A OMEGAMON Statistics Report - IBM Documentation

The document discusses fields in an OMEGAMON statistics report related to group buffer pool activity on IBM z/OS systems. It explains key fields such as the number of page reads from the group buffer pool due to cross-invalidation or the pool being non-full, as well as counts of page casts, writes, and locks.

Uploaded by

amir ghorbani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
122 views5 pages

What To Look For in A OMEGAMON Statistics Report - IBM Documentation

The document discusses fields in an OMEGAMON statistics report related to group buffer pool activity on IBM z/OS systems. It explains key fields such as the number of page reads from the group buffer pool due to cross-invalidation or the pool being non-full, as well as counts of page casts, writes, and locks.

Uploaded by

amir ghorbani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

5/1/23, 12:31 AM What to look for in a OMEGAMON statistics report - IBM Documentation

What to look for in a OMEGAMON


statistics report
Last Updated: 2021-12-29

You can use Tivoli® OMEGAMON® XE for Db2 Performance Expert on z/OS® statistics reports to
understand group buffer pool activity.

Refer to the Tivoli OMEGAMON XE for Db2 Performance Expert on z/OS statistics detail report shown in
the following figure. The fields from that report are used to explain some of the activity that takes place
for cross-invalidation and refresh of buffers. Some of the information is the same as that described by the
DISPLAY GROUPBUFFERPOOL output, which was covered earlier in this section.

Figure 1. Portion of Tivoli OMEGAMON XE for Db2 Performance Expert on z/OS statistics detail report
showing GBP activity

GROUP BP30 QUANTITY /SECOND /THREAD /COMMIT


----------------------------- -------- ------- ------- -------
GROUP BP R/W RATIO (%) 27.26 N/A N/A N/A
GBP-DEPENDENT GETPAGES 651.4M 45.4K 233.60 102.02
SYN.READ(XI)-DATA RETURNED A 1091.6K 76.12 0.39 0.17
SYN.READ(XI)-NO DATA RETURN B 133.0K 9.28 0.05 0.02
SYN.READ(NF)-DATA RETURNED C 1062.1K 74.07 0.38 0.17
SYN.READ(NF)-NO DATA RETURN 14515.1K 1012.21 5.21 2.27
UNREGISTER PAGE D 4323.7K 301.52 1.55 0.68

CLEAN PAGES SYNC.WRITTEN 0.00 0.00 0.00 0.00


CLEAN PAGES ASYNC.WRTN 0.00 0.00 0.00 0.00
REG.PAGE LIST (RPL) REQUEST 4025.4K 280.71 1.44 0.63
NUMBER OF PAGES RETR.FROM GBP 750.0K 52.30 0.27 0.12
PAGES CASTOUT E 3033.5K 211.54 1.09 0.48
UNLOCK CASTOUT F 115.7K 8.07 0.04 0.02

READ CASTOUT CLASS G 105.4K 7.35 0.04 0.02


READ DIRECTORY INFO H 69375.00 4.84 0.02 0.01
READ STORAGE STATISTICS I 9237.00 0.64 0.00 0.00
REGISTER PAGE J 307.2K 21.43 0.11 0.05
DELETE NAME K 24191.00 1.69 0.01 0.00
ASYNCH GBP REQUESTS L 7532.5K 525.28 2.70 1.18

EXPLICIT X-INVALIDATIONS M 0.00 0.00 0.00 0.00


CASTOUT CLASS THRESHOLD N 78.00 0.01 0.00 0.00
GROUP BP CASTOUT THRESHOLD O 24.00 0.00 0.00 0.00
GBP CHECKPOINTS TRIGGERED P 100.00 0.01 0.00 0.00
WRITE FAILED-NO STORAGE Q 0.00 0.00 0.00 0.00

WRITE TO SEC-GBP FAILED 0.00 0.00 0.00 0.00


DELETE NAME LIST SEC-GBP 115.6K 8.06 0.04 0.02
DELETE NAME FROM SEC-GBP 5718.00 0.40 0.00 0.00
UNLOCK CASTOUT STATS SEC-GBP R 0.00 0.00 0.00 0.00
ASYNCH SEC-GBP REQUESTS 599.00 0.04 0.00 0.00

https://www.ibm.com/docs/en/db2-for-zos/11?topic=pools-what-look-in-omegamon-statistics-report 1/5
5/1/23, 12:31 AM What to look for in a OMEGAMON statistics report - IBM Documentation
WRITE AND REGISTER 4220.8K 294.34 1.51 0.66
WRITE AND REGISTER MULT 1350.3K 94.17 0.48 0.21
CHANGED PGS SYNC.WRTN S 7901.0K 550.98 2.83 1.24
CHANGED PGS ASYNC.WRTN T 2752.1K 191.92 0.99 0.43
PAGES WRITE & REG MULT 6432.4K 448.57 2.31 1.01
READ FOR CASTOUT 29352.00 2.05 0.01 0.00
READ FOR CASTOUT MULT 407.8K 28.44 0.15 0.06

PAGE P-LOCK LOCK REQ 2604.3K 181.61 0.93 0.41


SPACE MAP PAGES 844.2K 58.87 0.30 0.13
DATA PAGES 1760.1K 122.74 0.63 0.28
INDEX LEAF PAGES 0.00 0.00 0.00 0.00

PAGE P-LOCK UNLOCK REQ 2478.9K 172.87 0.89 0.39

PAGE P-LOCK LOCK SUSP 98270.00 6.85 0.04 0.02


SPACE MAP PAGES 48419.00 3.38 0.02 0.01
DATA PAGES 49851.00 3.48 0.02 0.01
INDEX LEAF PAGES 0.00 0.00 0.00 0.00

PAGE P-LOCK LOCK NEG 63760.00 4.45 0.02 0.01


SPACE MAP PAGES U 45651.00 3.18 0.02 0.01
DATA PAGES V 18109.00 1.26 0.01 0.00
INDEX LEAF PAGES W 0.00 0.00 0.00 0.00

Explanation of fields
A
The number of requests made to read a page from the group buffer pool because the page was
invalidated in the member's buffer pool. The member found the required page in the group buffer
pool.
B
The number of requests to read a page from the group buffer pool that were required because the
page was invalidated in the member's buffer pool. The member did not find the data in the group
buffer pool and had to retrieve the page from DASD. If this number is high, use the following formula
to calculate the percentage: B /( A + B ). If the result is greater than 10%, consider increasing the
size of the group buffer pool.
C
The number of requests made to read a page from the group buffer pool because the page was not
in the member's buffer pool. The member found the page in the group buffer pool.
D
The number of times Db2 unregistered interest for a single page. This happens when Db2 steals
pages from the member's buffer pool that belong to GBP-dependent page sets or partitions.
E
The number of data pages that were cast out of the member's group buffer pool. Castout to a page
set or partition is done by the castout owner of the page set or partition. This is normally the Db2

https://www.ibm.com/docs/en/db2-for-zos/11?topic=pools-what-look-in-omegamon-statistics-report 2/5
5/1/23, 12:31 AM What to look for in a OMEGAMON statistics report - IBM Documentation

subsystem that had the first update intent on the page set or partition.
F
The number of times Db2 issued an unlock request to the coupling facility for completed castout
I/Os. When pages are cast out to DASD, they are locked for castout in the coupling facility. This
castout lock is not an IRLM lock; its function is to ensure that only one system can cast out a given
page at a time.
G
The number of requests issued by the group buffer pool to determine which pages, from a particular
page set or partition, must be cast out because they are cached as changed pages. This request is
issued either by the page set or partition castout owner, or, when the group buffer pool castout
threshold is reached by the group buffer pool structure owner.
H
The number of requests issued by the group buffer pool structure owner to read the directory
entries of all changed pages in the group buffer pool. This request is issued at group buffer pool
checkpoints to record the oldest recovery log record sequence number (LRSN). It is used as a basis
for recovery if the group buffer pool fails. Such requests might have to be issued several times for
each group buffer pool checkpoint to read the directory entries for all changed pages.
I
The number of times Db2 requested statistics information from the group buffer pool. It is issued by
the group buffer pool structure owner at timed intervals to determine whether the group buffer pool
castout threshold (GBPOOLT) has been reached.
J
The number of times Db2 registered interest in a single page. These are "register-only" requests,
which means that Db2 is not requesting any data back from the request. This request is made only
to create a directory entry for the page to be used for cross-invalidation when the page set or
partition P-Lock is downgraded from S to IS mode, or from SIX to IX mode.
K
The number of requests made by Db2 to delete directory and data entries associated with a
particular page set or partition from the group buffer pool. Db2 issues this request when it changes
a page set or partition from GBP-dependent to non GBP-dependent. Db2 also issues this request for
objects that are defined with GBPCACHE ALL when those objects are first opened.
L
The number of IXLCACHE invocations for the primary group buffer pool.
M
The number of times an explicit coupling facility cross-invalidation request was issued.
N
The number of times group buffer pool castout was initiated because the group buffer pool class
castout threshold was detected.

https://www.ibm.com/docs/en/db2-for-zos/11?topic=pools-what-look-in-omegamon-statistics-report 3/5
5/1/23, 12:31 AM What to look for in a OMEGAMON statistics report - IBM Documentation

O
The number of times a group buffer pool castout was initiated because the group buffer pool
castout threshold was detected.
P
The number of group buffer pool checkpoints triggered by this member.
Q
The number of coupling facility write requests that could not complete due to a lack of coupling
facility storage resources.A high number indicates a shortage of group buffer pool data elements
because the size of the group buffer pool is too small, or because castout is not keeping up with the
rate that changed pages are written. If the pages were not written to LPL, then the write retry
attempt was successful.
R
The number of coupling facility requests to read the castout statistics for the secondary group
buffer pool. These requests are issued by the group buffer pool structure owner to check for
orphaned data entries in the secondary group buffer pool.
S
The number of changed pages written synchronously to the group buffer pool. Pages are written
with Write and Register (WAR) requests or Write and Register Multiple (WARM) requests. At commit
time changed pages are forced from the member's virtual buffer pool to the coupling facility.
T
The number of changed pages written asynchronously to the group buffer pool. Pages are written in
response to Write and Register (WAR) and Write and Register Multiple (WARM) requests. Changed
pages can be written from the member's virtual buffer pool to the group coupling facility before the
application commits. This happens when, for example, a local buffer pool threshold is reached, or
when P-Lock negotiation forces the pages on the vertical deferred write queue to be written to the
group buffer pool.
U
The number of P-lock negotiations between data sharing members for space map pages. If this
number is high, identify the objects by using IFCID 0259 performance trace. If the high number is
caused by insert-intensive applications, consider using the MEMBER CLUSTER or TRACKMOD NO
options, or both.
V
The number of P-lock negotiations between data sharing members for data pages. If this number is
high, identify the objects by using IFCID 0259 performance trace. The typical cause is tables spaces
that use row-level locking. For small tables, consider using MAXROWS=1, and VDWQT=0 to free
page P-locks as soon as possible.
W

https://www.ibm.com/docs/en/db2-for-zos/11?topic=pools-what-look-in-omegamon-statistics-report 4/5
5/1/23, 12:31 AM What to look for in a OMEGAMON statistics report - IBM Documentation

The number of p-lock negotiations between members for index leaf pages. If this number is high,
identify the objects by using IFCID 0259 performance trace. The typical cause is applications that
do ascending or descending updates of index keys. Creating indexes with randomized keys might
help this situation. However, doing so might incur other performance degradation because more
get-page operations, I/O, and lock requests are needed.

Parent topic:
Determining the correct size and ratio of group buffer pools

https://www.ibm.com/docs/en/db2-for-zos/11?topic=pools-what-look-in-omegamon-statistics-report 5/5

You might also like