

3. REPORTS › 3.2 Standard Analysis Reports › 3.2.2 System Software Malfunction Summary Report
3.2.2 System Software Malfunction Summary Report
The System Software Malfunction Summary Report provides an
overview of all system software failures that have occurred
during the reporting period by system identification (SYSID).
Software failure data is summarized by jobname, CSECT name,
recovery routine name, and the system and user completion
codes. The report also includes an indication of whether the
failure occurred in a module or job identified as being
critical to the installation, as specified during the CA MICS
generation and installation process. See Section 3.1.2 for
more information on this report, as well as an example of the
output generated.
REPORT FORMAT:
See Section 3.1.2 for an example of the output generated by
the System Software Malfunction Summary Report.
DATA SOURCE (file/time-span):
SRLSSM at the DETAIL time-span.
DATA ELEMENTS USED:
The data elements used for this report are:
___________________________________________________________
| | |
| FILE | DATA ELEMENTS |
|__________|_______________________________________________|
| | |
| SRLSSM | SSMJOB SSMCSECT SSMFRRTN SSMSCMPC SSMUCMPC |
| | SSMUCMPC SSMCMOD SSMFCT |
| | |
|__________|_______________________________________________|
REPORT DEFAULTS AND CONSIDERATIONS
The following table summarizes the keywords which may be used
for the System Software Malfunction Summary Report and gives
their default values.
A complete list of keywords and their descriptions can be
found in Section 3.2.9.
KEYWORD DEFAULT
--------------- --------------------
CURRENT aaa,bbb yesterday's date
TIMESPAN DETAIL DETAIL
CYCLES nn 2
DAYRANGE n 0
SYSID list all SYSIDs
CPUSER list all CPUSERs
JOBNAME list all JOBNAMEs
MODULE list all MODULEs
SCC list all SCCs
UCC list all UCCs
FAILURES nnn 1
EXCLUDE YES EXCLUDE NO
REPORT SFWSM -
----------------------------------------
Notes:
1. CURRENT may specify a single date or range of dates.
The default is to process data from yesterday only.
2. The only valid TIMESPAN value is DETAIL.
3. CYCLES may have any value, however, data will
only be used from the dates contained in the
period startdate to enddate
4. DAYRANGE may be used to establish a default
startdate that is different than the value
established by CURRENT. If DAYRANGE is used, it
will override the value specified in CURRENT. The
value of startdate will be set from the expression
enddate - DAYRANGE + 1
5. The keywords SYSID, CPUSER, JOBNAME, MODULE, SCC,
and UCC may be used to limit the data to be
selected.
6. If other keywords are used, they MAY AFFECT the
report. They are NOT ignored by the report.
Copyright © 2014 CA.
All rights reserved.
 
|
|