Measure Reference Manual

Usage Notes for H-Series and J-Series CPU Entities
• In H-series, J-series, and later RVUs, all byte count fields are 64-bit counters. The suffix -F no
longer appears in counter names in ZMS format; however, counters with names ending in -F
remain available to applications requesting data in legacy style format.
• In Measure H06/J04 and later PVUs, ZMS style CPU and ZMS style PROCESS support the
LOCKED-PAGES-END and LOCKED-PAGES-START counters. Note the following usage
considerations when using these counters:
◦ The sum of page frames reported as locked in all PROCESS entities for a CPU does not
need to equal the page frames reported as locked in the corresponding CPU entity.
◦ A page frame is locked when it is made present in memory and marked to keep it present.
It becomes unlocked when all such marks are removed, or when the page frame is
de-allocated.
◦ A locked page frame is initially associated with (sponsored by) the process that locked
it. If the page is shared among multiple processes, and the original process terminates,
the page becomes unsponsored; at a later time it becomes sponsored by one of the
remaining processes sharing the page. If the page frame is mapped in global address
space and not in the unique address space of any process, the page becomes sponsored
by the memory manager process, PIN 1, which also sponsors pages allocated by and
for the system.
◦ An unsponsored locked page frame remains unsponsored (associated with no process)
until the next routine visit by the Memory Manager process.
• The initial record of the CPU entity is created at CPU load time and not at the measurement
start time. During active retrieval the current counter values are shown taking in consideration
the delta time between the initial record and the current record. The counters ACCEL-BUSY-TIME,
NATIVE-BUSY-TIME, and TNS-BUSY-TIME are calculated, returned, and displayed only if a
PROCESSH measurement has been active in the CPU during the delta time period. Otherwise,
the counters are not displayed, and their values in the returned record are zero. If the
PROCESSH measurement has not been active during this entire time period (which is not likely
for the CPU entity), the counter values will not be correct.
The counters are calculated based on the number of PROCESSH samples observed in the
applicable code region, and so for more accurate numbers, you can increase the frequency
of PROCESSH samples. The PROCESSH-SAMPLES counter reports the current sampling
frequency.
Effective with Measure H04/J02, and later PVUs, if the PROCESSH sample count is unchanged
from the start to the end of a measurement interval, the ACCEL-BUSY-TIME, NATIVE-BUSY-TIME,
and TNS-BUSY-TIME fields will not be displayed by MEASCOM even if a PROCESSH
measurement is active. For the LISTALL command, this means some intervals might display
those fields and others might not.
The MEASCOM command LISTACTIVE FOR time will give correct values for the counters
ACCEL-BUSY-TIME, NATIVE-BUSY-TIME, and TNS-BUSY-TIME only if a PROCESSH measurement
was running during the entire time period in question.
Usage Notes for G-Series CPU Entities
• The 64-bit byte-count fields (fields ending in -F) collect the same data as older 32-bit byte-count
fields. For example, the 64-bit field DISC-IOS-F collects the same data as the 32-bit field
DISC-IOS. The 64-bit fields are less subject to overflow caused by high levels of I/O activity.
The 32-bit fields are currently active and continue to return values. If there is no field overflow,
the 32-bit fields and the 64-bit fields return the same value. If a 32-bit field overflows, the
CPU 177