IBM VTS MICF Inquiry General Information
All IBM VTS MICF inquiries use similar inquiry specification panels. In addition, the report headings have similar content. The specification panels and report headings are described in the following sections.
micsrm140cd
All IBM VTS MICF inquiries use similar inquiry specification panels. In addition, the report headings have similar content. The specification panels and report headings are described in the following sections.
IBM VTS MICF Inquiry Specification Panels
The rules for filling in fields on the panels are identical for all IBM VTS reports, with the following exceptions:
- The "Composing Inquiry" line is different for each report. It gives the report ID (for example, TAPLVA) and the report title (for example, IBM VTS Performance Overview Report).
- The "VTS Type" selection choices vary, depending on the inquiry. For each inquiry, the acceptable choices for that VTS type are listed.
A sample inquiry specification panel for inquiry TAPLVA is shown below. Explanations for field choices follow.
+-------------------------------------------------------------------------------+ | -------------------------- MICS IBM VTS Inquiry --------------------------- | | Command ===> | | | | Composing Inquiry: TAPLVA - IBM VTS Performance Overview Report | | 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 ===> _ _ _ _ _ _ _ _ _ | | VTS Type - ALL (default), COMPOSITE, or STANDALONE | | (IVTTYPE) ===> | | VTS ID | | (IVTVLS) ===> _____ _____ _____ _____ _____ _____ | | | +-------------------------------------------------------------------------------+
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 N. 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 a 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 versus 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 three 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.
Sysid
(Optional) No default. A one to four character value. Up to six SYSIDs can be specified. An input observation is selected if its SYSID value is equal to any of the specified values.
VTS Type (IVTTYPE)
(Optional) Default is ALL. The specific VTS type to report on. Valid values are ALL, STANDALONE, COMPOSITE, UI, or SECONDARY. The specific types that can be selected vary by report and are listed on the specification panel for each report. If a VTS type is specified, the observations that are selected for reporting are limited to those that match that type. The default value ALL means that all VTS types are selected for reporting.
VTS ID (IVTVLS)
(Optional) No default. A one to five character value identifying specific VTSs to report on. Specify up to six VTS Library Sequence Numbers (IVTVLS) to report on. If specific VTS IDs are specified, observations selected for reporting are limited to those that match the specification.
IBM VTS Report Headers
The report headings for all IBM VTS reports are similar and consist of general information plus customized information, based on the VTS type reported on. The headings and content are as follows:
General VTS and report information
All IBM VTS report headings include the following general information:
Report Label | Example |
report title | MICS Tape Data Set Summary Report |
report granularity | Data Summarized by Day |
Inquiry | TAPLVB |
Run Date | 10SEPyy |
VTS Library ID | VTS001 |
Tape Library Type | STANDALONE |
Report Start | 09SEPyy:10:24 |
Report End | 10SEPyy:10:24 |
Timespan | DAYS |
F/C 4001 Status | Enabled |
Note:
The IBM function code F/C 4001 Status (Enabled or Disabled) changes the measurements available in the raw data used to build the MICS
IVT information area files. The F/C 4001 status determines whether some metrics are available for reporting.The data elements used to populate the heading data are:
Heading | Data Element |
Report title | MICF generated |
Report granularity | MICF generated |
Inquiry | MICF generated |
Run Date | MICF generated |
VTS Library ID | IVTVLS - VTS Library Sequence Number |
Tape Library Type | IVTTYPE - VTS Type |
Report Start | MICF generated |
Report End | MICF generated |
Timespan | MICF generated |
F/C 4001 Status | IVT4001 - F/C 4001 Indicator |
Customized information based on VTS type
The VTS types fall into two categories: composite and distributed. The VTS types that fall into each of these categories are as follows:
- Composite category
- COMPOSITE
- Distributed category
- STANDALONE, UI, and SECONDARY
In the general heading information presented above, one of the values is Library Type. The rest of the header information is customized for that type.
For the distributed category (VTS types STANDALONE, UI, and SECONDARY) the additional heading information includes:
Report Label | Example |
Composite ID | VTCC01 |
Library Make-Model | 3584-L22 |
Lib Maint Level | 534.33 |
VTS Cache Size | 1728 GB |
VTS Maint Level | 7414.00 |
The data elements used to populate the distributed VTS category heading data are:
Heading | Data Elements |
Composite ID | IVTCMPID - Composite Library Association |
Library Make-Model: | IVTLTYPE - System-Managed Tape Library Type IVTLMODL - System-Managed Tape Library Model |
Lib Maint Level: | VDLLVLM - Library Manager Version and Release |
VTS Cache Size: | VDLAVCSZ - Avg VTC Cache Size (GB) |
VTS Maint Level: | VDLLVVTS - VTS Code Modification and Fix Level |
For the composite category (VTS type COMPOSITE) the additional heading information includes:
Report Label
| Example
|
UI/SEC IDs | VTS001/VTS001 |
VTC Preferred I/O | NONE |
VTC Preferred Mast | VTS0 |
VTC Maintenance Level | 7414.00 |
Copy Mode Setting | Immediate |
The data elements used to populate the composite VTS category heading data are:
Heading | Data Elements |
UI/SEC IDs: | VCLUIID - UI IVTVLS ID VCLSECID - SECONDARY IVTVLS ID |
VTC Preferred I/O: | VCLPIO - Composite VTC Preferred I/O VTS |
VTC Preferred Mast: | VCLPMST - Composite VTC Preferred Master VTS |
VTC Maintenance Level: | VCLLVVTC - VTC Code Modification and Fix Level |
Copy Mode Setting: | VCLOPCPY - Operation Copy Mode |
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).