3. REPORTS › 3.1 MICF Inquiries › 3.1.9 Description of Run-time Options
3.1.9 Description of Run-time Options
The System Reliability Analyzer Option's Standard Analysis
Reports are controlled by MICF run-time options. After you
have selected an inquiry for execution, you are presented
with one or more screens of execution-time override options.
While most of these values are optional or use default
values, you can use them to tailor the data that appears on
the final reports.
This section describes each override. The function and
syntax of each option is described and examples are provided.
The general format of each override option is shown in the
example below:
Enter the CPU serial numbers to be reported or leave
blank to report all.
____________________________-____________________________
The text describes the function of the option and the syntax
of the two operands to be entered. In this example, the
option can be used to report only on selected CPU serial
numbers. Defaults are provided where applicable.
MICF lets you specify default output line and page sizes. If
you choose a line size less than 132, ensure that the value
you specify is large enough to accommodate the heading and
title lines that appear on each page.
MICF page size defaults (the number of lines per page) cannot
be changed. If you choose a page size less than 23, the
value is forced to 23.
For each of the execution-time override options described on
the following pages, note that some options apply to all
inquiries while others apply to one or two specific
inquiries.
Enter one or more database IDs for the databases you want to
process.
Function: Specify the CA MICS Unit database ID (DBID)
from which the data for this report should be
extracted. The value coded must specify a
unit containing the SRL information area. You
can enter a question mark (?) to obtain a list
of the valid units for your installation.
Check with your CA MICS Administrator if you
have further questions or problems.
Usage: Required.
Operand 1: Specify one or more 1-character Unit database
IDs (DBID) to use to obtain data for this
report. The default value can be specified as
a MICF option.
Operand 2: Not used.
Example: Run a report using data from the San Francisco
office. Data from that office resides in Unit
database ID (DBID) S.
Entry: S
Enter a range of CA MICS File Cycles to be processed.
Function: Specify the cycles of CA MICS SRL data to use
as input to this report. Cycle 01 of a
CA MICS file at the DAYS timespan represents
yesterday's processing, while cycle 02
represents processing from two days ago, and
so forth.
Usage: Required.
Operand 1: Specify a numeric cycle number 01 through 99
to be used as the beginning cycle number to
include in this report. The default value can
be specified as a MICF option.
Operand 2: Specify a numeric cycle number 01 through 99
to be used as the ending cycle number to
include in this report. If this is not
specified, only a single cycle (the beginning
cycle) is used.
Example: Run a report using SRL data starting with
cycle 01 and ending with cycle 05.
Entry: 01 - 05
Enter the SYSID(s) to be reported on or leave blank to report
all.
Function: Lets you include or exclude SRL information
based on the System Identifier. See CA MICS
data dictionary element SYSID for more
information.
Usage: Optional.
Operand 1: Specify up to 9 SYSIDs on which to report.
Information for only the specified
SYSIDs is processed. If a SYSID
is not specified, information for all
systems is used.
Operand 2: Continuation of Operand 1.
Example: Include information from System Identifier
PROD and TEST.
Entry: PROD TEST
Enter ending date to be reported for current period. (e.g.
01JUL08).
Function: Specify the ending date for the current
report processing period.
Usage: Optional.
Operand 1: Specify an ending date in the form ddmonyy.
If this option is not specified, the inquiry
uses yesterday's date as the ending date.
Operand 2: Not used.
Example: Include information from August 1st, 2008.
Entry: 01AUG08
Enter date ranges to be reported for current period. (e.g.
01JUL08).
Function: Specify a range of dates for the current
report processing period. If a single date is
present, it is used as the starting and ending
date for the report. If two dates are
present, the report programs select data based
on the specified dates, where the first date
is the start date and the second date is the
end date. If left blank, the inquiry uses
yesterday's date as the ending date and
calculates a starting date, if one is
required, based on the requested report.
Usage: Optional.
Operand 1: Specify a starting date in the form ddmonyy.
Operand 2: Specify an ending date in the form ddmonyy.
Example: Include information from August 1st through
the 7th, 2008.
Entry: 01AUG08 - 07AUG08
Specify number of consecutive days of data to be selected
(DAYRANGE).
Function: Specify the number of consecutive days of data
to be selected from the CA MICS database.
The value ranges from 1 to 99. This parameter
is used to set a default number of previous
days to select for reports having a current
and previous period. For example, the
specification DAYRANGE 14 would set a default
of 14 days for reports using comparisons. If
the parameter is not specified, a default
number will be used based on the report(s)
selected.
Usage: Optional.
Operand 1: Specify the number of days.
Operand 2: Not used.
Example: Report on 10 days of data.
Entry: 10
Enter SELECT or EXCLUDE for options below.
Function: Indicates that the run time options following
this option are used to SELECT data meeting
the criteria or to EXCLUDE data meeting the
criteria.
Usage: Optional.
Operand 1: Specify SELECT or EXCLUDE. The default is
SELECT.
Operand 2: Not used.
Example: Exclude data based on the options following
this run time option.
Entry: EXCLUDE
Enter the CPU serial numbers to be reported or leave blank to
report all.
Function: Lets you specify up to 9 CPU/processor serial
numbers on which to report. If this option is
not specified, information for all systems
will be used. NOTE that for processors having
more than 1 serial number, all of the serial
numbers must be specified to ensure that all
data is reported. This includes AP and MP
systems and systems of the IBM 308x class
(dyadic processors).
Usage: Optional.
Operand 1: Specify the CPU serial numbers separated by
blanks.
Operand 2: Continuation of Operand 1.
Example: Report on the CPUs whose serial numbers are
070216 and 170216.
Entry: 070216 170216
Enter date ranges to be reported for previous period. (e.g.
01JUL91)
Function: Specify an ending date or, where required, a
range of dates for the previous report
processing period. If a single date is
present, it is used as the starting and ending
date for the period. If two dates are
present, the inquiry selects data based on the
specified dates, where the first date is the
start of the period and the second date is the
end of the period. If this option is not
specified, the inquiry calculates a previous
period based on the values of the Current
Period and DAYRANGE options.
Usage: Optional.
Operand 1: Specify a starting date in the form ddmonyy.
Operand 2: Specify an ending date in the form ddmonyy.
Example: Include information from August 1st through
7th, 2008.
Entry: 01AUG08 - 07AUG08
Specify num of software failures that must occur before
entry is reported.
Function: Specify the number of software failures
that must occur before an entry appears on
the software reports. Valid values range from
1 through 365 and are used to exclude data
that does not meet the given value. The
specification FAILURES 25 indicates that only
software failures occurring 25 or more times
will appear on the report.
Usage: Optional.
Operand 1: Specify a number between 1 and 365.
Operand 2: Not used
Example: Produce report only if software failures
occurred 15 or more times.
Entry: 15
Enter the load module names to be reported or leave blank
to report all.
Function: Specify up to 7 module names for reporting.
Each name ranges from 1 to 8 characters in
length. Information for only the specified
module names is reported. If this option is
not specified, information for all modules is
used.
If a specification ends with an asterisk (*),
the preceding characters are assumed to be a
prefix value. All modules beginning with the
prefix value are included in the report. For
example, the specification IEF* will result
in the selection of all modules beginning with
the characters IEF.
Usage: Optional.
Operand 1: Specify up to 7 module names on which to
report.
Operand 2: Continuation of Operand 1.
Example: Report on all modules that start with IEF and
on a module called ILRTEMR.
Entry: IEF* ILRTEMR
Enter JOBNAME(s) to be reported or leave blank to report
all JOBNAMEs.
Function: Lets you specify up to 7 job names on which to
report. Each name may be from 1 to 8
characters in length and should be a valid job
name. Information for only the specified job
names will be reported. If this option is not
specified, information for all jobs is used.
If a parameter ends with an asterisk (*), the
preceding characters are used as a prefix
value. All job names beginning with the
prefix value are selected and processed. For
example, specifying CSD* results in selecting
all job names beginning with the characters
CSD.
Usage: Optional.
Operand 1: Specify up to 7 job names on which to report,
separated by blanks.
Operand 2: Continuation of Operand 1.
Example: Report on all job names that start with MSI
and DSI.
Entry: MSI* DSI*
Specify System ABEND code(s) to be reported or leave blank to
report all.
Function: Specify up to 9 system completion codes on
which to report. Each code is a 3 hexadecimal
character value, such as 0C4 or A03.
Information for only the specified system
completion codes is used. If this option is
not specified, information for all system
completion codes is used.
Usage: Optional.
Operand 1: Specify up to 9 system completion codes on
which to report, separated by blanks.
Operand 2: Continuation of Operand 1.
Example: Report on all 222 and 322 abends that
occurred.
Entry: 222 322
Enter DETAIL or DAYS for the timespan to be reported.
Function: Specify the timespan on which you want to
report. Only those inquiries that can report
against multiple timespans have this option.
If nothing is specified, the default displayed
will be used.
Usage: Optional.
Operand 1: Specify either DETAIL or DAYS.
Operand 2: Not used.
Example: Use the DETAIL timespan for the inquiry.
Entry: DETAIL
Enter num. of temporary errors that must occur before entry
is reported.
Function: Specify the number of temporary errors that
must occur before an entry appears on the
hardware reports. Valid values range from 1
through 1000 and are used to exclude data that
does not meet the given value. The
specification ERRORS 128 indicates that only
temporary errors occurring 128 or more times
will appear on the report.
Usage: Optional.
Operand 1: Specify a value between 1 and 1000.
Operand 2: Not used.
Example: Write the entry only if the number of
temporary errors is 100 or greater.
Entry: 100
Enter Device classes to be reported or leave blank to report
all classes.
Function: Specify the device classes on which to report.
The valid classes are DASD, TAPE, UNIT-REC,
and COMMGEAR. Information for only the
specified device classes will be used. The
default is to report on all device classes.
Usage: Optional.
Operand 1: Specify one or more of the following values:
DASD TAPE UNIT-REC and COMMGEAR.
Operand 2: Not used.
Example: Report on DASD only.
Entry: DASD
Enter device type(s) to be reported. Blank to report all
device types.
Function: Specify up to 7 device types on which to
report. Each device type is a 4- to 8-digit
identifier for a group of devices within a
class of devices, such as 3380 or 3390 within
DASD devices. Information for only the
specified device types is used. If this option
is not specified, all device types are
reported.
Usage: Optional.
Operand 1: Specify up to 7 device types to be reported
on.
Operand 2: Not used.
Example: Report on 3390 DASD devices only.
Entry: 3390
Enter the address(es) to be reported on or leave blank to
report all.
Function: Specify up to 7 device address entries, where
each entry represents an address, a string of
addresses, or an address range. An entry of
the form 'cuuu' represents a single device at
the channel and unit address given by 'cuuu'.
An entry of the form 'cuuX' represents the
string of 16 devices attached to channel 'c'
and control unit 'u'. If this option is not
specified, then all devices are reported.
Usage: Optional.
Operand 1: Specify up to 7 device address entries.
Operand 2: Not used.
Example: Report on all devices starting with 03F.
Entry: 03FX
Enter the volume(s) to be reported or leave blank to report
all volumes.
Function: Specify up to 9 volumes (for magnetic tape or
direct access) on which to report. Each entry
is the 6-character volume serial number of a
magnetic tape or direct access volume.
Information for only the specified volumes is
used. If this option is not specified,
information for all volumes is reported.
If a parameter ends with an asterisk (*), the
preceding characters are assumed to be a
prefix value. All volumes beginning with the
prefix value are selected and processed.
For example, specifying TSO* results in
selecting all volumes beginning with the
characters TSO.
Usage: Optional.
Operand 1: Specify up to 9 Volume Serial numbers
separated by a blank.
Operand 2: Continuation of Operand 1.
Example: Report on all Volumes starting with TSO.
Entry: TSO*
Copyright © 2014 CA.
All rights reserved.
|
|