Measure Reference Manual

OPENER-DEVICE-NAME
Disk device on which the opener program file is located. For SMF files, this field provides the
physical location that corresponds to the logical file name. For NonStop files, this field is the same
as the OPENER-PROGRAM-FILENAME VOLUME subfield.
OPENER-OSSPID
If the opener process runs in the OSS environment, this field contains the OSS Process ID. If this
process is not an OSS process, this field contains zeros.
OPENER-PIN
Process identification number of the process that opened the file.
OPENER-PROCESSNAME
Name of the opener process.
OPENER-PROGRAM-FILENAME
Name of the opener program file. The name can apply to either a NonStop file or an SMF file.
OPENER-PROGRAM-FILENAME has three subfields:
For NonStop files, is the device location of the physical file.
For SMF files, is the device location of the physical file that corresponds to
the logical file name is stored in the DEVICE-NAME field.
VOLUME
For NonStop files, is the device name of the physical volume on which the
program file is located.
SUBVOLUME
For NonStop files, represents the physical program file name of the file
opener.
FILENAME
For SMF files, represents a location-independent logical file name of the file
opener.
OPENER-PROGRAM-FNAME-MID
Internal representation of an OSS file name. OPENER-PROGRAM-FNAME-MID has two subfields:
is an internal representation of an OSS file name. For non-OSS files, this
field contains zeros.
PATHID
is the creation version serial number that identifies a unique instance of an
OSS file. For other files, this field contains zeros.
CRVSN
Common Counter Field DDL Definitions for FILE Entities
These counter fields are used in both styles of DDL records.
Fields are listed alphabetically.
DBIO-READ-BYTES
Number of bytes transferred by direct bulk I/O read operations.
Counter type: Incrementing.
DBIO-READS
Number of direct bulk I/O read operations to the measured file. This counter is a subset of READS.
Counter type: Incrementing.
238 Entities and Counters