Measure Reference Manual

DBIO-WRITE-BYTES
Number of bytes transferred by direct bulk I/O write operations.
Counter type: Incrementing.
DBIO-WRITES
Number of direct bulk I/O write operations to the measured file. This counter is a subset of WRITES.
Counter type: Incrementing.
DELETES-OR-WRITEREADS
Number of calls to the WRITEUPDATE or WRITEUPDATEUNLOCK procedure with a buffer length
of 0 (delete operations) or the number of calls to the WRITEREAD procedure (writeread operations).
This counter includes both user and system calls to these procedures.
Interpretation of this counter depends on the type of file being measured. Delete operations are
performed on disk and tape files. Writeread operations are performed on terminals or processes.
Counter type: Incrementing.
DISC-READS
Number of physical disk reads performed.
Counter type: Incrementing.
ESCALATIONS
Number of times a lock escalated to a file-level lock.
Counter type: Incrementing.
FILE-BUSY-TIME
For waited I/O, the FILE-BUSY-TIME counter is the elapsed time spent executing waited I/O requests.
OSS file opens count file busy time for waited requests after the first significant file operation on
the file. This counter is started by the file system when the message for the I/O request (for example,
READ or WRITE) is sent to the server. The counter is stopped after the reply is received and the
process runs again to process the reply. Thus, the counter includes execution time of the requester,
execution time of the server (for example, DP2 disk process), any physical I/O time (for example,
disk read), and possibly the execution time of higher priority processes in both CPUs, and so forth.
Requests sent during the file open and close and requests sent to the OSS name server are not
counted in the FILE-BUSY-TIME counter, but are counted in the PROCESS entity.
For nowait I/O, the FILE-BUSY-TIME counter is the execution time to initiate nowait I/O requests
to the server and any elapsed time the process actually spends waiting for nowait requests to
complete in AWAITIO[X].
For the OSSPIPE FILE open type, general application usage of the OSSPIPE will allow read() or
write() to complete on a memory-to-memory move and will generate a very low FILE-BUSY-TIME.
However, if applications ignore the OSSFM error EWOULDBLOCK (4101), then FILE-BUSY-TIME
will increment.
Counter type: Busy.
FILE 239