HP 3000 Manuals HP 3000 Manuals
Introduction to SCOPE(XL)
The Performance Collection Software SCOPE(XL) program collects and
summarizes performance-measurement data on system-resource utilization,
terminal transaction rates, and terminal response times. It collects
data continuously to provide a complete record of system performance.
SCOPE(XL) collects this data from several sources in the HP 3000 system,
but it collects data mainly from the HP 3000 Measurement Interface (MI).
The PARM File
The Performance Collection Software PARM file is a standard flat,
unnumbered file used to customize your collection environment. The file
contains directives (instructions) that tell SCOPE(XL) to log specific
performance measurements.
When SCOPE(XL) starts, it looks for the PARM file in the logon group. To
enable you to start data collection immediately, Performance Collection
Software includes a default PARM file. We suggest that you use this file
until you gain experience with Performance Collection Software.
Performance Collection Software Log Files
SCOPE(XL) logs data into one to five log files, depending on the types of
information you want to collect:
* Global
Summarized measurements of the system-wide workload are logged to
the file LOGGLOB. One record is written to the log file every 5
minutes.
* Application
Summarized measurements of the processes in each user-defined
group (application) are logged to the file LOGAPPL once every 5
minutes. Users can define up to 15 applications on MPE V or 31
applications on MPE/iX. Performance Collection Software reserves
an application called OTHER for recording all processes not
included in other user-defined applications.
* Process
Summarized measurements of selected interesting processes are
logged to the file LOGPROC once every minute. A process can
become interesting (and be logged) when any of the following
occurs:
* The process is first created.
* The process terminates.
* An existing process exceeds user-defined thresholds for
CPU, disc, response time, or transaction rate.
* An existing process exceeds user-defined thresholds for
waiting on CPU, disc, or memory, or it is impeded.
* Disc space
Summarized measurements of disc space usage are logged to the
LOGDISC file once a day. This data is an instantaneous "snapshot"
of the condition of the system's disc space at the time the disc
was sampled and the peak value for transient or virtual disc space
for the day.
You can control the time of sampling using PARM-file parameters.
Disc space is measured for all nonprivate disc volumes (MPE V) and
for any private disc volumes (MPE/iX) that are mounted when daily
data collection occurs.
* Indexing information
Information used to rapidly access the log file data when
retrieving information is maintained in the LOGINDX file on MPE/iX
systems. On MPE V systems this information is kept in each of the
other log files so the LOGINDX file is not needed.
CAUTION Never modify the LOGINDX file!
You can control how much process history you keep on disc by adjusting
the size of each log file with the UTILITY program (see chapter 4). Data
collection does not stop when a log file is full. Instead, the oldest 25
percent of the records in the file are deleted to make room for new
records.
NOTE Use only the Performance Collection Software UTILITY program to
resize Performance Collection Software log files.
Starting and Stopping SCOPE(XL)
The SCOPE(XL) program resides in the SCOPE.SYS group on the HP 3000. The
file SCOPEJOB.SCOPE.SYS is a job stream that runs SCOPE(XL) as the user
MANAGER.SYS. If you use the SCOPEJOB file supplied, you must provide all
necessary passwords. If you choose to run SCOPE(XL) in any other way,
you must set user capabilities to at least the following:
IA, BA, ND, SF, SM
When to Start SCOPE(XL).
As mentioned in chapter 1, you should start SCOPE(XL) as soon as possible
on the system (or systems) to be measured. This will allow you to
develop a background of collected data for assessing performance.
When to Stop SCOPE(XL).
SCOPE(XL) should run continuously. Stop it only under the following
conditions:
* You are shutting down your system.
* You are updating the Performance Collection Software host software
to a new release.
* You are changing the size of a Performance Collection Software log
file.
* You are performing a system backup and want to include the
Performance Collection Software log files.
You can perform system backups with SCOPE(XL) running, but
Performance Collection Software log files will not be included in
the backup. (They are always "busy".) If you RELOAD your system,
you lose the contents of these log files unless they have been
backed up. See chapter 6 for different archiving strategies you
can use to save Performance Collection Software log files.
Data collection also stops if a system failure occurs or SCOPE(XL)
aborts. If this occurs, you must follow the restarting procedures
described below.
NOTE At the end of each interval, SCOPE(XL) flushes its file buffers to
disc and updates the MPE file label on its log files. Even if it
aborts abnormally, you will not lose more than the data collected
during the current interval (5 minutes for global and application
data and 1 minute for process data).
Restarting SCOPE(XL).
You have three options for restarting SCOPE(XL) after the system has been
down or the SCOPEJOB job is canceled:
* You can include the streaming of the file SCOPEJOB as part of
SYSSTART.PUB.SYS. It can be streamed each time the system comes
up.
* You can build a logon UDC for OPERATOR.SYS that includes the
streaming of SCOPEJOB.
* You can stream SCOPEJOB whenever you want to initiate SCOPE(XL) by
including it in your own startup procedure that is executed each
time the system comes up.
If you restart SCOPE(XL), Performance Collection Software continues to
use the same log files and appends new records to the end of the file.
If you restart SCOPE(XL) while it is already running, the second
SCOPE(XL) job will terminate immediately.