Measure Reference Manual

$*.*.file means the specified file in any subvolume in any volume.
• To ensure that the SQLSTMT entity is captured when monitoring a SQL/MP application, start
the SQLSTMT entity measurement before starting the SQL application process and stop the
SQLSTMT entity measurement after the SQL process stops (that is, start and stop the SQLSMT
entity measurement so that it spans the entire execution of the SQL application.)
Usage Notes for H-Series and J-Series SQLSTMT Entities
In H-series and J-series, all byte-count fields accommodate 64 bits. Fields ending in -F are no longer
used in ZMS style records but remain available to applications that request data in legacy style.
Usage Notes for G-Series SQLSTMT Entities
In G-series, 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. (A field overflow is indicated
by a value of -1 in both the field that has overflowed and in the ERROR field for the measured
entity.) However, you should convert your applications to use the 64-bit fields. 32-bit fields might
be deactivated in a future RVU.
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.
Example
The report output for the SQLSTMT entity includes the SQL run unit name in double-quotes or the
ANSI SQL module name in single quotes depending on the name type. For example:
SQL Statement
Procedure 'CATALOG_12.SCHEMA_34.MODULE_56' Index #
Process Pri OSSPID:
Program
OSSPath:
Userid Creatorid Ancestor
Format Version: H01 Data Version: H01 Subsystem Version: 1
Local System
----------------------------------------------------------------------------
Elapsed-Busy-Time 4.17 ms Calls 0.17 /s
Elapsed-Sort-Time Sorts
Elapsed-Recompile-Time Recompiles
Messages 0.22 /s Message-Bytes 931.00 /s
Lock-Waits Escalations
Timeouts Disc-Reads
Records-Accessed 0.17 /s Records-Used 0.17 /s
SYSTEM
The SYSTEM entity provides information about network traffic through Expand line handlers. A
network link involves at least two processes: the linker that initiated the link and the listener that
accepted the link. Because the Measure subsystem can measure only the local system, the
measurement data reflects only one side of each link: the linker or the listener, but not both.
SYSTEM 353