Post Processor EADM Activity Report
The EADM Activity report provides detailed information for Extended Asynchronous Data Mover (EADM) activities.
micsrm140
Comprehensive EADM information is provided, encompassing request counts, averages, rates, and percentages of key performance metrics. For IBM z15 and later CPCs, zEDC on-chip compress/decompress metrics are provided. For earlier CPC models, zEDC compress/decompress metrics are provided by the PCIe Activity report.
The report is broken into three sections:
The first section provides the rate of Start Subchannel (SSCH) instructions for all EADM devices, along with a variety of response time metrics.
The second section is produced if the MICS data was produced on an IBM z15 of later CPC, and contains compression and decompression statistics similar to the zEDC statistics provided in the PCIe Activity report for IBM z14 and earlier CPCs.
The third section provides Storage Class Memory (SCM) activity information at both the LPAR and CPC levels for each PCIe Flash Express adapter. For IBM z14 and later CPCs, where Flash Express cards are emulated in the level 3 cache, all SCM activity is reported in a single report line.
Intended use
The EADM Activity report allows you to monitor the performance of EADM activity, for both Storage Class Memory (SCM) and asynchronous compression/decompression handled by IBM z15 and later CPCs using on-chip hardware.
Report Format
See EADM Activity Report for an example of the output generated by the EADM Activity report.
Data source (file/timespan)
HAREAD and HARSCM at all timespans.
Data elements and calculations
Consult the SAS source code used to generate this report in sharedprefix.MICS.SOURCE member:
- @RMFEAD1 - for all systems generating the SMF type 74 subtype 10 records.
How to Produce the Report
- Enter theMICS Workstation Facility(MWF).
- Choose option 2,MICS Information Center Facility(MICF).
- Choose option 2, Database Inquiries.
- Select RMFLPX, whose Catalog Group is PERFORM.
- Complete the MICF Execution panel. (If you are not familiar with MICF, see see Using MICF and MICF Reference.)
- Complete the specification panel illustrated below. (Descriptions of the fields follow the panel.)
+----------------------------------------------------------------------+ |-------------------- Post Processor EADM Activity Report -----------| | Command ===> | | | | Composing Inquiry: RMFLPX - Post Processor EADM Activity Report | | Database ===> ___________ | | Cycle(s) ===> __ - __ | | Timespan ===> ________ (DETAIL/DAYS/WEEKS/MONTHS) | | | | Data Selection: | | dd mmm yy dd mmm yy dd mmm yy dd mmm yy | | Date ===> __ ___ __ - __ ___ __ __ ___ __ - __ ___ __ | | Hour ===> __ - __ | | Zone ===> _ _ _ _ _ _ _ _ _ | | Sysid ===> ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ | | | | Summarization Break Variable ===> ________ | | Summarization Technique ===> _________ (DETAIL or COMPOSITE) | | | | SAS Subsetting Statements ===> | | _______________________________________________________________ | | | +----------------------------------------------------------------------+
Database
(Required) No default. Specify up to six database unit IDs (the IDs of the
MICS database
units from which the files are read). If MICS
files exist in only one database unit, this parameter is set automatically. To display a selection list of valid database unit IDs, specify ? (question mark).Cycle(s)
(Required) Defaults to 01. 00-99 in either data entry field; leading zeros are inserted automatically. The
MICS
files cycle (specify first field) or cycle range (specify both fields) for the inquiry execution.Timespan
(Required) The timespan of the
MICS database
from which the primary input files are selected. See RMF Reports for a listing of file requirements. The MICS
required input files must be available at the specified timespan.Date
(Optional) No default. Up to two date ranges in DD MMM YY format. The first value in each date range is the starting date and the last value is the ending date. The ending date must be higher than the starting date. The date ranges should not overlap, but you can specify the higher range before the lower range. An input observation is selected if its date value is greater than or equal to the starting date and is less than or equal to the ending date of any specified date range.
Hour
(Optional) No default. An hour range from 0 to 23. The first value is the starting hour and the last value is the ending hour. The ending hour must be higher than the starting hour. An input observation is selected if its hour value is greater than or equal to the starting hour and is less than or equal to the ending hour of the specified hour range.
Zone
(Optional) No default. One-character zone value from 1 to 9. You can specify up to nine zone values. An input observation is selected if its zone value is equal to any of the specified values.
SYSID
(Optional) No default. 1-4 character SYSID value. You can specify up to ten SYSIDs. An input observation is selected if its SYSID value is equal to any of the specified values.
Summarization Break Variable
(Optional) No default. Data element name to be used as control-break variable. Valid entries are STARTTS, HOUR, ZONE, DAY, WEEK, MONTH, YEAR, and SYSID.
MICS
summarization facilities are used to preprocess the files used by the report programs. These facilities allow that a data element be defined as a control-break variable and that the summarized file(s) are sorted so the break variable is last in the sort key list. A single summarized observation is then written from multiple observations, with the same break variable value, whenever the break variable value changes.Summarization Technique
(Required) Defaults to DETAIL. Specify DETAIL to cause the input files to be processed and reported in date/time order, or COMPOSITE to force ALL occurrences of the same value of the summarization break variable to be summarized and reported together. See the RMF SUMBY and SUMTYPE - Controlling Summarization section for a more detailed explanation of the summarization control techniques.
SAS Subsetting Statements
(Optional) No default. Free-form user-supplied SAS code. During the creation of the work files used to generate the reports, user-defined SAS code may be included to modify or subset the data.
No validity checking is done on the user-defined code. If it contains syntax or logic errors, the inquiry will either terminate abnormally or will produce unpredictable results.
Examples of valid statements:
IF SYSID EQ "SYS1"; IF DEVTYPE EQ: "3390";
Usage considerations
This inquiry provides a user exit that you can use to perform additional data selection from the
MICS database
. To invoke this exit, you must first copy the shared inquiry into your private MICF catalog, then select it for modification. Finally code SAS statements in the SELECT macro, bracketed by the %MACRO and %MEND statements.The default for the SELECT macro is null. This macro is invoked when the observations are read from the specified
MICS
file(s). You can use it to delete observations from the data as it is selected. For example, in a system activity study, you might want to exclude test systems starting with a T from the analysis. You would then code the following:%MACRO SELECT; IF SYSID NE: 'T'; %MEND SELECT;
Note that you do not have to code the %MACRO and %MEND statements, as they are already provided for you.
You must code each specified SAS statement in accordance with the syntax of the SAS Macro Language, as described in the SAS manuals. No validity checking is done on the defined code. If the user code contains syntax or logic errors, the inquiry will either terminate abnormally or will produce unpredictable results.