Measure Reference Manual

Common and ZMS Style Only Counter Field DDL Definitions for CPU Entities
These counter fields are used in both styles of DDL records. Fields that are used in ZMS Style DDL
records only are noted.
Fields are listed alphabetically; subfields are listed in the order they occur in the field.
ACCEL-BUSY-TIME
Time that the CPU was busy executing accelerated code. This counter applies only to measurements
taken on a TNS/R system or a TNS/E system.
See Usage Notes for H-Series and J-Series CPU Entities (page 177).
Counter type: Busy.
CACHE-HITS
Number of times the required block was found in cache during an I/O operation.
For a read operation (or the read part of a write operation), a cache hit saves a disk I/O. For a
write operation, the result of a cache hit depends on the type of file I/O. For buffered I/O, the
cache hit saves a disk I/O. For write-through I/O, it does not.
A write operation causes a read in a number of cases. For example, in a key-sequenced file,
writing to a data block can require reads of one or more index blocks. Or, if you write a partially
filled block to disk, the disk process must read the block from disk, merge the new data into the
block, and then write the block to disk.
The DISC entity provides additional cache and I/O information.
In D-series and G-series RVUs, this is a 32-bit counter. In H-series and J-series RVUs, this is a 64-bit
counter.
In G-series RVUs, the CACHE-HITS-F field is a 64-bit version of CACHE-HITS.
Counter type: Incrementing.
COMP-TRAPS
Number of times a compatibility trap occurred on the processor. A compatibility trap is a data
misalignment event, an unexpected transition to or from accelerated or unaccelerated code, or a
relative segment 2 or 3 problem. See the EPTRACE Manual for further details.
Counter type: Incrementing.
CPU-BUSY-TIME
Time that the CPU was busy.
For TNS/R systems, CPU-BUSY-TIME is the sum of ACCEL-BUSY-TIME, TNS-BUSY-TIME,
TNSR-BUSY-TIME, and INTR-BUSY-TIME.
For TNS/E systems, CPU-BUSY-TIME is the sum of ACCEL-BUSY-TIME, TNS-BUSY-TIME, and
NATIVE-BUSY-TIME. A CPU-BUSY-TIME value is always displayed. However, the ACCEL-BUSY-TIME,
TNS-BUSY-TIME, and NATIVE-BUSY-TIME counter values are only calculated and displayed if a
PROCESSH measurement was active during the measurement. For details about the behavior of
the ACCEL-BUSY-TIME, TNS-BUSY-TIME, and NATIVE-BUSY-TIME counters, see the descriptions of
these counters.
For NSMA systems in Measure J01 and later PVUs, CPU-BUSY-TIME is the aggregate of the
BUSY-TIMEs of the individual IPUs that comprise the logical CPU. With REPORT RATE OFF, this
value is the sum of all the IPU-BUSY-TIMEs. With REPORT RATE ON, STYLE ZMS, the maximum
value of CPU-BUSY-TIME is 100% where CPU-BUSY-TIME approaches the AVERAGE of all
IPU-BUSY-TIMEs. With REPORT RATE ON, STYLE LEGACY, the maximum value of CPU-BUSY-TIME
is the Number of IPUs multiplied by 100%.
Counter type: Busy.
166 Entities and Counters