Measure Reference Manual

code-range-address
In an EDIT (code 101) file describing TNS code, code-range-address is
an octal address in the range 0 through 177777 or an address offset.
For EDIT (code 101) files describing TNS/R or TNS/E code,
code-range-address is a valid virtual address for the systems, in
hexadecimal, or an address offset. To indicate an offset from the previous
code-range-address, precede the octal or hexadecimal number with a plus
sign (+). The last code-range-address without a plus sign is added to the
offset to yield the effective address.
The first line of the EDIT file must contain an object file name specifier consisting
of the keyword OBJECT followed by a Guardian file name or OSS pathname.
A Guardian file name example is OBJECT $A.B.MYAPP and an OSS pathname
example is OBJECT "/a/b/myapp".
NOTE: In Measure H02 and later PVUs, support for using EDIT files to specify
code ranges for PROCESSH measurements is no longer available for TNS
executables.
ALLTIME
specifies measurement of the execution time for all processes, including interrupts.
In PVUs earlier than Measure G12, if you specify ALLTIME, you must specify
code-space as SC.n or SL.n for TNS code-file measurements. In Measure G12 and
later PVUs, specify code-space only for TNS and accelerated code. (If you specify
a code-space when it is not required, the parameter is accepted but ignored.)
In H-series and J-series RVUs, if you specify ALLTIME, the code-space you specify
must be a system library. For example:
+ ADD PROCESSH ALLTIME 3 ($SYSTEM.SYS02.INITDLL)
+ ADD PROCESSH ALLTIME 3 ($SYSTEM.ZDLL009A.ZCREDLL)
ALLINTR
specifies measurement of the execution time for all system interrupts.
In PVUs earlier than Measure G12, if you specify ALLINTR, you must specify
code-space as SC.n or SL.n for TNS code-file measurements. In Measure G12 and
later PVUs, specify code-space only for TNS and accelerated code. (If you specify
a code-space when it is not required, the parameter is accepted but ignored.)
This option is disabled in H-series and J-series RVUs. See Usage Notes for H-Series and
J-Series PROCESS Entities (page 310).
cpu
is the number of the CPU on which the process to be measured is running. To indicate
all CPUs, use an asterisk (*). There is no default value.
DDL Record for PROCESSH Entities (ZMS Style)
The ZMS Style DDL record for PROCESSH entities is supported in Measure G11 and later PVUs.
ID Fields DDL Definition
DEFINITION zmsproch-id.
02 pin type binary 16 unsigned.
02 priority type binary 16 unsigned.
02 userid.
03 group type binary 8 unsigned.
03 user type binary 8 unsigned.
02 creatorid.
03 group type binary 8 unsigned.
03 user type binary 8 unsigned.
316 Entities and Counters