GPA Manual

Running GPA

Guardian Performance Analyzer (GPA) Manual—135081

2-3

Determining the Analysis Period

The object of this step is to examine the data collected with Measure in the preceding

step to determine the most appropriate period of system use for GPA to analyze. Keep in

mind the following:

•

The analysis period should include the time of heaviest use, but should not be so

narrow as to result in tuning the system for just a sharp peak. For a system in

consistent daily use for 24 hours or some other large part of the day, the busiest

three-hour period is the most suitable for analysis.

•

The analysis period should be a minimum of one hour.

Creating the Structured Data Files for GPA

The purpose of this step is to create the three structured data files (CPU, PROCESS, and

DISC) that GPA will use for its analysis. You do this by using the Measure file handler

MEASFH.

Editing the GPA Text Statements

This is an optional step and is required only if you want to change the GPA text

statements (see GPA Analysis Statements

in Section 3, Description of GPA Reports) or

omit them from the GPA report entirely. Editing the text statements, contained in a file

named TUNEDATA, requires some care and in doing so, you should bear in mind the

following:

•

To edit the statements, use one of the Tandem editors: EDIT, TEDIT, or SEEDIT.

•

GPA inserts performance data and variable information in the text statements by

means of a keyword-and-code-character analysis. Therefore, to maintain the

integrity of this information, do not change any of the code characters. These

characters precede each statement paragraph and are sometimes also embedded in

the text as shown in Figure 2-2

•

Each statement paragraph is also preceded by a two-digit decimal number that

indicates the total number of lines in the paragraph, including blank lines

(Figure 2-2). If you change the number of lines in any paragraph, be sure to change

the corresponding number.

Note. If MEASCOM reports a mismatch, it probably occurred because the system on which

you are running GPA is not the one being analyzed. This problem can be solved by copying the

active MEASFH file on the system being analyzed to the Measure data subvolume. You can

then move the correct MEASFH along with the Measure data files to the other system.