|
|
|
The Standard Analysis Reports are run in batch by coding the
unique control statements required for each report and then
submitting the appropriate JCL stream.
SYSTEM AVAILABILITY REPORT
The System Availability Report uses no control statements.
You can run the report by submitting the following JCL:
//jobname JOB .....
//S1 EXEC MICSSHRi <--- i is the data base proc ID
//SYSIN DD DSN=sharedprefix.MICS.SOURCE(SMFAVRPT),DISP=SHR
CONFIGURATION TRACE REPORT AND SYSTEM INCIDENT REPORT
Use the following JCL to submit the Configuration Trace
Report and the System Incident Report. To define the report
options, modify the SMFUOPTS member of prefix.MICS.PARMS,
which is specified by the USEROPTS DD statement.
//jobname JOB .....
//S1 EXEC MICSSHRi <--- i is the data base proc ID
//SYSIN DD DSN=sharedprefix.MICS.SOURCE(SMFOPRPT),DISP=SHR
//USEROPTS DD DSN=prefix.MICS.PARMS(SMFUOPTS),DISP=SHR
o Report Options
All report options are specified in SMFUOPTS. The
SMFUOPTS member must have at least a blank line
(default values are then used for the report options).
If the SMFUOPTS member is null (no lines) the report
generator will abend.
STARTDAY= DATE7. ddmmmyy Date to start the report
STARTHR= NUMBER nn Hour of start date
STARTDAY is all that is required to define the report
beginning. If STARTHR is omitted, an hour of zero is
used.
DEFAULT:
- If a report end time is specified using the
ENDDAY/ENDHR report options, the report begins at
the last IPL prior to the report end for each SYSID
in the OPSOPI file.
- If report end is not specified, the report begins
at the last IPL for each SYSID in the OPSOPI01
file.
ENDDAY= DATE7. ddmmmyy Date to end the report
ENDHR= NUMBER nn Hour of end date
ENDDAY is all that is required to define the report
end. If ENDHR is omitted, a value of 23 hours 59
minutes, 59 seconds is used. This means that
specifying a STARTDAY of 10JUN91 and an ENDDAY of
10JUN91 generates a report from 00:00:00 to 23:59:59
for 10JUN91.
ENDHR has 59 minutes and 59 seconds added to it.
This means that if you specify ENDHR=15, the report
will include all records through 15:59:59.
DEFAULT: The report end time defaults to the end of
data for each SYSID in the OPSOPI01/OPSCON01 files.
SYSTEM= $4. System to be reported
SYSTEM serves to limit the report. If SYSTEM is
specified, the report will exclude all other SYSIDs
in the OPSOPI file.
DEFAULT: The report generator reports on all SYSIDs
found in the OPSOPI01 file up to a limit of 999.
OPI= $1. System Incident Report? Y/N
OPI=Y generates the System Incident Report.
OPI=N suppresses the System Incident Report.
DEFAULT: Y - The report generator produces a
System Incident Report.
CON= $1. Configuration Trace? Y/N
CON=Y generates the Configuration Trace Report.
CON=N suppresses the Configuration Trace Report.
DEFAULT: Y - The report generator produces a
System Incident Report.
MODE= $8. Separate or combine the two
report types for each SYSID
SEPARATE/COMBINE
MODE is ignored unless both OPI and CON equal Y or
both OPI and CON are omitted (defaulting to Y).
MODE=COMBINE tells the report generator to combine
the Configuration Trace and System Incident data into
a single report for each SYSID.
MODE=SEPARATE tells the report generator to produce
separate Configuration Trace and System Incident
reports for each SYSID.
DEFAULT: SEPARATE - Separate reports are produced.
DEBUG= $1. Produce a diagnostics report?
Y/N
DEBUG=Y produces a separate diagnostics report for
for all SYSIDs found in the OPSOPI01 file. This
report helps you identify any discrepancies between
what you expected and what you received from the
report generator. It shows whether data could be
found in the OPSOPI01 and OPSCON01 files to generate
an Incident or Configuration report, and if not, why.
It also reports for both the OPSCON01 and OPSOPI01
files:
- Total records for each SYSID
- Number of records selected for reports
- Number of records rejected for reports
The diagnostics report is generated ahead of the
Configuration Trace and System Incident reports.
DEBUG=N suppresses the diagnostics report.
DEFAULT: Y - The diagnostic report is produced.
All SMFUOPTS are read by using the SAS "named input"
technique. For example, the statement INPUT
STARTDAY= is used to read in the STARTDAY. It should
be on the data card as STARTDAY=DDMMMYY. Use a /
to continue the report options on additional lines.
For example:
OPI=Y CON=Y STARTDAY=21JUN90 /
ENDDAY=23JUN90 ENDHR=12 /
MODE=SEPARATE DEBUG=Y
Running the report generator with the default values (a
blank line in member SMFUOPTS) results in a diagnostics
report on all SYSIDs encountered in the OPSOPI01 and
OPSCON01 files and a System Incident and Configuration
Trace report for each SYSID with an IPL record in the
OPSOPI01 file. The report will begin with the last IPL
event in the OPSOPI01 file for each SYSID.
o Diagnostic Report
The sample diagnostic report shown in Figure 3-4 was
generated using the following report options:
ENDDAY=26DEC90 ENDHR=8
The SYSID column shows each SYSID encountered in the
OPSOPI and OPSCON files.
The DATA FOR REPORT column value is either YES or
NO. If YES, reports were generated for the
SYSID. If NO, CA MICS was unable to find data for
the SYSID that met the report option specifications.
The REASON column is only populated if the DATA FOR
REPORT value is NO. Possible REASON values are:
SYSID REJECT - The SYSTEM= option specified a
particular SYSID to report on. All
other SYSIDs have SYSID REJECT in
the REASON column.
TIME REJECTED - Data could not be found in the OPSOPI
and/or OPSCON file(s) to meet the
STARTDAY= (STARTHR=) and/or ENDDAY=
(ENDHR=) options for the SYSID.
NO IPL RECORD - STARTDAY= was not specified and the
report generator was unable to find
an IPL event in the OPSOPI file that
occurred prior to the report end time
for the SYSID.
The REPORT START TIME and REPORT END TIME columns
define the timespan that encompasses the reports for
each SYSID. The REPORT START TIME will have a value of
'..... MISSING ....' if the REASON column has a value
of 'NO IPL RECORD.' Both REPORT START TIME and REPORT
END TIME will have values of '..... MISSING ....' if
the REASON column has a value of 'SYSID REJECT.'
The OPSCON FILE RECORDS section has three columns:
TOTAL - Total number of records in the OPSCON file
for the SYSID.
SELECT - Number of records selected for the
Configuration Trace Report.
REJECT - Number of records excluded from the
Configuration Trace Report.
The OPSOPI FILE RECORDS section has three columns:
TOTAL - Total number of records in the OPSOPI file
the SYSID.
SELECT - Number of records selected for the System
Incident Report.
REJECT - Number of records excluded from the System
Incident Report.
In cases where the DATA FOR REPORT column has a value
of NO, the value in the SELECT columns is NONE and
the value in the REJECT columns is ALL.
o MICSLOG
MICSLOG contains a detailed description of the report
options you specified and how they were interpreted by
the report generator. Any options you omitted are
presented with the default values. Examining MICSLOG
shows you exactly what the report generator intends to
produce. Any unacceptable options that are overridden
by the report generator are highlighted in MICSLOG.
o Overrides
If any report options are unacceptable, they are
overridden by the report generator. If this happens,
the first page of your System Incident and/or
Configuration Trace reports will be a banner telling
you that one or more report options were overridden.
You are referred to MICSLOG to see which options were
overridden, why, and how.
Overrides occur for the following report option errors:
- STARTDAY/(STARTHR) later than ENDDAY/(ENDHR)
- STARTHR specified without STARTDAY
Both of these conditions result in reports
generated as though you omitted STARTDAY and
STARTHR.
- ENDHR specified without ENDDAY
This results in reports generated as though you
omitted ENDDAY and ENDHR.
- CON=X where X is neither Y nor N
- OPI=X where X is neither Y nor N
If a character other than Y or N is used for
the CON or OPI option, the report generator uses
Y.
- CON=N and OPI=N
Running SMFOPRPT with both report types suppressed
results in both report types generated as though
you specified CON=Y and OPI=Y.
- DEBUG=X where X is not Y or N.
If a character other than Y or N is used for
the DEBUG option, the report generator uses Y.
- MODE=XXXXXXXX where XXXXXXXX is not SEPARATE or
COMBINE.
If MODE is not SEPARATE or COMBINE, the report
generator uses SEPARATE.
o Report Processing Errors
- If the SMFUOPTS member is empty, the report program
will abend with a U998, and MICSLOG will tell you to
add a blank line to the SMFUOPTS member.
- If more than 999 SYSIDs are found in the OPSOPI01
and OPSCON01 files, the report generator will abend
with A U998.
o Sample SMFUOPTS Member
STARTDAY=10JAN91 STARTHR=08 SYSTEM=PROD CON=Y OPI=Y /
ENDDAY=10JAN91 ENDHR=17 DEBUG=Y MODE=COMBINE
These report options will produce:
- Diagnostic report on all SYSIDs encountered in the
OPSOPI01 file.
- Combined System Incident and Configuration Trace
report for SYSID PROD from 08:00:00 January 10,
1991 through 5:59:59 pm on the same day.
+--------------------------------------------------------------------------------------------------------------------------------+ | | | CA | | CA MICS | | | | OPSOPI AND OPSCON FILE SUMMARY | | REPORT RECORD SELECTION/REJECTION ANALYSIS | | | +--------------------------------------------------------------------------------------------------------------------------------+ | | DATA | | REPORT | REPORT | OPSCON FILE RECORDS | OPSOPI FILE RECORDS | | | FOR | | START | END | | | | SYSID | REPORT | REASON | TIME | TIME | TOTAL SELECT REJECT | TOTAL SELECT REJECT | +-------+--------+----------------+--------------------+--------------------+--------+--------+--------+-------+--------+--------+ | SYSA | NO | NO IPL RECORD | ..... MISSING .... | 26DEC1990:08:59:59 | 256 | NONE | ALL | 98 | NONE | ALL | +-------+--------+----------------+--------------------+--------------------+--------+--------+--------+-------+--------+--------+ | SYSB | YES | | 26DEC1990:01:18:23 | 26DEC1990:08:59:59 | 807 | 157 | 650 | 210 | 14 | 196 | +-------+--------+----------------+--------------------+--------------------+--------+--------+--------+-------+--------+--------+ | SYSC | YES | | 26DEC1990:01:20:32 | 26DEC1990:08:59:59 | 1222 | 150 | 1072 | 224 | 14 | 210 | +-------+--------+----------------+--------------------+--------------------+--------+--------+--------+-------+--------+--------+
Figure 3-4. SMFOPRPT Diagnostic Report
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |