SM2 monitoring program

System monitoring

2.12 Using SM2 for system monitoring

Depending on the mode of monitored-data acquisition (frequency, scope), we must consider two different applications:

Trend monitoring (= long-term monitoring) for obtaining data for system capacity planning

Bottleneck analysis for locating and eliminating performance problems

Trend monitoring

The utilization data of the following resources is required in order to carry out long-term system capacity planning:

CPUs

channels

devices

main memory

Additional monitoring routines need not be activated.

It is advisable to use the following settings for monitoring periods:

Sampling cycle (SAMPLING-PERIOD):

1000 milliseconds

Monitoring cycle (OFFLINE-PERIOD):

5 minutes

Analysis subinterval

1 hour

The monitoring period should cover the entire period from SYSTEM READY through to SHUTDOWN. If output of the online screen report takes too long during the session, you can shorten the online monitoring cycle.

Monitoring times are set using the MODIFY-MEASUREMENT-PERIODS statement.

It is a good idea to create a new SM2 output file every day (OPEN-LOG-FILE / CLOSE- LOG-FILE statements). The SM2U1 routine can be used to combine (and split) daily SM2 output files to create one large file, known as the master SM2 output file. The daily SM2 output files must be added to the master SM2 output file in chronological order.

U3585-J-Z125-8-76

27

Page 27
Image 27
Siemens U3585-J-Z125-8-76 1, SM2 monitoring system Using SM2 for system monitoring, System monitoring, Trend monitoring