Measure User's Guide

Creating a Custom Measurement Application
Measure User’s Guide—520560-003
6-18
Reading Active Counters
°
The opener^cpu, opener^pin, and file^number fields in the FILE
descriptor
°
The cpu^number and pin fields in the PROCESS and USERDEF descriptors
°
The lh^cpu and system^number fields in the SYSTEM and CLUSTER
descriptors
•
For systems running D-series RVUs:
°
The cpu^number, channel-num, ctrl, and unit fields in the
CONTROLLER, DISC, DEVICE, LINE, NETLINE, and TERMINAL descriptors
•
For systems running G-series RVUs:
°
The cpu^num, servernet, group, module, and slot fields in the DISC and
DEVICE descriptors
°
The cpu^number, trackid, clip, and line fields in the LINE, NETLINE,
and TERMINAL descriptors
°
The cpu^number, group, module, SvNet-node-number, slot, and
remote-CPU fields in the SERVERNET descriptor
MEASREADACTIVE and MEAS_READACTIVE_ ignore the remaining fields in the
descriptors. They can contain any valid value.
You must pass MEASREADACTIVE or MEAS_READACTIVE_ the measurement
number. If you do not have this number (which is returned by MEASCONFIGURE),
obtain it by calling MEASMONSTATUS and looking up the measurement data file
name in the array returned by the procedure. The data file index into the array is the
measurement number. (See Checking the Status of the Subsystem or a Measurement
on page 6-19.)
Because you specify a single entity in the call, MEASREADACTIVE and
MEAS_READACTIVE_ usually return one counter record. The exception is for a
USERDEF entity. Each user-defined counter has its own record, and
MEASREADACTIVE and MEAS_READACTIVE_ return all the counter records
associated with a USERDEF instance if there is room. The largest bufsize value
MEASREADACTIVE supports is 32767 bytes. To configure measurements for which
returning all counters for a USERDEF instance requires more space, use
MEAS_READACTIVE_.
When you start a measurement, MEASCTL initializes any new counters to zero
(except CPU counters, which are initialized at system load). If the counters already
exist because another measurement is using them, however, MEASCTL adopts them
for the new measurement. For this reason, the counter fields in an active counter
record the activity of the entity because the counters were initialized by the first
measurement using them. The FROM-TIMESTAMP field in an active counter record
contains the time and date when the counters were initialized.
Example 6-4 on page 6-19 shows how to call MEASREADACTIVE to read active CPU
counter records one at a time into a buffer. The buffer is defined as an array of referral