5. FILES › 5.2 HAR Information Area Files › 5.2.27 Physical Hardware File (HARPHY) › 5.2.30.3 Usage Considerations
5.2.30.3 Usage Considerations
Special considerations or techniques related to using the
HARCML file are provided below.
1. The SMF type 113 record, used to create the HARCML file,
is not created by the IBM Resource Measurement Facility
(RMF). As a result, the STARTTS and ENDTS values for
DETAIL level records will not exactly match the other RMF
component database files.
The Hardware Instrumentation Services (HIS) control
statements used to activate SMF type 113 record
collection include a SMFINTVAL=SYNC parameter that
synchronizes SMF type 113 records interval duration and
interval boundaries with those used by RMF, but the
timestamps do not match exactly.
As a result, at the DETAIL timespan, HARCME file
observations cannot be exactly merged with CA MICS files
created from RMF data, such as the HARIPU or HARCPU
files. If SMFINTVAL=SYNC is used in the HIS control
statements, however, merging this file with other RMF
component files at the DAYS and higher timespans will
provide accurate measurement associations.
2. Care must be exercised in using the special date and time
data elements contained in each CA MICS file. As the
file's granularity increases in higher timespans, certain
fields lose significance; they should not be used in
those cases.
o HOUR should not be used in MONTHS.
o DAY and DAYNAME should not be used in WEEKS, MONTHS.
o WEEK should not be used in MONTHS.
3. ENDTS and STARTTS, when appearing in the DAYS, WEEKS, or
MONTHS timespans, bound the span of time over which the
data has been summarized. STARTTS is the lowest date and
time and ENDTS is the highest date and time for the data
summarized. These data elements have different meanings
when used in the DETAIL timespan versus the DAYS, WEEKS,
and MONTHS timespans. Their purpose in DETAIL is
described below:
o STARTTS represents either the start time of an HIS
collection run, or the start time boundary of an
interval record.
o ENDTS represents the HIS interval record end time.
5.2.31 CF Channel Path File (HARCFA)
The CF Channel Path file stores the characteristics of the
channel paths of type CIB or CFP associated to local or
remote coupling facilities on a zEC12. It also contains
limited identification information (channel path id, channel
path type) for channel paths other than CIB or CFP.
This file is derived from the SMF type 74 subtype 4 Coupling
Facility Activity record.
The following sections describe the file's organization, list
the data elements maintained, and provide usage hints.
1 - File Organization
2 - Data Elements List
3 - Usage Considerations
5.2.31.1 File Organization
The table below identifies data elements by which the file is
sequenced and summarized in each timespan. N/A indicates
that the file is not supported in a timespan. At the DETAIL
level, data is sequenced but not summarized.
NOTE: The timespans in which a file is supported are
defined by each installation when CA MICS is installed.
Therefore, this table has been generated as part of the
installation process to accurately reflect the CA MICS system
at your installation.
+---------+-------------------------------------------------+
|Timespan | Level of Data Granularity |
+---------+-------------------------------------------------+
| | |
| DETAIL |SYSID YEAR MONTH DAY HOUR |
| |ENDTS CFYSYSNM CFYCFNM CFYRCFNM CHANNEL |
| | |
| DAYS |SYSID YEAR MONTH DAY HOUR |
| |CFYSYSNM CFYCFNM CFYRCFNM CHANNEL |
| | |
| WEEKS |SYSID YEAR WEEK ZONE HOUR |
| |CFYSYSNM CFYCFNM CFYRCFNM CHANNEL |
| | |
| MONTHS |SYSID YEAR MONTH ZONE CFYSYSNM |
| |CFYCFNM CFYRCFNM CHANNEL |
| | |
| YEARS | N/A |
| | |
+---------+-------------------------------------------------+
| TABLES | N/A |
+---------+-------------------------------------------------+
Generation Date: Mon, Dec 10, 2012
NOTE: This file was generated with ESSENTIAL=ALL
option in effect. All data elements defined in
the file are generated.
NOTE: This file was generated with DERIVED=DEFault
option in effect. Whether data elements are
kept on the file on auxiliary storage or not
is controlled by the complex definition of the
DERIVED option.
Figure 5-36. HARCFA Sort Sequence and Data Granularity
5.2.31.2 Data Elements List
The table below identifies data elements contained in this
file. The entries for each data element are:
TIMESPAN: Defines the timespans in which the data element
is supported. The timespans are indicated by
the letters "XDWMYT" as follows:
X - DETAIL
D - DAYS
W - WEEKS
M - MONTHS
Y - YEARS
T - TABLES AREA
. - File is not supported
The timespan field also indicates Essential Elements with
the letter E, if applicable.
DATA ELEMENT: The data element name.
DATA ELEMENT DESCRIPTION: The data element's long name.
The timespans in which a data element is supported are
defined by each installation when CA MICS is installed.
Therefore, this table has been generated as part of the
installation process to accurately reflect the CA MICS
system at your installation.
GENERATION DATE: Mon, Dec 10, 2012
Note: Essential data elements are identified by an "E"
under the Timespan asterisk (*) column.
Time- Data Data Element
Span * Element Description (LABEL)
------- -------- ----------------------------------------
Sequence/Summary Data Elements
XDWM..E CFYCFNM - CF Name
XDWM..E CFYRCFNM - Remote CF Name
XDWM..E CFYSYSNM - Name of System Using CF
XDWM..E CHANNEL - Physical Channel Address
XD....E DAY - Day of Month
XDW...E HOUR - Hour of Day
XD.M..E MONTH - Month of Year
XDWM..E SYSID - System Identifier
XDW...E WEEK - Week of Year
XDWM..E YEAR - Year of Century
XDWM..E ZONE - Time Zone
Common Data Elements
XDWM..E CFYLPID - CF Logical Partition ID
XDWM..E CYCLETM - RMF Sampling Cycle Interval
XD....E DAYNAME - Name of Day of Week
XDWM..E DURATION - Recording Interval Time
XDWM..E ENDTS - End Time Stamp
XDWM..E INTERVLS - Number of Recording Intervals
XDWM..E MVSLEVEL - MVS Software Level
XDWM..E ORGSYSID - Originating System Identification
XDWM..E PRSMLPNO - Logical Partition Number
XDWM..E RMFESAME - z/Architecture Mode Indicator
XDWM.. RMFGMTOF - GMT to Local Time Offset
X.....E RMFSRL - SMF Record Level Change Number
XDWM..E RMFVER - RMF Version Number
XDWM..E STARTTS - Start Time Stamp
XDWM..E SYSNAME - System Name
XDWM..E SYSPLEX - Sysplex Name
Retained Data Elements
XDWM..E CFAACRNM - Channel Path Acronym
XDWM..E CFADEGRA - Degraded Mode Indicator
XDWM..E CFAEDIST - Channel Path Estimated Distance
XDWM..E CFAHCAID - Host Channel Adapter Identifier
XDWM..E CFAHCAPN - Host Channel Adapter Port Number
XDWM..E CFALATTM - Channel Path Latency Time
XDWM..E CFAOPMOD - Channel Path Operation Mode
XDWM..E CFAPCHID - Physical Channel Id (PCHID)
XDWM..E CFASAP1 - 1st I/O Processor Identifier
XDWM..E CFASAP2 - 2nd I/O Processor Identifier
XDWM..E CFASAP3 - 3rd I/O Processor Identifier
XDWM..E CFASAP4 - 4th I/O Processor Identifier
Accumulated Data Elements
XDWM..E CFADEGCT - Intvls with Channel Path Degraded
5.2.31.3 Usage Considerations
Special considerations or techniques related to using the
HARCFA file are provided below.
1. Care must be exercised in using the special date and time
data elements contained in each CA MICS file. As the
file's granularity increases in higher timespans, certain
fields lose significance; they should not be used in
those cases.
o HOUR should not be used in MONTHS.
o DAY and DAYNAME should not be used in WEEKS, MONTHS.
o WEEK should not be used in MONTHS.
2. ENDTS and STARTTS, when appearing in the DAYS, WEEKS, or
MONTHS timespans, bound the span of time over which the
data has been summarized. STARTTS is the lowest date and
time and ENDTS is the highest date and time for the data
summarized. These data elements have different meanings
when used in the DETAIL timespan versus the DAYS, WEEKS,
and MONTHS timespans. Their purpose in DETAIL is
described below:
o STARTTS represents RMF recording interval start time.
o ENDTS represents RMF recording interval end time.
5.2.32 Crypto PKCS11 Coprocessor Activity File (HARCRK)
The Crypto PKCS11 Coprocessor Activity file provides
statistics on operations that are executed on Cryptographic Express4S
cards configured in PKCS11 coprocessor mode. Measurements
include operations counts, execution times, per second rates,
and utilization percentages, for secure public-key operations
executed by symmetric or asymmetric cryptographic functions.
The information in the HARCRK file is obtained from the
cryptographic PKCS11 coprocessor data section of the SMF type
70 subtype 2 Cryptographic Hardware Activity record.
The following sections describe the file's organization, list
the data elements maintained, and provide usage hints.
1 - File Organization
2 - Data Elements List
3 - Usage Considerations
5.2.32.1 File Organization
The table below identifies data elements by which the file is
sequenced and summarized in each timespan. N/A indicates
that the file is not supported in a timespan. At the DETAIL
level, data is sequenced but not summarized.
NOTE: The timespans in which a file is supported are
defined by each installation when CA MICS is installed.
Therefore, this table has been generated as part of the
installation process to accurately reflect the CA MICS system
at your installation.
+---------+-------------------------------------------------+
|Timespan | Level of Data Granularity |
+---------+-------------------------------------------------+
| | |
| DETAIL |SYSID CRKCCIDX YEAR MONTH DAY |
| |HOUR ENDTS |
| | |
| DAYS |SYSID CRKCCIDX YEAR MONTH DAY |
| |HOUR |
| | |
| WEEKS |SYSID CRKCCIDX YEAR WEEK ZONE |
| |HOUR |
| | |
| MONTHS |SYSID CRKCCIDX YEAR MONTH ZONE |
| | |
| YEARS | N/A |
| | |
+---------+-------------------------------------------------+
| TABLES | N/A |
+---------+-------------------------------------------------+
Generation Date: Fri, Sep 6, 2013
NOTE: This file was generated with ESSENTIAL=ALL
option in effect. All data elements defined in
the file are generated.
NOTE: This file was generated with DERIVED=DEFault
option in effect. Whether data elements are
kept on the file on auxiliary storage or not
is controlled by the complex definition of the
DERIVED option.
Figure 5-37. HARCRK Sort Sequence and Data Granularity
5.2.32.2 Data Elements List
The table below identifies data elements contained in this
file. The entries for each data element are:
TIMESPAN: Defines the timespans in which the data element
is supported. The timespans are indicated by
the letters "XDWMYT" as follows:
X - DETAIL
D - DAYS
W - WEEKS
M - MONTHS
Y - YEARS
T - TABLES AREA
. - File is not supported
The timespan field also indicates Essential Elements with
the letter E, if applicable.
DATA ELEMENT: The data element name.
DATA ELEMENT DESCRIPTION: The data element's long name.
The timespans in which a data element is supported are
defined by each installation when CA MICS is installed.
Therefore, this table has been generated as part of the
installation process to accurately reflect the CA MICS
system at your installation.
GENERATION DATE: Fri, Sep 6, 2013
Note: Essential data elements are identified by an "E"
under the Timespan asterisk (*) column.
Time- Data Data Element
Span * Element Description (LABEL)
------- -------- ----------------------------------------
Sequence/Summary Data Elements
XDWM..E CRKCCIDX - Cryptographic Coprocessor Index
XD....E DAY - Day of Month
XDW...E HOUR - Hour of Day
XD.M..E MONTH - Month of Year
XDWM..E SYSID - System Identifier
XDW...E WEEK - Week of Year
XDWM..E YEAR - Year of Century
XDWM..E ZONE - Time Zone
Common Data Elements
XDWM..E CYCLETM - RMF Sampling Cycle Interval
XD....E DAYNAME - Name of Day of Week
XDWM..E DURATION - Recording Interval Time
XDWM..E ENDTS - End Time Stamp
XDWM..E INTERVLS - Number of Recording Intervals
XDWM..E MVSLEVEL - MVS Software Level
XDWM..E ORGSYSID - Originating System Identification
XDWM..E RMFESAME - z/Architecture Mode Indicator
XDWM.. RMFGMTOF - GMT to Local Time Offset
X.....E RMFSRL - SMF Record Level Change Number
XDWM..E RMFVER - RMF Version Number
XDWM..E STARTTS - Start Time Stamp
XDWM..E SYSNAME - System Name
XDWM..E SYSPLEX - Sysplex Name
Retained Data Elements
XDWM..E CRKCPTYP - Cryptographic Processor Type
Accumulated Data Elements
XDWM..E CRKAGCCT - Intvls with Asymmetric-Key Gen Data
XDWM..E CRKFACCT - Intvls with Fast Asymmetric-Key Data
XDWM..E CRKSACCT - Intvls with Slow Asymmetric-Key Data
XDWM..E CRKSCCCT - Intvls with Complete Symmetric-Key Data
XDWM..E CRKSPCCT - Intvls with Partial Symmetric-Key Data
XDWM..E CRKTOAGC - Asymmetric-Key Generation Operations
XDWM..E CRKTOAGT - Asymmetric-Key Generation Execution Time
XDWM..E CRKTOFAC - Fast Asymmetric-Key Operations
XDWM..E CRKTOFAT - Fast Asymmetric-Key Execution Time
XDWM..E CRKTOOPS - Total Operations
XDWM..E CRKTOSAC - Slow Asymmetric-Key Operations
XDWM..E CRKTOSAT - Slow Asymmetric-Key Execution Time
XDWM..E CRKTOSCC - Complete Symmetric-Key Operations
XDWM..E CRKTOSCT - Complete Symmetric-Key Execution Time
XDWM..E CRKTOSPC - Partial Symmetric-Key Operations
XDWM..E CRKTOSPT - Partial Symmetric-Key Execution Time
XDWM..E CRKTOXET - Total Execution Time
Derived Data Elements
XDWM..E CRKAVAGT - Avg Asymmetric-Key Generation Exec Time
XDWM..E CRKAVFAT - Avg Fast Asymmetric-Key Execution Time
XDWM..E CRKAVSAT - Avg Slow Asymmetric-Key Execution Time
XDWM..E CRKAVSCT - Avg Complete Symmetric-Key Exec Time
XDWM..E CRKAVSPT - Avg Partial Symmetric-Key Execution Time
XDWM..E CRKAVXET - Avg Operations Execution Time
XDWM..E CRKPCAGT - Pct Asymmetric-Key Gen Utilization
XDWM..E CRKPCFAT - Pct Fast Asymmetric-Key Utilization
XDWM..E CRKPCSAT - Pct Slow Asymmetric-Key Utilization
XDWM..E CRKPCSCT - Pct Complete Symmetric-Key Utilization
XDWM..E CRKPCSPT - Pct Partial Symmetric-Key Utilization
XDWM..E CRKPCXET - Pct Utilization
XDWM..E CRKPSAGC - Asymmetric-Key Gen Operations Rate
XDWM..E CRKPSFAC - Fast Asymmetric-Key Operations Rate
XDWM..E CRKPSOPS - Total Operations Rate
XDWM..E CRKPSSAC - Slow Asymmetric-Key Operations Rate
XDWM..E CRKPSSCC - Complete Symmetric-Key Operations Rate
XDWM..E CRKPSSPC - Partial Symmetric-Key Operations Rate
5.2.32.3 Usage Considerations
Special considerations or techniques related to using the
HARCRK file are provided.
1. Care must be taken in using the special date and time
data elements contained in each CA MICS file. As the
file's granularity increases in higher timespans, certain
fields lose significance; they should not be used in
those cases.
o HOUR should not be used in MONTHS.
o DAY and DAYNAME should not be used in WEEKS, MONTHS.
o WEEK should not be used in MONTHS.
2. ENDTS and STARTTS, when appearing in the DAYS, WEEKS, or
MONTHS timespans, bound the span of time over which the
data has been summarized. STARTTS is the lowest date and
time, and ENDTS is the highest date and time for the data
summarized. These data elements have different meanings
when used in the DETAIL timespan versus the DAYS, WEEKS,
and MONTHS timespans. Their purpose in DETAIL is
described here:
o STARTTS represents RMF recording interval start time.
o ENDTS represents RMF recording interval end time.
3. Information related to cryptographic hardware activity is
found in the following four files:
o Crypto Accelerator Activity File (HARCRA)
o ICSF Services Activity File (HARCRF)
o Crypto PKCS11 Coprocessor Activity File (HARCRK)
o Crypto CCA Coprocessor Activity File (HARCRP)
While the data contained in the HARCRF file only applies
to the logical partition (LPAR) that created the RMF
records, the data in the HARCRA, HARCRK, and HARCRP files
always reflects the total activity in your CPC.
Copyright © 2014 CA.
All rights reserved.
|
|