IBM Hydra MICF Inquiry General Information

All IBM Hydra MICF inquiries use similar inquiry specification panels. In addition, the report headings have similar content.
micsrm140
The IBM Hydra MICF specification panels and report headings are described in the following sections:

IBM Hydra MICF Inquiry Specification Panels

The rules for filling in fields on the panels are identical for all IBM Hydra reports, with the following exceptions:
The "Composing Inquiry" line is different for each report. It gives the report ID (for example, TAPLHA) and the report title (for example, IBM Hydra Performance Overview Report).
A sample inquiry specification panel for inquiry TAPLHA is shown below. Explanations for field choices follow.
+-------------------------------------------------------------------------------+ | ------------------------- MICS IBM Hydra Inquiry -------------------------- | | Command ===> | | | | Composing Inquiry: TAPLHA - IBM Hydra Performance Overview | | Database ===> _ | | Cycle(s) ===> __ - __ | | Timespan ===> ______ (DETAIL/DAYS/WEEKS/MONTHS) | | Report by hour (DETAIL, DAYS, WEEKS only) ===> _ (Y/N) | | Generate report for each value of ZONE ===> _ (Y/N) | | | | Data Selection: | | dd mmm yy dd mmm yy dd mmm yy dd mmm yy | | Date Ranges ===> __ ___ __ - __ ___ __ __ ___ __ - __ ___ __ | | Hour ===> __ - __ __ - __ __ - __ | | Zone ===> _ _ _ _ _ _ _ _ _ | | Cluster ID Selection - ALL (default) | | (HVTCLID) ===> _ _ _ _ _ _ _ (blank/0-7) | | | +-------------------------------------------------------------------------------+
Composing Inquiry
(Required) No default. The report ID and report title.
Database
(Required) No default. Up to six database unit IDs can be specified (the IDs of the
MICS database
units from which files are read). Duplicates are not allowed. 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. The cycle of the specified timespan of the
MICS
files that are used as input to the analysis. A range of cycles can be specified. The fields can contain any numeric value between 0 and 99. If a single cycle is required (such as cycle 01), it must be specified in the first entry field, and the second field must be blank. Leading zeros are not required and are inserted automatically if a single-digit number is entered (for example, 7 becomes 07). If a cycle range is specified, it can be specified in either ascending or descending order (for example, 01-05 or 05-01).
Timespan
(Required) Default varies by report. The timespan of the
MICS
files that are used as input to the analysis. Required input files must be available at the specified timespan.
Report by hour
(Required) Defaults to Y. At the DAYS and WEEKS timespans, reports can be produced at an hourly, daily, or weekly level. If you specify Y (Yes), the data is summarized and displayed by hour, and separate reports are produced for each day or week. If you specify N (No), the data is summarized by day or week, and a single report listing all days or weeks is produced.
Generate report for each value of Zone
(Required) Defaults to N. Reports for each zone can be generated when requested if you specify Y (Yes). The nature and resource requirements of processing often change from one zone to another (for example, prime shift online demands as opposed to production batch requirements at non-prime shift periods). Zone reporting gives you the ability to display separate reports for each observed zone. If you specify N (No), the data is summarized to the appropriate level and displayed on a single report.
Date Ranges
(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 the higher range can be specified before the lower range. For example, a valid date range specification is specifying date range 1 as 01 JAN 09 - 31 DEC 09 and specifying date range 2 as 01 JAN 08 - 31 DEC 08. 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. 0 to 23. Up to 3  hour ranges. 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. The hour ranges should not overlap, but the higher range can be specified before the lower range. For example, a valid hour range specification is 18 - 23 and 09 - 17. 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 any specified hour range.
Zone
(Optional) No default. A one-character value from 1 to 9. Up to nine zone values can be specified. An input observation is selected if its zone value is equal to any of the specified values.
Cluster ID (HVTCLID)
(Optional) Default is blank. The specific Cluster ID's on which to report. Valid values are blank or any numbers 0 through 7. If specific Cluster ID's are specified, the observations that are selected for reporting are limited to those that match the ID's. The default value (blank) means that all Cluster ID's are selected for reporting.

IBM Hydra Report Headers

The report headings for all IBM Hydra reports are similar and consist of general information. The headings and content are as follows:
General Hydra and report information
All IBM Hydra report headings include the following general information:
Report Label
Example
report title
MICS
IBM Hydra Cache Preference Group Report
report granularity
Data Presented by Hour within DAY
Inquiry
TAPLHB
Run Date
10SEPyy
Cluster Identification #
0
Node Identification #
0
Node Serial Number
78-AB123
Grid Composite Identification
10000
Distributed Library Sequence #
00001
Virtual Engine Code Level
5.4.2.132
Report Start
08SEPyyyy
Report End
10SEPyyyy
Timespan
DAYS
The data elements used to populate the heading data are:
heading data
data elements
Report title
MICF generated
Report granularity
MICF generated
Inquiry
MICF generated
Run Date
MICF generated
Cluster Id
HVTCLID - Cluster ID
Node Identification
HVTNODE - Node ID
Node Serial #
HVTSN - Node Serial Number
Grid Composite Identification
HVTGRID - Grid Composite ID
Distributed Library Sequence #
HVTDLSN - Distributed Library Sequence Number
Virtual Engine Code Level
HVTVECD - VE Code Level
Report Start
MICF generated
Report End
MICF generated
Timespan
MICF generated
The first column of each report indicates the time period represented by each line of the report and is dynamically changed based on the report granularity. For example, if the report is by-hour-within-day, the first column heading will be HOUR, and each line of the report will list the hour value reported (for example, 0, 1, 2, and so on). If the report is by-day-within-month, however, the first column heading will be DAY, and each line of the report will list the day value reported (for example, 01-Mo, 02-Tu, 03-We, and so on).