3. REPORTS › 3.1 TLM Component Reports › 3.1.1 TLM MICF Inquiry Specification Panels

3.1.1 TLM MICF Inquiry Specification Panels

The rules for filling in fields on the panels are identical
for all Tape Library Management reports.

A sample inquiry specification panel for inquiry TAPLTA is
shown below.  Explanations for field choices follow.

+-------------------------------------------------------------------------------+
| -------------------  CA MICS Tape Library Management Inquiry  --------------- |
| Command ===>                                                                  |
|                                                                               |
| Composing Inquiry:  TAPLTA - Tape Data Set Summary Report                     |
| Database ===> _                                                               |
| Cycle(s) ===> __ - __                                                         |
| Timespan ===> DAYS__ (DAYS)                                                   |
| Data Selection:                                                               |
|                     dd mmm yy   dd mmm yy   dd mmm yy   dd mmm yy             |
|   Date Ranges  ===> __ ___ __ - __ ___ __   __ ___ __ - __ ___ __             |
|   Tape Library Id (TAPELIB) ===> ____ ____ ____ ____ ____ ____                |
|   Volume Group (VOLGROUP)   ===> ________________ ________________            |
|                                  ________________ ________________            |
|                                                                               |
+-------------------------------------------------------------------------------+

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 CA MICS database units
from which files are read).  Duplicates are not allowed.  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.  The cycle of the
specified timespan of the CA 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 - DAYS is the only timespan supported.

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.

Tape Library (TAPELIB) - Optional.  No default.  A one to
four character value identifying a specific tape management
system.  Up to six tape management system IDs can be
specified.  If coded, the observations that are selected for
reporting are limited to those that match the specified
system IDs.

Volume Group (VOLGROUP) - Optional.  No default.  A one to
sixteen character value identifying a specific volume group.
Up to four volume groups can be specified.  If coded, the
observations that are selected for reporting are limited to
those that match the specified volume groups.