SQL/MX 3.2 Management Manual (H06.25+, J06.14+)

Table Of Contents
Figure 5 Measure Entities and Program Structures
To reduce the cost of overhead for the Measure interface to NonStop SQL/MX, the Measure product
updates more than one counter per call. The overall cost of using the Measure product depends
on the frequency of the intervals for measurements and on the number of active SQL statements.
As the number of active SQL statements in a program increases, the cost of performing measurements
increases.
The Measure product provides other entities to measure activity on processes, processors, and disk
processes. For more information on how to set up the Measure product and prepare reports, see
the Measure Reference Manual and the Measure User’s Guide.
Statistics and Reports for NonStop SQL/MX
Use the Measure entities to gather statistics on an SQL/MX database and application programs.
After gathering the statistics, you can generate reports about the statistics. Information gathered
by the entities is described next.
SQLPROC Statistics
The SQLPROC report provides information about specific statistics concerning recompilations,
NEWPROCESS calls, and opens of files or processes.
You can monitor automatic recompilation time with the SQLPROC report, but not for the purpose
of determining the best compiler option. SQL/MX supports no compiler options and only recompiles
on demand when an SQL statement needs to be automatically recompiled at run time.
SQLSTMT Statistics
The SQLSTMT report provides information for specific statements of an SQL process. SQLSTMT
entities gather statistics for all statements of a process selected for measurement. These statistics
encompass the sum of activity on all files used by the SQL query.
One SQLSTMT entity exists for each statement. The SQLSTMT report contains the module name
and the statement index that you can use to identify the statement in a compiled module. See the
embedded module definition or the module definition file for a list of statement indexes and
associated statement names. For a dynamic SQL statement, the module name appears as
SQLMX^EXECUTE_statement-name, and the statement index is zero.
The SQLSTMT report gathers statistics on these measurements:
Busy time
Calls
Measure Performance Measurement Tool 285