Previous Topic: 3.4 CSV Extracts

Next Topic: 3.4.2 Paging Activity (RMFED3)

3.4.1 CPU and ASID Activity (RMFED1)


INQUIRY ID:

     RMFED1

DATA SOURCE (file/timespan):

     HARCPU at the DAYS timespan

OUTPUT CONTROL PARAMETER:
     1) Daily -  Percent CPU Busy by System
         -- K3D1 (Three key columns, one three-dimensional
            area chart per system/date)

     2) Daily -  ASID Activity by System
         -- K3D9 (Three key columns, nine three-dimensional
            area charts per system/date)

DATA ELEMENTS USED:

     SYSID    - SYSID
     DATE     - Date
     HOUR     - Hour
     CPUPCBSY - Pct CPs Busy
     CPUPCBZP - Pct zAAPs Busy
     CPUPCBSU - Pct zIIPs Busy
     CPUTOBTM - Total Time CPs Busy
     CPUZPBTM - Total Time zAAPs Busy
     CPUSUBTM - Total Time zIIPs Busy
     CPUTOOTM - Total CPs Online Time
     CPUZPOTM - Total zAAPs Online Time
     CPUSUOTM - Total zIIPs Online Time
     CPUAVONL - Avg Online CPs
     CPUAVOZP - Avg Online zAAPs
     CPUAVOSU - Avg Online zIIPs
     CPUTOONL - Total Online CPs
     CPUTOOZP - Total Online zAAPs
     CPUTOOSU - Total Online zIIPs
     INTERVLS - Number of Recording Intervals
     CPUAVB   - Avg Batch Users
     CPUAVT   - Avg Tso Users
     CPUAVE   - Avg OMVS Users
     CPUAVI   - Avg In Users
     CPUAVP   - Avg APPC Users
     CPUAVS   - Avg Started Users
     CPUAVA   - Avg Logical Wait Users
     CPUAVL   - Avg Logical Ready Users
     CPUAVO   - Avg Out and Ready Users
     CPUAVR   - Avg In and Ready
     CPUAVW   - Avg Out and Wait Users
     CPURSMP  - Number of RMF Samples
     CPUATT   - Total Logical Out Wait Users
     CPUBTT   - Total Batch Users
     CPUETT   - Total OMVS Users
     CPUITT   - Total In Users
     CPULTT   - Total Logical Out Ready Users
     CPUOTT   - Total Out and Ready Users
     CPUPTT   - Total APPC Users
     CPURTT   - Total In and Ready Count
     CPUSTT   - Total Started Users
     CPUTTT   - Total Tso Users
     CPUWTT   - Total Out and Wait Users

CALCULATIONS:

     DATE = MDY(MONTH,DAY,%YEAR4);

USAGE CONSIDERATIONS:

     Not applicable

EXECUTION-TIME PARAMETERS:

     Execution-time parameters enable you to produce a CSV
     file containing just the information you want.  This
     reduces the:

     o  Amount of data extracted
     o  Network traffic during download

     as well as makes the presentation more effective.

+--------------------------------------------------------------------------------+ | ------------------------- Execution-Time Parameters -------------------------| | Command ===> Scroll ===> CSR | | | | Executing CA MICS Inquiry: RMFED1 - CPU and ASID Activity (.CSV) | | | | ------------------------------------------------------------------------------ | | Enter one or more Data Base IDs for the Data Base(s) you want to process. | | _____________________________________ - _____________________________________ | | | | Enter range of CA MICS online file cycles or enter ARCHIVE for archive files.| | _____________________________________ - _____________________________________ | | | | Enter the range of dates (DDMMMYY) to be reported or leave blank for all | | _____________________________________ - _____________________________________ | | | | Enter the range of hours to be reported or leave blank to report all | | _____________________________________ - _____________________________________ | | | | Enter the SYSID(s) to be reported or leave blank to report all systems | |_____________________________________ - _____________________________________ | | | +--------------------------------------------------------------------------------+



Enter one or more Data Base IDs for the Data Base(s) you want
to process.

-- Required.  Specify database unit IDs (the IDs of the
   CA MICS database units from which files are read).  To
   display a selection list of valid database unit IDs,
   specify ? (question mark).

Enter range of CA MICS online file cycles or enter ARCHIVE
for archive files.

-- Required.  These are the cycles of the specified timespan
   for the CA MICS files that are used as input to the
   analysis.  You can specify a range of cycles in either
   ascending or descending order (for example, 01-03 or
   03-01).  The fields can contain any numeric value between
   0 and 99, or "ARCHIVE" for archive files.

Enter the range of dates (DDMMMYY) to be reported or leave
blank for all.

-- Optional.  Specify the date range in DDMMMYY format (for
   example, 01OCT10).  The first date range is the starting
   date and the last value in each date range is the ending
   date.  The ending date must be higher than, or equal to
   the starting date.  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 the
   specified date range.  If only one value is specified, an
   observation is selected if its date value is equal to the
   specified value.

Enter the range of hours to be reported or leave blank to
report all.

-- Optional.  The first value is the starting hour and the
   last is the ending hour.  The ending hour must be higher
   than, or equal to 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 date range.  If only one value is
   specified, an observation is selected if its hour value is
   equal to the specified value.

Enter the SYSID(s) to be reported or leave blank to report
all systems.

-- Optional.  Specify one or more 1-4 character SYSID
   value(s).  Observations whose SYSID value is equal to any
   of the specified values are selected.  If not specified,
   all are selected.