HP NonStop G-Series - Manual (Page 58)

Configuring and Running Measurements
Measure User’s Guide — 520560-003
3- 16
Viewing Reports From Active Counters
Disc-IOs Cache-Hits
Transactions Response-Time
Page-Requests Page-Scans
Ending-Free-Mem 4092 Ending-UCME
Ending-UDS 500 Ending-SDS 1500
Ending-UCL 100 Ending-SCL 2000
Use an asterisk to select all specifications of an entity. When you use the
measurement described previously, the next command lists two reports for each CPU
being measured:
21+ LISTALL CPU *
Use the FROM, TO, and FOR clauses to display data collected between specific times.
For example, to request listings for CPU 2 for intervals completed between 9:00 a.m.
and noon:
22+ LISTALL CPU 2, FROM 9:00, TO 12:00
You can specify the same timeframe using the FROM-FOR clause. For example:
23+ LISTALL CPU 2, FROM 9:00, FOR 3 HOURS
To control the content and format of LISTALL reports, use BY and IF clauses and
REPORT attributes. For more information, see
Section 4, Formatting Reports and
Plots , and the Measure Reference Manual.
Viewing Reports From Active Counters
Active counter records are read by the MEASCTL processes rather than by the
MEASFH process. Each MEASCTL process reads the data from the counters and
passes the information to MEASCOM.
Differences between active counter values and active data file counter values occur in
two cases:
•
Examining a CPU entity
CPU counters are initialized when the CPU is system loaded. Each MEASCTL
process stores current counter values in the data file when a measurement starts.
These values are used to compute CPU use during the measurement. Because
MEASCTL does not initialize the CPU counters when a measurement starts, it
returns the current CPU counter values, which reflect CPU activity since the
system load.
•
Examining an entity included in more than one active measurement
Counter values are stored in a data file for each measurement when the
measurement starts. These initial values are used to compute the counter values
for the life of a measurement. MEASCTL does not keep the counter values for the
start of each measurement, so it returns counter values that reflect entity activity
since the counter was initialized by the first measurement started.