Monitor windows

Another reason an SLC might not work as planned is that the events expected to trigger it occur outside its monitoring window.

In addition to the schedules associated with SLCs, SLC criteria include Start and End Window Tolerance values, which might range from zero to 24 hours.

Start and end events for the monitored process or file transfer can occur outside the monitoring window of the SLC. When these events happen, it is as if the process or transfer never occurred. SLC events are generated as such.

Another problem related to monitoring windows can occur when SLCs have multiple calendar schedules. Those schedules can overlap due to the size of the start or end window tolerance value specified.

For example, you have an SLC with two schedules. One schedule specifies an NERs of 02:00 and an NERe of 02:15, and a second specifies an NERs of 03:00 and an NERe of 03:15. The SLC has a start and end window tolerance of one hour. The monitoring windows for the two SLC instances overlap and might cause unexpected events to be generated, as illustrated in the following figure:

The monitor window for the first SLC instance ranges from 1:00 to 3:15. The monitor window for the second SLC instance ranges from 2:00 to 4:15. If the first process that ought to trigger the SLC does not run at all, but the second process starts anytime between 2:00 and 3:15, rather than generating SLC events that indicate the first process did not run but the second process completed on time, the SLC events generated indicate that the first process completed late and the second process did not run.

In cases such as this one, consider setting a monitor tolerance value of zero hours. Adjust the SLC schedules as needed to avoid getting erroneous SLC events.