Siemens SM2 monitoring system 用户手册
U3585-J-Z125-8-76
29
SM2 monitoring program
Efficient DP system usage
Because of the volume of data generated, it does not make sense to copy all data record
types into the master SM2 output file. SM2U1 can be used to suppress certain data records
when updating the master SM2 output file.
types into the master SM2 output file. SM2U1 can be used to suppress certain data records
when updating the master SM2 output file.
To investigate delays when handling special load requirements, you will need further infor-
mation in addition to the system utilization data described above. To begin with, the
monitoring program PERIODIC-TASK or TASK can be used to select a task. The DISK-FILE
monitoring program can be used for overloaded disks to determine the files accessed most
frequently. It is not possible to list general guidelines for the additional selection of
monitoring programs. For further information, please refer to the “Performance Handbook”
[5].
mation in addition to the system utilization data described above. To begin with, the
monitoring program PERIODIC-TASK or TASK can be used to select a task. The DISK-FILE
monitoring program can be used for overloaded disks to determine the files accessed most
frequently. It is not possible to list general guidelines for the additional selection of
monitoring programs. For further information, please refer to the “Performance Handbook”
[5].
2.13 Basic procedure for ensuring efficient DP system usage
To minimize performance analysis problems, the following procedure should be adhered to:
●
Define the performance expectations (see page 25).
●
Check the extent to which performance expectations are satisfied once productive
operation has begun. This involves carrying out a “basis” test.
operation has begun. This involves carrying out a “basis” test.
●
If some performance expectations are not satisfied, check whether these are system-
oriented or user-oriented.
oriented or user-oriented.
●
Check for errors in the system setup.
●
Carry out a bottleneck analysis (see the section “Automatic performance analysis” in
the chapter “SM2R1 analysis routine” and the description of the START-AUTOMATIC-
ANALYSIS statement in Volume 2 of the SM2 manual [21]).
Concentrate on those bottlenecks whose elimination promises the greatest perfor-
mance improvement.
the chapter “SM2R1 analysis routine” and the description of the START-AUTOMATIC-
ANALYSIS statement in Volume 2 of the SM2 manual [21]).
Concentrate on those bottlenecks whose elimination promises the greatest perfor-
mance improvement.
●
After eliminating the detected bottlenecks, repeat the bottleneck analysis. Many bottle-
necks remain hidden until after some kind of intervention.
necks remain hidden until after some kind of intervention.
●
Monitor the system at regular intervals (see page 27) to detect saturation symptoms in
the main resources (due to increasing loads) and to avoid critical system conditions.
the main resources (due to increasing loads) and to avoid critical system conditions.
The procedure is described in detail in the “Performance Handbook” [5], which also explains
how to interpret the results.
how to interpret the results.