z/OS MVS Product Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


The software outage report

z/OS MVS Product Management
SA23-1391-00

The software outage report shows the hours in the reporting period when no SMF type 89 records were found. This report allows users to check for missing data. Data might be missed because of:
  • A system crash or shutdown
  • Termination of SMF recording
  • Suppression of SMF type 89 record recording
  • Omission of some system data in the input files. This case can be corrected by rerunning the usage report program with the correct data.
The outage and statistics reports are generated once for each calendar month using both the history file and any new SMF input datasets.
Note: The Software Outage Report does not identify when all the data for a system is missed. To catch that situation, review the Software Summary Report and check for the absence of a system.
Figure 1. Software outage report
1                                   Measured Usage and S/390 Usage Pricing Charges                                    PAGE         1
 IFAURP 4.1.0                                   Software Outage Report                                              23 FEBRUARY 2010
 BETA SYSTEMS
 11 LOOKING GLASS
 FANTASY ISL, RI 12345
0Reporting Period:   1 APRIL 2008 -  4 APRIL 2008 (4 DAYS)
0 Type-Serial: 2094-604FE                                  LPAR ID:  1   MACHINE: 002094-0000000604FE        SYSPLEX ID:BETA
 MIDN |
  1AM |
  2AM |
  3AM |
  4AM |
  5AM |              *
  6AM |              *
  7AM |              *
  8AM |              *
  9AM |              *
 10AM |              *
 11AM |              *
 NOON |              *
  1PM |              *               *
  2PM |  *           *               *
  3PM |              *
  4PM |              *
  5PM |              *
  6PM |              *
  7PM |              *
  8PM |              *
  9PM |              *
 10PM |
 11PM |
 ----------------------------------------------------------------------------------------------------------------------------------
 DAY  |  01  02  03  04  05  06  07  08  09  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30
 MONTH| APR                                                     APR                                                         APR
 ----------------------------------------------------------------------------------------------------------------------------------
  MH     22  22  22  22  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24  24
0 Footnote:  MH stands for "Missing Hours".
0            *  - Record not found.
             .  - Record not found, not expected.
             B  - Invalid record found.
Table 1. Fields in the software outage report
Field heading Definition
Customer information The customer name, number, and address, obtained from the control statements.
Reporting Period The beginning and ending dates, inclusive, of the period covered by this report, and the number of days this period represents.
Processor Type-Serial, LPAR ID, Cluster, or Machine Serial, and SYSPLEX ID The processor type and serial, the logical partition identifier (if any), the machine type and serial, as obtained from the SMF type 89 record. The sysplex identifier, if any, is obtained from the SYSPLEX control statement. PR/SM™ Note: When a cluster is running in LPAR mode, the report shows, for each processor in the cluster, only the last 4 characters of the serial number, preceded by a period (such as .0111).
Midn, 1AM, etc. A row in the table represents an hour that begins at midnight, one o'clock a.m., etc.
Day and Month A column in the table represents a day within the reporting period

At the intersection of an hour and a day and month, an asterisk appears if there were no SMF type 89 records for that hour in the input files. A ‘B’ indicates an invalid SMF type 89 record was found for this interval.

MH The total number of hours that no records were found for each day in the reporting period.
* The record was not found
. The record was not found and not expected
B An invalid record was found

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014