1

Determine that the current day, date, and time displayed on the first line of the System Overview Display (1.1) is correct.

2

Determine the CPU type and serial numbers from the display. Verify that this information agrees with the data center’s billing information.

3

Determine if the z/OS release shown in the display is reasonably current.

4

Verify from the display that the job entry subsystem (JES) listed in the Computer System Profile is correct.

5

The SMF ID identifies the machine that is generating the SMF records. Ensure that it is unique for a multiple CPU environment.

6

The JES CPU ID and JES node name (JES2) identify machines in a network job entry (NJE) multiple CPU network. Verify that these IDs are unique for your CPU.

7

The date and time of the last IPL from the display. Verify that the IPL was documented in the operator’s shift log report. If applicable, verify that the reason for the IPL was recorded in Technical Support change authorization records.

8

z/OS can be set up to require the operator to enter a reason for the IPL. Use the SMF Options Display (1.5.1) to see if the operator IPL reason prompt and response option was specified.

9

Request the computer operator’s console log sheet for the period of time immediately before and after the last IPL. Prepare a work paper to use with later displays that use IPL parameters.

10

Verify that Technical Support does performance tuning on an ongoing basis. They should monitor common service area (CSA and ECSA) levels carefully if they exceed 90 percent. In addition, the sizes of the below-the-line private area as well as the above-the-line private area are listed as well. While not particularly audit-worthy, changes in these values should nevertheless be noted as application problems and outages could result if the private area storage size were reduced.

Note: We recommend that you evaluate CSA levels several times per day to provide more accurate results.

11

The last line indicates how system performance is controlled. On most systems, an IBM component called the Workload Manager (WLM) is responsible for balancing system resources against the executing workload. For more information about these parameters, see the Technical Reference Guide.