Measure Reference Manual

priority of 100. If the priority for that process were changed to 150 using one of the
procedures listed above, its initial priority would thereafter be 150.
NOTE: The original initial priority value of a process (also known as the creation priority)
is displayed in the first line of the PROCESS header and stored in the PRIORITY field in
the ID section of the ZMSPROC record. This PRIORITY value is static during a measurement.
◦ The CURRENT-PRIORITY-START and CURRENT-PRIORITY-END snapshot counters reflect
the current execution priority at the start and end of a measurement interval. The current
priority can differ from the initial priority because a process may have its priority
decremented by process control. For example: the current priority for a CPU bound process
that started out with an initial priority of 150 may go down to 149, 148, and so on, as
it executes and then return to a current priority (that matches the initial priority) of 150
when it becomes I/O bound.
Configuring a PROCESS entity measurement with intervals, then plotting the
INITIAL-PRIORITY-START/INITIAL-PRIORITY-END and
CURRENT-PRIORITY-START/CURRENT-PRIORITY counters, can provide a historical representation
of the priority changes for a process or set of processes across measurement intervals.
NOTE: Viewing the INITIAL-PRIORITY-START/INITIAL-PRIORITY-END and
CURRENT-PRIORITY-START/CURRENT-PRIORITY-END counter value pairs with LISTACTIVE,
MEASREADACTIVE, MEAS_READACTIVE_ or MEAS_READACTIVE_MANY_, during a running
measurement, produces a value of zero for the START counter and the existing value for the
END counter.
• The PAGE-SIZE-BYTES field for PROCESS entities is supported only in Legacy Style records for
pre-H-Series Measure data files. Although this field may still be populated by Measure G12
and later G-series PVUs, the field is obselete in H-series and J-series RVUs.
• In H-series and J-series RVUs, all byte-count fields accommodate 64 bits. Field names ending
in -F are no longer used in ZMS style records but remain available to applications that request
data in legacy style.
• Counters that report maximum numbers (counters that have MAX in their names) are valid
only in Legacy style. In H-series and J-series RVUs, the value of any such counter is 1.
• In Measure H02, H03, H04, J01, and J02 PVUs, the ZMS style PROCESS displays report a
subsystem version of 2.
• In Measure H05/J03 and later PVUs, the ZMS style PROCESS displays report a subsystem
version of 3.
• In Measure H06/J04 and later PVUs, ZMS style PROCESS and ZMS style CPU support the
LOCKED-PAGES-END and LOCKED-PAGES-START counters. Note the following usage
considerations when using these counters:
◦ The sum of page frames reported as locked in all PROCESS entities for a CPU does not
need to equal the page frames reported as locked in the corresponding CPU entity.
◦ A page frame is locked when it is made present in memory and marked to keep it present.
It becomes unlocked when all such marks are removed, or when the page frame is
de-allocated.
◦ A locked page frame is initially associated with (sponsored by) the process that locked
it. If the page is shared among multiple processes, and the original process terminates,
the page becomes unsponsored; at a later time it becomes sponsored by one of the
remaining processes sharing the page. If the page frame is mapped in global address
space and not in the unique address space of any process, the page becomes sponsored
PROCESS 311