

5. FILES › 5.3 SCP Information Area Files › 5.3.17 USS Kernel Activity File (SCPKRN) › 5.3.17.3 Usage Considerations
5.3.17.3 Usage Considerations
Special considerations or techniques related to using the
SCPKRN 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.3.18 Serialization Delay Details File (SCPSRD)
The Serialization Delay Details file provides contention
information at the address space level for different types of
suspend locks, GRS enqueues, and GRS latches: CMS locks, CMS
enqueue/dequeue locks, CMS latch locks, CMS SMF locks, local
locks, and CML locks.
This file is derived from the RMF Serialization Delay
Records, type 72 subtype 5.
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.3.18.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 ASID JOB WLMCLASS WLMCLSPD |
| |SRDTOKEN |
| | |
| DAYS | N/A |
| | |
| WEEKS | N/A |
| | |
| MONTHS | N/A |
| | |
| YEARS | N/A |
| | |
+---------+-------------------------------------------------+
| TABLES | N/A |
+---------+-------------------------------------------------+
Generation Date: Wed, Apr 18, 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-57. SCPSRD Sort Sequence and Data Granularity
5.3.18.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: Wed, Apr 18, 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
X.....E ASID - Address Space Identification
X.....E DAY - Day of Month
X.....E HOUR - Hour of Day
X.....E JOB - Job Identification
X.....E MONTH - Month of Year
X.....E SRDTOKEN - Address Space SToken
X.....E SYSID - System Identifier
X.....E WEEK - Week of Year
X.....E WLMCLASS - Service Class Name
X.....E WLMCLSPD - Service/Report Class Period
X.....E YEAR - Year of Century
X.....E ZONE - Time Zone
Common Data Elements
X.....E CYCLETM - RMF Sampling Cycle Interval
X.....E DAYNAME - Name of Day of Week
X.....E DURATION - Recording Interval Time
X.....E ENDTS - End Time Stamp
X.....E GRSMODE - GRS Mode
X.....E INTERVLS - Number of Recording Intervals
X.....E MVSLEVEL - MVS Software Level
X.....E ORGSYSID - Originating System Identification
X.....E RMFESAME - z/Architecture Mode Indicator
X..... RMFGMTOF - GMT to Local Time Offset
X.....E RMFIML - I/O Measurement Level
X..... RMFSRL - SMF Record Level Change Number
X.....E RMFSYNCH - Intvls with RMF Synchronized to SMF
X.....E RMFVER - RMF Version Number
X.....E SAMPLES - RMF Sample Count
X.....E STARTTS - Start Time Stamp
X.....E SYSNAME - System Name
X.....E SYSPLEX - Sysplex Name
Accumulated Data Elements
X.....E SRDTOCLA - CML Lock Owner Contentions with QLen>1
X.....E SRDTOCLS - Total CML Lock Owner Contentions
X.....E SRDTOCLT - Total CML Lock Owner Contention Time
X.....E SRDTOCMA - CMS Lock Contentions with QLen>1
X.....E SRDTOCMS - Total CMS Lock Contentions
X.....E SRDTOCMT - Total CMS Lock Contention Time
X.....E SRDTOCRA - CML Lock Req. Contentions with QLen>1
X.....E SRDTOCRS - Total CML Lock Requestor Contentions
X.....E SRDTOCRT - Total CML Lock Requestor Contention Time
X.....E SRDTOEDA - CMSEQDQ Lock Contentions with QLen>1
X.....E SRDTOEDS - Total CMSEQDQ Lock Contentions
X.....E SRDTOEDT - Total CMSEQDQ Lock Contention Time
X.....E SRDTOLAA - CMSLatch Lock Contentions with QLen>1
X.....E SRDTOLAS - Total CMSLatch Lock Contentions
X.....E SRDTOLAT - Total CMSLatch Lock Contention Time
X.....E SRDTOLCQ - Latch Set Creator Cont. Time Sum Squares
X.....E SRDTOLCS - Total Latch Set Creator Contentions
X.....E SRDTOLCT - Total Latch Set Creator Contention Time
X.....E SRDTOLOA - Local Lock Contentions with QLen>1
X.....E SRDTOLOS - Total Local Lock Contentions
X.....E SRDTOLOT - Total Local Lock Contention Time
X.....E SRDTOLRQ - Latch Requestor Cont. Time Sum Squares
X.....E SRDTOLRS - Total Latch Requestor Contentions
X.....E SRDTOLRT - Total Latch Requestor Contention Time
X.....E SRDTOSMA - CMSSMF Lock Contentions with QLen>1
X.....E SRDTOSMS - Total CMSSMF Lock Contentions
X.....E SRDTOSMT - Total CMSSMF Lock Contention Time
X.....E SRDTOSSQ - GRS ENQ Systems Cont. Time Sum Squares
X.....E SRDTOSSR - Total GRS ENQ Systems Requests
X.....E SRDTOSSS - Total GRS ENQ Systems Contentions
X.....E SRDTOSST - Total GRS ENQ Systems Contention Time
X.....E SRDTOSTQ - GRS ENQ Step Contention Time Sum Squares
X.....E SRDTOSTR - Total GRS ENQ Step Requests
X.....E SRDTOSTS - Total GRS ENQ Step Contentions
X.....E SRDTOSTT - Total GRS ENQ Step Contention Time
X.....E SRDTOSYQ - GRS ENQ System Cont. Time Sum Squares
X.....E SRDTOSYR - Total GRS ENQ System Requests
X.....E SRDTOSYS - Total GRS ENQ System Contentions
X.....E SRDTOSYT - Total GRS ENQ System Contention Time
Derived Data Elements
X.....E SRDAVCLT - Avg CML Lock Owner Contention Time
X.....E SRDAVCMT - Avg CMS Lock Contention Time
X.....E SRDAVCRT - Avg CML Lock Requestor Contention Time
X.....E SRDAVEDT - Avg CMSEQDQ Lock Contention Time
X.....E SRDAVLAT - Avg CMSLatch Lock Contention Time
X.....E SRDAVLCT - Avg Latch Set Creator Contention Time
X.....E SRDAVLOT - Avg Local Lock Contention Time
X.....E SRDAVLRT - Avg Latch Requestor Contention Time
X.....E SRDAVSMT - Avg CMSSMF Lock Contention Time
X.....E SRDAVSST - Avg GRS ENQ Systems Contention Time
X.....E SRDAVSTT - Avg GRS ENQ Step Contention Time
X.....E SRDAVSYT - Avg GRS ENQ System Contention Time
X.....E SRDLCDEV - Latch Set Creator Cont. Time Std Dev
X.....E SRDLRDEV - Latch Requestor Cont. Time Std Dev
X.....E SRDSSDEV - GRS ENQ Systems Contention Time Std Dev
X.....E SRDSTDEV - GRS ENQ Step Contention Time Std Dev
X.....E SRDSYDEV - GRS ENQ System Contention Time Std Dev
5.3.18.3 Usage Considerations
Special considerations or techniques related to using the
SCPSRD 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 decreases 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.3.19 Serialization Delay System File (SCPSRS)
The Serialization Delay System file provides system-wide
summary contention information for all address spaces, for
different types of suspend locks, GRS enqueues, and GRS
latches: CMS locks, CMS enqueue/dequeue locks, CMS latch
locks, CMS SMF locks, local locks, and CML locks.
This file is derived from the RMF Serialization Delay
Records, type 72 subtype 5.
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
Copyright © 2014 CA.
All rights reserved.
 
|
|