Measure Reference Manual

{ “address port” }
{ “address *” }
{ “* port” }
For more information about IP field values, see IP (page 237). Examples of use are in Command
Examples: OSS File Opens (page 244).
ANSI SQL Naming Conventions
In Measure G11 and later PVUs, the FILE entity can provide ANSI SQL names in place of Guardian
file names in its output. For complete details on SQL naming, see the SQL/MX Reference Manual.
Entity Specification Syntax for FILE Entities
To describe FILE entities:
FILE entity-spec [,entity-spec] ...
FILE
In D-series RVUs, collects information about operations on one or more logical files. The file
can be local or remote. However, only local processes that access the file are measured.
In G-series and later RVUs, measures the I/O operations performed by a process on an explicitly
open file (logical file access). The file can be local or remote. However, only local processes
that access the file are measured.
entity-spec
is specified as:
file [ (opener) ] [(file^open^type [, file^open^type, ...] ) ]
where:
file
is the file to be measured. Specify file as one of the following:
{ * }
{ [ [ [\system.]$device.]subvolume.]filename[:crvsn] }
{ [ [\system.]$device.]#tempfile }
{ [ [\system.]$device.]#subdevice }
{ “pathname” }
{ ‘{TABLE|INDEX} [ [catalog.]schema.]object’ }
{ ‘SCHEMA [ [catalog.]schema’ }
{ ‘CATALOG {catalog|* }’ }
where
*
measures all files, temporary files, and subdevices, both local and remote, accessed
by local processes.
\system
is the name of the system that contains the file to be measured. To indicate all systems,
use an asterisk (*). The default is the current default system.
$device
is a name of the volume (device) that contains the file to be measured. To indicate all
devices, use an asterisk (*). The default is the current default device.
subvolume
is the name of the subvolume that contains the file to be measured. To indicate all
subvolumes, use an asterisk (*). The default is the current default subvolume).
230 Entities and Counters