IBM SY44-5902-05 manual Interpreting Product Activity Log reports

Interpreting Product Activity Log reports

The data in the product activity log wraps. The newest log entries overlay the older ones. There is not an option to delete or clear data, but you can reduce the log sizes so that they wrap more quickly. Figure 48 is an example of a printed product activity log report. You can display the same information online by selecting various options and function keys.

Product Activity Log

Page

. . . :

2

Analysis Report

CUSTSYS1

05/05/91 08:00:00

System

Resource

Type/Mod

Serial

Physical Location

Ref Code

Date

Time

Class

Logical

Address

Name

Comp/Lib

Number

Log ID

Frame Card Device

--------

--------

--------

----

----------------------

----------

--------

---------

------

----- ---- ------

2661B000

05/05/94

08:07:13

PERM

1/ 1/0/

0-1/1/ 0/ 0/ 0/1

COM1

2661

001

00-010111

80000010

5

2661B000

05/05/94

08:08:13

PERM

1/ 1/0/

0-1/1/ 0/ 0/ 0/1

COM1

2661

001

00-010111

80000040

B900FDC0

05/05/94

08:09:13

SOFT

MS

LIC

80000080

Figure 48. Example Product Activity Log Printed Analysis Report

Some considerations when interpreting Product Activity Log reports

If you update an operating system release or apply a new operating system version to the system, the product activity log data might be cleared. (If you need the data in the product activity log, print it before you install the new operating system.)

Entries in the log might have been previously resolved (for example, machine check entries).

For more information on resource names, see “Resource name” on page 111.

For more information on interpreting disk storage log entries, see the error information sections under “Recovery Procedures” in the Repair and Parts information.

If the system cannot display a character in any of the following fields, it displays an asterisk (*) instead of that character:

Resource

Type

Model

Serial number

Volume ID

You can use the Log Analysis report to analyze problems that occur over a period of time. Look for error patterns such as multiple I/O processor errors that occur at the same time, or errors caused by the environment that occur at the same time of the day or week. Figure 49 on page 111 shows an example of entries that were logged in a 24-hour period. As you cycle through the different views of the Log Analysis Report screens, note that F11 shows variable text: Such as View Description, View Logical Address, View Physical Location, View Component Information, and View Resource Identification.

110Service Functions V5R2