Measure Reference Manual

{ disk-filename ( pid ) "run-unit", #index }
{ disk-filename ( pid ) "run-unit", [Index] #index }
{ "pname" (pid) "run-unit", #index }
{ "pname" (pid) "run-unit" [Index] #index }
{ pid "run-unit", #index }
{ pid "run-unit" [Index] #index }
where:
*
measures all SQL statements in all processes on the local system.
$process-name
is the name of the process that contains the SQL statements to be measured.
pid
is a process identifier. The process identifier identifies the owner of the process to be
measured. Specify pid as:
{ cpu,pin }
cpu
is the number of the CPU on which the process is running.
pin
is the process identification number of the process. To indicate all PINs, use an asterisk
(*).
run-unit
in Measure pre-G09 PVUs, is the name of a procedure to be measured. For example:
+ LIST SQLSTMT * “max32bytelongrununitname”
in Measure G09 and later PVUs:
• is the SQL/MP procedure name of up to 32 characters, enclosed in double quotes.
For example:
+ LIST SQLSTMT * “max32bytelongrununitname”
+ LISTACTIVE SQLSTMT 3,99 “max32bytelongrununitname”, #1
• is the SQL/MX Release 1 module name of up to 128 characters, enclosed in double
quotes. For example:
+ LIST SQLSTMT * “max128bytelongrununitname”
+ LISTACTIVE SQLSTMT 3,99 “max128bytelongrununitname”, #1
in Measure H01 and later PVUs:
• is the SQL/MX Release 2 module name with only undelimited identifiers of up to 128
bytes, enclosed in double quotes. For example:
+ LIST SQLSTMT * “catA.schemaB.moduleM”
• is the SQL/MX Release 2 module name with a maximum length as supported by
SQL/MX (currently up to 783 characters), enclosed in single quotes. For example:
+ LIST SQLSTMT * ‘catA.”schema%B”.moduleM’
+ LIST SQLSTMT * ‘moduleM’
+ LISTACTIVE SQLSTMT 3,99 ‘catA.”schema%B”.moduleM’, #1
Index
is optional. In Measure G09 and later PVUs, if used, Index enables use of the run unit and
index values (displayed in SQLSTMT reports) for cut-and-paste applications.
SQLSTMT 343