Measure Reference Manual

• In name fields, an asterisk (*) specifies all. Such fields must be left justified and blank filled.
Include, as the left-most character, any appropriate leading character, such as a backslash
(\) for a node, a dollar sign ($) for a volume, or a pound sign (#) for a subdevice.
• To designate all system processes, set the PIN to -2.
Wildcards are not always valid. For example, when Measure reads from active counters, the entity
descriptor you pass to MEASREADACTIVE must specify a single entity.
Excluding Entities from a Set
After specifying a set of entities to measure, you can exclude individual entities from the
measurement. To exclude an entity, add a descriptor for that entity to the configuration table, and
set the type field to a negative value. You can specify a negative value for the type string literal
or the numeric identifier. For example, to measure all CPUs except CPU 6:
1. Add a CPU descriptor in which type is set to CPU^T and cpu^number is set to ALL.
2. Add a second CPU descriptor in which type is set to -CPU^T (the negative literal that
corresponds to CPU^T) and cpu^number is set to 6.
To use numeric type identifiers instead of string literals:
1. Add a descriptor in which type is set to 1 (the numeric identifier for CPU) and cpu^number
is ALL (or the equivalent numeric literal, -1).
2. Add a second descriptor in which bit 0 of the type field is set to 1. This bit sets the exclude
flag and is equivalent to setting a negative value.
3. Set bits 1 through 15 of the type field to 1, the numeric type identifier for CPU.
4. Set the cpu^number field to 6.
Specifying File and Device Names
All disk file, system, device, and process names must be in local internal name format. For
descriptions of internal file name formats, see the Guardian Procedure Calls Reference Manual. If
you use an asterisk in a name field or subfield, you must include the appropriate leading character
(\, $, or #) and pad the field with blanks.
Specifying ANSI SQL Names
In the Measure G11 and H01 PVUs, additional fields have been added to some of the entity
descriptors to support ANSI SQL names.
When an ANSI SQL name is passed as an argument to a procedure, it should not be enclosed in
single quotes.
For more information, see Handling of ANSI SQL Names (page 149).
Creating the Configuration Table
The configuration table (contab) defines which entities are in a measurement. You pass the
configuration table to MEASCONFIGURE before you start a measurement. Once a measurement
is configured, you can read its configuration table by calling MEASREADCONF or MEASINFO.
The configuration table consists of:
• A header record
• The entity descriptor sections
• A trailer record
Both the header and trailer records have fixed lengths. The entity descriptor sections can vary in
length, so the table as a whole is variable length.
Measure Procedures Overview 377