3. REPORTS › 3.2 Standard Analysis Reports › 3.2.9 Generating System Reliability Reports
3.2.9 Generating System Reliability Reports
This section describes the considerations in generating the
various System Reliability reports. The areas discussed are:
o Process Flow
o JCL Requirements
o Report Options
PROCESS FLOW
The System Reliability reports are created in a one step
process consisting of reading and processing user supplied
parameters and control statements, selecting, sorting, and
where required, summarizing the reliability data from one or
more cycles and files of the data base, and producing the
requested reports, tables, or charts.
During control statement processing, MACROs are built
containing logic to select the appropriate data from the
Reliability files. Based on the requested reports, SAS
%INCLUDE statements are generated to load and execute the
report logic.
JCL REQUIREMENTS
To execute the System Reliability reports, the MICSSHRx JCL
procedure is used, where 'i' is the single character
identifier for the CA MICS Data Base containing the SRL
files. This section describes the additional JCL required to
execute the reports.
Two additional DD statements must be used with the MICSSHRx
procedure, one to select the control statement processing
routine and the other to specify the parameters and control
statements for the reports.
Figure 3-10 shows a sample of the JCL used to execute the
reports. In the example, the control statements are included
in the submitted job. As an alternative, the control
statements could be stored in a library on direct access.
//jobname JOB ...
//S1 EXEC MICSSHRx
//MICS.SYSIN DD DSN=sharedprefix.MICS.SOURCE(SRLRPT00),
// DISP=SHR
//MICS.CTLIN DD *
... control statements ...
/*
Figure 3-10. Sample Report JCL
A detailed description of the allowable parameters and
control statements is provided in the following section.
REPORT OPTIONS
The System Reliability reports are controlled through the use
of keywords and parameters on control statements entered via
the CTLIN DD statement as shown in Figure 3-10. The general
rules for the syntax of the statements are:
1. Control statements are composed of keywords, value
parameters, and lists of values.
2. Each statement consists of a keyword value followed
by one or more values.
3. Columns 1-72 are scanned for input. Columns 73-80
are ignored.
4. Keywords may not be abbreviated.
5. Comments may not appear on the control statements.
Any statement with * as the first character will be
considered a comment and the statement will be
ignored.
6. A keyword value and its list must be completed on one
line. No continuation lines are allowed.
7. All keywords associated with a REPORT statement are
ANDed together, that is, all selection tests must be
met for data to be passed to the report routine.
8. The order of the keywords is not significant.
The following topics on the report options are discussed:
o Report Control Statements
o Report Keyword Syntax Specifications
o Usage and Examples
REPORT CONTROL STATEMENTS
The System Reliability reports and the data to be selected
and presented in the reports are controlled through the use
of parameters or control statements. No reports are
generated as part of the normal CA MICS update or processing
cycles. However, any report may be produced at any time by
executing the report generation routine.
The control statements allow you to select one or more
reports to be produced and to tailor or control the data used
in the reports. The control statement is:
REPORT rrrrrrrr
where rrrrrrr is the name of the report to be produced. If
no other parameters are specified, then report 'rrrrrrrr'
will be produced using the default values for that specific
report. The default values are described by report in the
sections entitled 'Report Defaults and Considerations'.
The keywords available and a brief description of each one is
listed in Figure 3-11.
KEYWORD DESCRIPTION
------------- -----------------------------------------
CURRENT specifies an ending date and possibly a
starting date for the current period to be
selected and reported
PREVIOUS specifies a starting date and an ending
date for the previous period to be selected
and reported
TIMESPAN specifies a CA MICS timespan value used to
select files from the data base.
CYCLES specifies the number of cycles or range of
cycles of data to be selected from the data
base.
DAYRANGE specifies the number of consecutive days of
data to be selected from the data base for
reports having comparative information.
SYSID specifies from 1 to 9 SYSIDs to be selected
and reported
CPUSER specifies from 1 to 9 CPU/processor serial
numbers to be selected and reported
JOBNAME specifies from 1 to 7 MVS job names to be
selected and reported
MODULE specifies from 1 to 7 module names to be
selected and reported
SCC specifies from 1 to 9 system completion
codes to be selected and reported
UCC specifies from 1 to 9 user completion codes
to be selected and reported
FAILURES specifies a value for the number of
software failures which must occur before
an entry appears on software reports.
ERRORS specifies a value for the number of
temporary errors which must occur before an
entry appears on hardware reports.
CLASS specifies from 1 to 7 classes of devices to
be selected and reported (e.g., DASD)
TYPE specifies from 1 to 7 types of devices to
be selected and reported (e.g., 3380)
ADDRESS specifies an address, a string, or range of
device addresses to be selected and
reported
VOLUME specifies from 1 to 9 volume serial numbers
to be selected and reported
EXCLUDE specifies that the control statements are
to be used to exclude data and not select
data to be reported
REPORT specifies from 1 to 7 names of reports to
be produced using the previous parameter or
control statements.
Figure 3-11. Report Options
REPORT KEYWORD SYNTAX SPECIFICATIONS
CURRENT enddate
CURRENT startdate,enddate
The CURRENT parameter specifies an ending date or where
required, a range of dates, for the current report processing
period. If a single date is present, it is assumed to be the
starting and ending date for the report. If two dates are
present, a date range will be assumed, of the form
startdate,enddate. The report programs will select data
based on the specified dates. If CURRENT is not specified,
the programs will use yesterday's date as the ending date and
will calculate a starting date, if one is required, based on
the requested report.
EXAMPLES: CURRENT 01MAR83
CURRENT 01JAN82,07JAN82
PREVIOUS enddate
PREVIOUS startdate,enddate
The PREVIOUS parameter specifies an ending date or where
required, a range of dates, for the previous report
processing period. If a single date is present, it is
assumed to be the starting and ending date for the period.
If two dates are present, a range of dates will be assumed,
in the format startdate,enddate. The report programs will
select data based on the specified dates. If PREVIOUS is not
specified, the programs will calculate a previous period
based on the values of CURRENT and DAYRANGE.
EXAMPLES: PREVIOUS 01MAR83
PREVIOUS 01JAN82,07JAN82
TIMESPAN tttttt
The TIMESPAN parameter specifies a CA MICS timespan value
used to select files from the data base. For the standard
reports, the value may be DETAIL or DAYS. If specified, only
data from the given time-span will be used. If the TIMESPAN
parameter is not specified, a default time-span will be used
based on the report(s) selected.
EXAMPLES: TIMESPAN DAYS
TIMESPAN DETAIL
CYCLES nn,nn
The CYCLES parameter specifies the number of cycles or range
of cycles of data to be selected from the CA MICS data base.
CYCLES may be specified as a single value or a pair of values
in the range 1 to 99. If a single value is specified, it is
assumed to be the number of cycles to select, beginning with
the first cycle (01) and continuing to the cycle specified.
If a pair of values is specified, the values are assumed to
be a range of cycles beginning with the first value
specified and ending with the second value specified. For a
pair of values, the second value must be greater than or
equal to the first value. This parameter is used with the
TIMESPAN parameter to choose an appropriate timespan and
number of cycles to process. If the parameter is not
specified, a default number will be used based on the
report(s) selected.
EXAMPLES: CYCLES 5
CYCLES 3,10
DAYRANGE nn
The DAYRANGE parameter specifies the number of consecutive
days of data to be selected from the CA MICS Data Base for
reports having comparative information. The value may be
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.
EXAMPLES: DAYRANGE 7
DAYRANGE 14
SYSID aaaa,bbbb,cccc,...
The SYSID parameter specifies up to 9 system IDs to be
selected and processed. Information for only the specified
system IDs will be processed. If no SYSID parameter is
present, information for all systems will be used.
EXAMPLES: SYSID X084
SYSID PRD1,PRD2,PRD3
CPUSER nnnnnn,nnnnnn,nnnnnn,...
The CPUSER parameter specifies up to 9 CPU/processor serial
numbers to be selected and processed. Information for only
the specified CPUs/processors will be used. If no CPUSER
parameter is present, 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 be
sure that all data is reported. This includes AP and MP
systems and systems of the IBM 308x class (dyadic
processors).
EXAMPLES: CPUSER 049604,044130
CPUSER 020081,220081
JOBNAME mmmmmmmm,mmmmmmm,...
The JOBNAME parameter specifies up to 7 MVS job names to be
selected and processed. Each name may be from 1 to 8
characters in length and should be a valid MVS job name.
Information for only the specified job name(s) will be used.
If no JOBNAME parameter is present, information for all jobs
will be used.
If a parameter ends with the character *, the preceding
characters are assumed to be a prefix value. All job names
beginning with the prefix value will be selected and
processed. For example, the specification JOBNAME CSD* will
result in the selection of all job names beginning with the
characters CSD.
EXAMPLES: JOBNAME JES2,MSI*,NET
JOBNAME GRP4133
MODULE mmmmmmmm,mmmmmmmm,...
The MODULE parameter specifies up to 7 module names to be
selected and processed. Each name may be from 1 to 8
characters in length. Information for only the specified
module name(s) will be used. If no MODULE parameter is
present, information for all modules will be used.
If a parameter ends with the character *, the preceding
characters are assumed to be a prefix value. All modules
beginning with the prefix value will be selected and
processed. For example, the specification MODULE IEF* will
result in the selection of all modules beginning with the
characters IEF.
EXAMPLE: MODULE IKTIOM03,ILRTERMR
SCC hhh,hhh,hhh,...
The SCC parameter specifies up to 9 system completion codes
to be selected and processed. Each code is a 3 hexadecimal
character value, such as 0C4 or A03. Information for only
the specified system completion code(s) will be used. If no
SCC parameter is present, information for all system
completion codes will be used.
EXAMPLES: SCC 0C4,B37,E37
SCC 122,222,322,522
UCC hhh,hhh,hhh,...
The UCC parameter specifies up to 9 user completion codes to
be selected and processed. Each code is a 3 hexadecimal
character value, such as 200 or 800. Information for only
the specified user completion code(s) will be used. If no
UCC parameter is present, information for all user completion
codes will be used.
EXAMPLES: UCC 200,800
UCC 720
FAILURES nnn
The FAILURES parameter specifies the number of software
failures which must occur before an entry appears on the
software reports using this parameter. The value may be
between 1 and 365 and is used to drop report lines below a
given value. The specification FAILURES 25 indicates that
only software failures occurring 25 or more times are to
appear on the report.
EXAMPLE: FAILURES 15
ERRORS nnnn
The ERRORS parameter specifies the number of temporary errors
which must occur before an entry appears on the hardware
reports using this parameter. The value may be between 1 and
1000 and is used to drop report lines below a given value.
The specification ERRORS 128 indicates that only temporary
errors occurring 128 or more times are to appear on the
report.
EXAMPLE: ERRORS 100
CLASS cccccccc,cccccccc,...
The CLASS parameter specifies up to 7 device classes to be
selected and processed. The valid classes are DASD, TAPE,
UNIT-REC, and COMMGEAR. Information for only the specified
device class(es) will be used. If no CLASS parameter is
present, information for all device classes will be used.
EXAMPLES: CLASS DASD
CLASS TAPE,COMMGEAR
TYPE tttttttt,tttttttt,...
The TYPE parameter specifies up to 7 device types to be
selected and processed. Each device type is a 4 to 8 numeric
character identifier for a group of devices within a class of
devices, such as 3350 or 3380 within DASD devices.
Information for only the specified device type(s) will be
used. If no TYPE parameter is present, information for all
device types will be used.
EXAMPLES: TYPE 2400,3400
TYPE 3350,3380
ADDRESS aaa,aaa,aaa,...
The ADDRESS parameter specifies up to 7 device address
entries, where each entry may represent 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'. An entry of the form 'cuuu-cuuu'
represents all of the devices from the first address to the
second address. The address range is assumed to be within a
range of 16 addresses, that is, the first three hexadecimal
digits of both addresses must be the same. The range
03A2-03AC is a valid address range. The range 03A2-03BC is
not valid, since the first 3 digits of both addresses are not
the same. Information for only the specified address,
string, or range of addresses will be used. If no ADDRESS
parameter is present, information for all devices will be
used.
EXAMPLES: ADDRESS 0256,065X,075X
ADDRESS 0250-0259,0360,0365,0A80
VOLUME vvvvvv,vvvvvv,vvvvvv,...
The VOLUME parameter specifies up to 9 volumes (for magnetic
tape or direct access) to be selected and processed. Each
entry is the 6-character volume serial number of a magnetic
tape or direct access volume. Information for only the
specified volume(s) will be used. If no VOLUME parameter is
present, information for all volumes will be used.
If a parameter ends with the character *, the preceding
characters are assumed to be a prefix value. All volumes
beginning with the prefix value will be selected and
processed. For example, the specification VOLUME TSO* will
result in the selection of all volumes beginning with the
characters TSO.
EXAMPLES: VOLUME 795007,DSK906
VOLUME TSO805
EXCLUDE yes
The EXCLUDE parameter specifies that all of the previous
control statements are to be used to exclude data and not to
select data to be reported. The EXCLUDE parameter allows
data to be dropped from the standard report(s) for one or
more of the following keywords:
SYSID CPUSER JOBNAME MODULE
SCC UCC CLASS TYPE
ADDRESS VOLUME
If no EXCLUDE parameter is present, all of the specified
parameters will be used to select data to be included.
EXAMPLE: EXCLUDE YES
REPORT rrrrr,rrrrr,...
The REPORT parameter specifies the name of up to 7 reports or
report groups to produce using the previous parameter
statements or the report default values. The possible values
are:
SFWSM Software Malfunction Summary Report
MODTR Module Failure Trend Analysis Report
ABDTR Abend Trend Analysis Report
ALLSW Produce All Software Reports
RELSM Reliability Summary Report
EQPSM Equipment Reliability Summary Report
DEVSM Device Reliability Analysis Report
ALLHW Produce All Hardware Reports
MEDMT Magnetic Tape Media Reliability Report
MEDDA Direct Access Media Reliability Report
ALLME Produce All Media Reports
The same report may be specified more than one time, using
the default or specified parameters.
EXAMPLES: REPORT MODTR,DEVSM,MEDDA
REPORT ALLME
USAGE AND EXAMPLES
The control statements and parameters allow the reports to be
selected both individually and in groups and the data
contained in the reports to be included or excluded based on
values specified for various keywords. For doing studies of
the reliability data, the parameters allow you to specify
sets or subsets of information to process.
For standard reporting, a set of defaults may be established
and stored as a member of a partitioned data set. Report
requests using the default control statements will always
produce a standard series of reports, based on the
requirements of your installation. For other studies, the
control statements can be included as part of the instream
JCL.
EXAMPLE 1.
Produce an abend and module trend report for the production
systems only. The production systems have system IDs
(SYSIDs) of PRD1, PRD2, and PRD3. Use the standard report
defaults for all other parameters.
SYSID PRD1,PRD2,PRD3
REPORT ABDTR,MODTR
EXAMPLE 2.
Produce a system software malfunction summary report for the
online system (SYSID ONLN) and limit the report to those
modules failing 10 times or more.
SYSID ONLN
FAILURES 10
REPORT SFWSM
EXAMPLE 3.
Create a device reliability analysis report for the string of
3380 direct access devices at addresses 0250-025F.
CLASS DASD
TYPE 3380
ADDRESS 025X
REPORT DEVSM
EXAMPLE 4.
Print a media reliability report for any direct access volume
beginning with the characters TSO and having more than 250
temporary errors.
ERRORS 250
VOLUME TSO*
REPORT MEDDA
Copyright © 2014 CA.
All rights reserved.
|
|