|
|
|
The Enterprise Disk Systems inquiry measures the activities
of an enterprise disk system (or ESS). Depending on the data
that was gathered by RMF, it can contain up to three separate
sections describing system adapters' activity, extent pools'
disk space capacity, and rank performance statistics.
INTENDED USE:
For each adapter of an ESS, the ESS Link Statistics section
contains measurements about the occurred ECKD (for IBM
TotalStorage DS family devices), SCSI, and PPRC I/O
operations. For each link type, this section provides the
average numbers of transferred bytes and operations per
second, as well as their average response time. The I/O
intensity shows how utilized the adapter was during the
report interval. This section is useful for analysis of the
external links' usage and for capacity planning of the
peer-to-peer remote copy (PPRC) links.
The ESS Extent Pool Statistics section provides capacity and
performance information about allocated disk space. For each
extent pool, it shows the real capacity and the number of
real extents. This section can be used to check the
available disk capacity and, if required, change the
capacity.
The ESS Rank Statistics section provides statistics about
read and write operations in each rank of an extent pool. It
also shows the characteristics of the arrays defined in all
ranks. These values reflect the current configuration. You
can use this section to detect and resolve performance
problems and also for disk space capacity planning.
REPORT FORMAT:
See Section 3.1.1.19 for an example of the output generated
by the Enterprise Disk Systems report.
DATA SOURCE (file/timespan):
HARELS, HARERS, HARXPS at the DETAIL, DAYS, WEEKS or MONTHS
timespan.
DATA ELEMENTS USED AND CALCULATIONS:
Consult the SAS source code used to generate this report
in sharedprefix.MICS.SOURCE member:
o @RMFESS1 - for all systems generating the SMF type 74
subtype 8 record.
HOW TO PRODUCE THE REPORT:
o Enter the CA MICS Workstation Facility (MWF).
o Choose option 2, CA MICS Information Center Facility
(MICF).
o Choose option 2, Database Inquiries.
o Select RMFLPT, whose Catalog Group is PERFORM.
o Complete the MICF Execution panel. (If you are not
familiar with MICF, see the MICF User Guide and the MICF
Reference Guide.)
o Complete the specification panel illustrated below.
(Descriptions of the fields follow the panel.)
+----------------------------------------------------------------------+ |------------ Post Processor Enterprise Disk Systems Report ---------| | Command ===> | | | | Composing Inquiry: RMFLPT - Enterprise Disk Systems 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 ===> | | _______________________________________________________________ | | | | Specify Extended Options ===> N (Y/N/R) | +----------------------------------------------------------------------+
Database - Required. No default.
Specify up to six database unit IDs (the IDs of the
CA MICS database units from which the files are read).
If CA 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 CA MICS files cycle
(specify first field) or cycle range (specify both
fields) for the inquiry execution.
Timespan - Required. Defaults to DAYS.
The timespan of the CA MICS database from which the
primary input files are selected. See Chapter 3 for a
listing of file requirements by report. The CA 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. CA 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 section 3.1.2.1.4 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.
IMPORTANT: 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";
Specify Extended Options - Required. Defaults to N (No).
This parameter is used to specify extended options
parameters for the inquiry function. It is displayed
at the bottom of the panel. Specify Y to display the
Extended Options Menu. Extended options parameters are
used to perform additional selections for the report
being defined. Extended options are never required;
default values are provided. A flag will appear to the
right of this parameter if ANY extended option has been
specified. To restore the extended options to their
default values, specify R (Reset).
USAGE CONSIDERATIONS:
This inquiry provides a user exit that you can use to perform
additional data selection from the CA 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
CA 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.
IMPORTANT: 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.
************************************************************
** Note: This report cannot be produced if the CA MICS **
** database contains essential data elements only.**
************************************************************
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |