Measure Reference Manual

by the memory manager process, PIN 1, which also sponsors pages allocated by and
for the system.
◦ An unsponsored locked page frame remains unsponsored (associated with no process)
until the next routine visit by the Memory Manager process.
• The initial record of the PROCESS entity is created when the process is started and not at the
measurement start time. During active retrieval the current counter values are shown taking in
consideration the delta time between the initial record and the current record. The counters
ACCEL-BUSY-TIME, NATIVE-BUSY-TIME, and TNS-BUSY-TIME are calculated, returned, and
displayed only if a PROCESSH measurement is active in the CPU where the process is running.
Otherwise, the counters are not displayed, and their values in the returned record are zero.
If the PROCESSH measurement has not been active since the process was started (which is
likely for most system processes), the counter values will not be correct.
The counters are calculated based on the number of PROCESSH samples observed in the
applicable code region, and so for more accurate numbers, you can increase the frequency
of PROCESSH samples. The PROCESSH-SAMPLES counters of the CPU entity reports the current
sampling frequency.
Effective with Measure H04/J02, and later PVUs, if the PROCESSH sample count is unchanged
from the start to the end of a measurement interval, the ACCEL-BUSY-TIME, NATIVE-BUSY-TIME,
and TNS-BUSY-TIME fields will not be displayed by MEASCOM even if a PROCESSH
measurement is active. For the LISTALL command, this means some intervals might display
those fields and others might not.
The MEASCOM command LISTACTIVE FOR time will give correct values for the counters
ACCEL-BUSY-TIME, NATIVE-BUSY-TIME, and TNS-BUSY-TIME only if a PROCESSH measurement
was running during the entire time period in question.
Usage Notes for G-Series PROCESS Entities
• The 64-bit byte-count fields ending in -F collect the same data as existing 32-bit byte-count
fields. For example, the 64-bit field RETURNED-BYTES-F collects the same data as the 32-bit
field RETURNED-BYTES. The 64-bit fields are less subject to overflow caused by high levels of
I/O activity.
The 32-bit fields are currently active and continue to return values. (A field overflow is indicated
by a value of -1 in both the field that has overflowed and in the ERROR field for the measured
entity.) However, you should convert your applications to use the 64-bit fields. The 32-bit fields
might be deactivated in a future RVU.
In MEASCOM commands and in command (OBEY) files, use the names of the 32-bit fields.
For example, issue the command LIST PROCESS BY RETURNED-BYTES, not LIST PROCESS BY
RETURNED-BYTES-F. MEASCOM uses the names of the 32-bit fields in output displays such
as reports and plots.
• In G05 and later RVUs, changes in memory handling have introduced the concept of sponsored
and unsponsored memory pages. Pages are sponsored in memory by the process that causes
them to be present (usually, but not always, the process that defines the segment). If a process
that is the sponsor of shared pages terminates, the pages become temporarily unsponsored.
The next sharing process to reference an unsponsored page becomes the sponsor for that
page.
The PRES-PAGES-QTIME counter provides information about pages sponsored by the measured
process.
• For a discussion on the different types of message system transfer protocols and concepts,
(pre-push, post-pull, linker and listener), see the NonStop S-Series Server Description Manual.
312 Entities and Counters