Measure Reference Manual

Counter type: Accumulating
Usage Notes for All FILE Entities
• FILE counters are useful for detecting potential problems in database access.
• The Measure subsystem tracks only local entities. Therefore, the FILE entity includes I/O
operations performed by local user processes only. The files being accessed can be local,
remote, or both, depending on the measurement configuration.
• The FILE entity measures all partitions of a partitioned file together, as a single entity. To
measure partitions individually, use the DISCOPEN entity.
• The FILE entity cannot measure files, such as alternate-key files, that are not explicitly opened
by your application.
• Remote Data Facility and TMF I/O operations are not reported under the FILE entity because
these operations are performed by direct interface with the disk process.
Usage Notes for H-Series and J-Series FILE Entities
• In H-series and J-series RVUs, all byte-count fields accommodate 64 bits. Field names ending
in -F are no longer used in ZMS style records but remain available to applications that request
data in legacy style.
• In H-series and J-series RVUs, SUBSYSTEM-VERSION for ZMSFILE records is provided by the
Guardian or OSS file system, depending on the type of open represented by the ZMSFILE
record.
Usage Notes for G-Series FILE Entities
• In Measure G11 and later PVUs, FILE records all ANSI SQL file opens.
• In G-series RVUs, SUBSYSTEM-VERSION has a value of zero.
• The 64-bit byte-count fields (fields ending in -F) collect the same data as older 32-bit byte-count
fields. For example, the 64-bit field MESSAGE-BYTES-F collects the same data as the 32-bit
field MESSAGE-BYTES. The 64-bit fields are less subject to overflow caused by high levels of
I/O activity.
The 32-bit fields are currently active and continue to return values. If no field overflow exists,
the 32-bit fields and the 64-bit fields return the same value. If a 32-bit field overflows, the
corresponding 64-bit field returns the correct value, and the 32-bit field returns a value of -1.
The ERROR field for the measured entity also returns -1 to indicate an overflow condition.
Convert your applications to use the 64-bit fields. The 32-bit fields might be deactivated in a
future release.
In MEASCOM commands and in command (OBEY) files, use the names of the 32-bit fields.
For example, issue the command LIST DEVICE BY INPUT-BYTES, not LIST DEVICE BY
INPUT-BYTES-F. MEASCOM uses the names of the 32-bit fields in output displays such as
reports and plots.
• In the Measure G09 PVU support for OSS file pathnames, file records are available for opens
of OSS files only through the Guardian file system. In Measure G10 and later PVUs, the FILE
entity records opens by the OSS file system.
FILE 243