OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-4
What Performance Indicators to Monitor
•
Performance statistics
You can determine the amount of data sent and received by using the SCF STATS
command. (Use the SCF STATS command to also look at TLAM/PAM port
statistics; the value of undelivered AG SDUs might be an indication of an improper
configuration.) You can determine response time using response time monitors, or
by manually clocking responses at the terminals. Measure can be used to determine
utilizations of CPUs, disks, processes, and more. ViewSys can be used to obtain a
dynamic picture of the activities in the system.
•
Data sent and received over communications lines
You can determine the content of the data sent and received over the
communications lines by using a line monitor. The SCF TRACE command is not
recommended for this purpose because it can reduce the throughput of the entire
system. In addition, data is truncated if the data frames are larger than the trace
frames.
•
Interaction between the user application and a TSP process
The SCF TRACE command provides the ability to capture information on data
exchanged between the user application and a TSP process. It records information
on the procedure calls made. Although the SCF TRACE command can reduce the
throughput of the entire system, it is the best way of obtaining this type of
information. You can minimize the effect of TRACE on throughput by narrowing
the items you trace and by running the trace only for a short period of time.
Performance Warning Signs
There are a number of general warning signs that you should be aware of. They include
the following:
•
Excessive response times
•
Error condition reports
•
CPU, disk, and line queuing delays
User complaints are often good indicators of poor response time. However, you should
be aware that response time is a very subjective thing for most users. Accurate
measurement is necessary to ensure that complaints about poor response time are
justified.
Utilization of hardware devices and communications lines should be kept at values that
do not cause excessive queuing delays, which can cause excessive response times. You
can obtain utilization and queuing delay information using Measure and ViewSys. Line
utilization can be partly obtained using Measure and the SCF STATS command to
determine how much data was sent over the line. A more accurate method is to use a
response time monitor, which provides this type of information as well as the average
response times for the lines. Where line speeds are relatively slow, it may be necessary
to keep the utilization correspondingly low to avoid long queuing delays.
You can also examine the various SCF counters, file-system errors reported, and EMS
events generated to help determine causes of subsystem performance problems.