System Management in Control
Certo Certius
more surely than sure
SMiC
Server management
Elapsed Time Monitoring settings
The data file SMiC_DATA: MONITORELAPSEDTIMES.DAT contains the following fields:

  1. The name of the batch job to be monitored.

  1. The file specification of the log file.

  1. The status of this monitoring.
Active:       the elapsed time of this batch job is actively monitored.
Notactive: the elapsed time of this batch job is not monitored.

  1. Options.
The elapsed time monitoring works in the standard configuration on a daily basis. This is great for batch jobs that run several times a week and then have similar elapsed times. For batch jobs that run several times a week but have different elapsed times on the different days of the week, this is less suitable. The Weekday option is available for this. The elapsed times of batch jobs on the same day of the week are then monitored and saved.

  1. Minimum guard threshold.
If the elapsed time of the batch job falls below this value, this measurement is not included in the historical data file. This is to prevent contamination with elapsed times for jobs that have clearly not been successful.

  1. Maximum guard threshold.
The maximum elapsed time threshold has two functions:
The warning limit is calculated using the average elapsed time and the maximum guard threshold.
If the elapsed time of the batch job exceeds this value, this measurement is not included in the historical data file. This is to prevent contamination with elapsed times for jobs that have clearly not been successful.