Measure Reference Manual

• To add all processes running a specific object file to a measurement and collect procedure
(code-range) execution data:
+ ADD PROCESSH $SYSTEM.SYS00.TCPIP ($SYSTEM.SYS00.TCPIP)
• To add measurement of specific code ranges and provide recognizable names via an EDIT
(code 101) file, either ranges or range offsets can be specified. This example shows use of
offsets to define code ranges:
OBJECT $a.b.prog1
CSS^6100^LEVEL3 130206
FIRST^LOCATION +000000
PROCESS^EVENT +000401
PROCESS^EVENT^1 +001401
PROCESS^EVENT^2 +002401
PROCESS^EVENT^3 +003401
PROCESS^EVENT^4 +004401
PROCESS^EVENT^5 +005401
L4^PROTOCOL +006577
CMI^PROTOCOL +006743
ADD COUNTER
The ADD COUNTER command adds a user-defined counter from a specified process to the current
configuration.
Before configuring a user-defined counter, you must configure the process associated with that
counter. To configure the process, use the ADD USERDEF command (the ADD entity-type
command with USERDEF as the entity type).
For information about counter types, see Interpreting Counter Values (page 137).
Syntax
ADD [ COUNTER ] counter-name, PROCESS process-spec, counter-type [ , ARRAY size ]
COUNTER
is optional if you specified COUNTER as the default command object by using the ASSUME
command.
counter-name
is a counter name. Counter names can contain 1 to 16 letters, numbers, hyphens, and
underscores. The first character must be a letter.
PROCESS process-spec
is the name of a process that maintains the counter. This process specification must match
exactly the process specification in the ADD USERDEF command.
You can use a wild-card template, such as \MAIN.$ACCTS.BILLING.*, as a process
specification. However, all processes indicated by the template must modify the same counters.
ADD COUNTER 43