Previous Topic: 3.2.18 Post Processor Workload Activity Goal Mode

Next Topic: 3.2.19 Post Processor Cache Subsystem Detail

3.2.19 Post Processor Cache Subsystem Summary

The Cache Subsystem Summary inquiry provides subsystem level
information on caching performance.  Following the subsystem
summary is an overview providing a single line of information
on each volume attached to the subsystem, and a RAID Rank
Activity section.

INTENDED USE:

The report is intended to help monitor caching performance in
terms of I/O rates and hit percentages for various types of
I/O access.  Information in the report can be used to track
the effects of changes to the overall caching subsystem
options.


REPORT FORMAT:

See Section 3.1.1.13 for an example of the output generated
by the Cache Subsystem Summary report.

DATA SOURCE (file/timespan):

HARCCU, HARCVA and HARRRA 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 @RMFCAC8 - for all systems generating the SMF type 74
             subtype 5 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 RMFLPN, 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.)

+----------------------------------------------------------------------+ |--------------- Cache Subsystem Activity Summary Report ------------| | Command ===> | | | | Composing Inquiry: RMFLPN - Cache Subsystem Act. Summary Rpt | | 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).

  o Optionally, complete the extended option panel
    illustrated below.  (Descriptions of the fields follow
    the panel.)

+----------------------------------------------------------------------+ |--------------- Cache Subsystem Activity Summary Report ------------| | Command ===> | | | | Extended Options for: RMFLPN - Cache Subsystem Act. Summary Rpt | | | | Specify Cache Subsystem IDs to Include in Report: | | SSID List ===> ____ ____ ____ ____ ____ ____ ____ | | or/and | | SSID Range(s) ===> ____ - ____ ____ - ____ ____ - ____ | +----------------------------------------------------------------------+


    Specify Cache Subsystem IDs to Include in Report:
      You can specify up to seven individual subsystem ID
      numbers or/and four subsystem ID ranges, in
      hexadecimal, to include in your report.

USAGE CONSIDERATIONS:

The information recorded in the type 74 subtype 5 cache
subsystem activity record, the data source for the Cache
Device Activity (HARCVA), Cache Control Unit Activity
(HARCCU) and RAID Rank Activity (HARRRA) files, contains
total cache subsystem activity.  Only one system in a shared
DASD environment needs to collect this record type.

If you collect type 74 subtype 5 records with more than one
system sharing a particular caching subsystem, and process
these records in CA MICS, your database will contain
redundant information.  To avoid unnecessary processing and
excessive print volume, it is recommended that you restrict
your inquiry reporting to a single SYSID on the execution
panel when executing this inquiry.


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.