Measure Reference Manual

• OSS file pathnames can be long (up to 1023 characters in length). In displaying these long
OSS file pathnames, Measure displays the first 80 characters and wraps any remaining
characters to the next line. Measure displays the name in 80-character blocks until the entire
OSS file pathname is displayed. Additionally, if you use the cut-and-paste feature on these
longer OSS file pathnames, you might need to cut and paste the name in sections to avoid
picking up extraneous carriage return characters from the end of each 80-character line.
• The POSIX standards allow the use of nonprintable (nondisplayable) characters in OSS file
pathnames. However, names that use these characters might be handled differently according
to differences in the user interface, workstation, and terminal environments. Neither the OSS
utilities nor Measure deal with this issue.
• Although Measure G09 and later PVUs provide entity support for OSS file pathnames, be
cautious when you use OSS file pathnames in measurement specifications because pathnames
can overrun the buffer limit. For detailed measurements, break the measurement into several
separate measurement configurations. Measure supports up to 64 concurrent measurements.
• Do not confuse the meanings of OSSPID and PID:
OSSPID is a numeric value displayed in many Measure entity reports, and PID is a
Guardian process identifier consisting of CPU, PIN.
◦
◦ PID is used extensively in the Measure command interface, but the Measure command
interface does not support OSSPID.
• OSS file pathnames are null-terminated strings. In Measure, the length of a string field is
required and includes the null character
Guardian File-Name Reuse
Guardian file-name values are based on an internal value or cell in the OSS file system, commonly
referred to as an inode number. When a file and all references to it are deleted, reuse of the inode
number and the file name can occur.
When a file is created on disk, a unique creation version serial number (CRVSN) is assigned to
the file. The CRVSN provides a mechanism to distinguish between various instances of a Guardian
file name. Measure uses the mechanism to avoid file-name resolution problems due to inode number
reuse.
If Guardian file name and CRVSN values do not match the values currently associated in the OSS
name server data, it is assumed that file-name reuse occurred. When file-name reuse occurs, no
associated OSS file pathname is displayed, and this message is generated: *** Translation
Not Available ***.
Handling of the Creation Version Serial Number (CRVSN)
The creation version serial number (CRVSN) is a 48-bit value. Measure displays the CRVSN as a
decimal string of up to 15 characters following the Guardian name (for example,
$DATA01.ZYQ00001.Y00003D2:340359). Measure stores the CRVSN value in data records as
a string of six characters (48 bits).
Measure Identification (MID)
OSS file pathnames are contained within a data structure called a PATHID. PATHIDs are internal
and are passed around in control blocks. When an OSS file pathname is externalized, it is passed
to the OSS name server for file pathname translation.
To support reporting of OSS file pathnames, Measure captures PATHID and CRVSN information
for each OSS file pathname and stores the information in Measure data. The association of a
PATHID and a CRVSN value in Measure data is a Measure ID (MID). The addition of the MID data
does not increase the size of your Measure data file because the MID information and representation
of the internal file name are compressed.
148 Entities and Counters