6. DATA SOURCES › 6.8 PR/SM LPAR Concepts › 6.8.5 Data Analysis › 6.8.5.1 PR/SM Related Hardware and SCP Analyzer Files › 6.8.5.1.2 HARVPA/HARLPC Relationship › 6.8.5.1.2.2 System z9 and Later Models' Data Organization
6.8.5.1.2.2 System z9 and Later Models' Data Organization
Starting with the IBM System z9, processors defined as ICF,
IFL, IFA (zAAP), or IIP (zIIP) are managed in four separate
pools, in addition to the standard CP processors' pool. The
HARVPA and HARLPC files provide separate sets of measurements
for each of the five possible pools (CP, ICF, IFL, zAAP,
zIIP), simplifying management of the processor resources
within a PR/SM configuration.
Note that the HARLPC file contains a separate specialized
processor management flag, LPCSEPPU, that can be used to
determine the scope of data elements related to ICF
processors. For System z9 and later models, LPCSEPPU is
equal to Y, indicating that the data elements related to ICF
processors only describe the activity of internal coupling
facilities, while additional sets of data elements, specific
to IFLs, zAAPs, and zIIPs, are available.
Think of the HARVPA/HARLPC files' organization in terms of
tables with rows and columns. The HARVPA file contains one
row per logical processor configured within a logical
partition. In each row, one column is used to identify
whether the remaining metrics pertain to a standard CP
processor, an internal coupling facility (ICF), an integrated
facility for Linux (IFL), a System z9 Application Assist
Processor (zAAP), or a System z9 Integrated Information
Processor (zIIP). The same information is represented in the
HARLPC file by a single row for each logical partition with
five sets of summarized data columns for standard CP
processors, internal coupling facilities (ICF), integrated
facilities for Linux (IFL), System z9 Application Assist
Processors (zAAP), and System z9 Integrated Information
Processors (zIIP).
Example
-------
Let's assume the following PR/SM configuration:
o ZOS1 is z/OS LPAR configured with two standard CP
processors, one zAAP, and one zIIP.
o ZOS2 is z/OS LPAR configured with two standard CP
processors.
o CF1 is a coupling facility LPAR configured with one
internal coupling facility (ICF).
o LNX1 is Linux only LPAR configured with one integrated
facility for Linux (IFL).
HARVPA structure
----------------
LPAR Log. Proc Log Proc Processor
Name Address Type Busy Time
---- --------- -------- ---------
ZOS1 0 CP 07:00
ZOS1 1 CP 07:00
ZOS1 2 IFA 12:00
ZOS1 3 IIP 05:00
ZOS2 0 CP 03:00
ZOS2 1 CP 03:00
CF1 0 ICF 15:00
LNX1 0 IFL 15:00
HARLPC structure
----------------
LPAR LPAR Std CP ICFs IFLs zAAPs zIIPs
Name Type Busy Tm Busy Tm Busy Tm Busy Tm Busy Tm
---- ---- ------- ------- ------- ------- --------
ZOS1 CP 14:00 00:00 00:00 12:00 05:00
ZOS2 CP 06:00 00:00 00:00 00:00 00:00
CF1 ICF 00:00 15:00 00:00 00:00 00:00
LNX1 ICF 00:00 00:00 15:00 00:00 00:00
For ZOS1, busy times for processors 0 and 1 have been
consolidated in the overall busy time for all standard CP
processors (same for ZOS2), busy time for the zAAP (processor
2) has been summarized in the ZOS1 overall busy time for all
processors belonging to the zAAP pool, and busy time for the
zIIP (processor 3) has been summarized in the ZOS1 overall
busy time for all processors belonging to the zIIP pool. CF1
with its internal coupling facility only contributes to the
ICF pool, and LNX1 with its integrated facility for Linux
only contributes to IFL pool.
