Measure Reference Manual

C Subsystem Files
This list describes the files that make up the Measure performance monitor:
MEASCOM is the Measure subsystem command interpreter. For descriptions of the
commands, see Chapter 2: MEASCOM Commands (page 35). Typically started from
MEASCOM process
TACL, a MEASCOM process lets the user who started it carry on an interactive session
with the Measure subsystem. A super-group user (member of user group 255) can use
MEASCOM to start the Measure subsystem. Thereafter, any user can use MEASCOM
to configure, run, and examine measurements. Concurrent sessions as well as concurrent
measurements within a session are allowed. MEASCOM is stored in $SYSTEM.SYSnn.
Created by the callable procedures whenever you run a measurement or later examine
the resulting data file, one MEASFH process presides over one user-designated data
MEASFH process
file: formatting it, adding data to it, and retrieving data as needed. MEASFH is
release-dependent in that a data file generated in one version can be examined only
by using a MEASFH process of the same version. MEASFH is stored in
$SYSTEM.SYSnn. In the H01 PVU, the default record style changed from Legacy to
ZMS. Accordingly, in G-series and earlier RVUs, fields that appear only in ZMS style
records and reports cannot be used in “IF” clauses, even in the ZMS style report mode.
In H-series and J-series RVUs, fields that appear only in legacy style records and reports
cannot be used in “IF” clauses, even in the legacy style report mode.
Serving as the subsystem monitoring and coordinating process, a single MEASMON
process (running as a process pair) is created when the Measure subsystem is started.
MEASMON process
MEASMON creates a MEASCTL process in each CPU and coordinates the activity of
these processes, sending them measurement configuration requests and gathering
information from them. MEASMON is stored in $SYSTEM.SYSnn.
MEASMON creates one MEASCTL process in each CPU when the Measure subsystem
is started. The job of a MEASCTL process is to handle a description of counter space
MEASCTL process
and to engage the relevant subsystems responsible for maintaining the counters. Among
the tasks performed by MEASCTL are those that initialize counters when a measurement
starts and those that copy counters to the data file. MEASCTL also retrieves for display
the counters a user requests for online examination. MEASCTL is stored in
$SYSTEM.SYSnn.
MEASIP is the Measure Interrupt Process. It does the sampling for a PROCESSH
measurement. The MEASMON process creates one or more MEASIP processes that
MEASIP process
run in each CPU of the local system when the Measure subsystem starts. This process
is not present in RVUs prior to H-series and J-series. MEASIP is stored in
$SYSTEM.SYSnn.
The MEASDDLS file contains the record definitions (DDLs) of the optional structured
files produced by the commands and procedures that display measurement results.
MEASDDLS file
You can use these record definitions to produce language-specific record declaration
files for programmatic use of data or as the basis for user-developed reports using the
Enform product. MEASDDLS is stored in $SYSTEM.SYSnn.
The MEASDDLF file contains FORTRAN DDL definitions. MEASDDLF is stored in
$SYSTEM.SYSnn.
MEASDDLF
The MEASDDLB file contains COBOL85 DDL definitions. MEASDDLB is stored in
$SYSTEM.SYSnn.
MEASDDLB
The MEASDDLZ file lets applications access ZMS style data records with minimal
impact. The ZMS style record structure adds a level of naming to each component of
MEASDDLZ file
the record. The legacy format does not have this additional naming level. For example,
the field cpu.dispatches in a legacy style record is equivalent to the
zmscpu.ctr.dispatches in the ZMS style record structure. Converting existing applications
and ENFORM reports from the legacy naming format to the ZMS style naming format
is a significant edit of record references. It also involves removal of fields that might
be referenced by programs, and the possible combination of equivalent fields that
appeared in two sizes (for example, process.sent-bytes and process.sent-bytes-f). To
simplify this process, use the MEASDDLZ file. MEASDDLZ presents the ZMS style counter
widths and locations in the record using the legacy style record naming convention.
548 Subsystem Files