To be alerted if an hourly Process is not on time, create
24 calendar SLC schedules. Assign the 24 schedules to one standard
SLC.
About this task
Say that you have a Process named HOURLY that is supposed
to run every hour on Server REGULAR. How can you be alerted when it
fails to run?
The easiest way to handle this requirement is
to create 24 different calendar SLC schedules, one for each hour of
the day, and then assign all 24 of them to one standard SLC that specifies
appropriate matching criteria (a Server name of REGULAR and a Process
name of HOURLY) for its parameters.
Procedure
- Select and click the Create button to create a schedule.
- Create a schedule with NERs between midnight and 1:00 a.m.
The following table illustrates sample settings of an SLC schedule:
| Schedule Type |
Name |
Description |
Enabled |
| Calendar Schedule |
1AM |
NERs between midnight and 1AM |
Yes |
This schedule is for the first hour of the day.
- As our process is supposed to run 24 hours a day, 7 days
a week, set Calendar Name to the predefined
calendar called Daily.
- It is not necessary to set a start range. Simply setting
an end range that encompasses the hour within which the process is
supposed to run is sufficient. The following table illustrates sample
settings for the SCL Schedule Parameters:
| Calendar Name |
Time Zone |
End Day |
Start Time |
End Time |
| Daily |
(UTC - 06:00) Central Time (US & Canada) |
Calendar Start Day |
00:00 |
01:00 |
- Duplicate this SLC calendar schedule 23 times, modifying
the name and NER values appropriately.
| SLC Calendar Schedule Name |
NERs |
NERe |
| Midnight to 1AM |
00:00 |
01:00 |
| 1AM to 2AM |
01:00 |
02:00 |
| 2AM to 3AM |
02:00 |
03:00 |
| 3AM to 4AM |
03:00 |
04:00 |
| 4AM to 5AM |
04:00 |
05:00 |
| 5AM to 6AM |
05:00 |
06:00 |
| 6AM to 7AM |
06:00 |
07:00 |
| 7AM to 8AM |
07:00 |
08:00 |
| 8AM to 9AM |
08:00 |
09:00 |
| 9AM to 10AM |
09:00 |
10:00 |
| 10AM to 11AM |
10:00 |
11:00 |
| 11AM to 12PM |
11:00 |
12:00 |
| 12PM to 1PM |
12:00 |
13:00 |
| 1PM to 2PM |
13:00 |
14:00 |
| 2PM to 3PM |
14:00 |
15:00 |
| 3PM to 4PM |
15:00 |
16:00 |
| 4PM to 5PM |
16:00 |
17:00 |
| 5PM to 6PM |
17:00 |
18:00 |
| 6PM to 7PM |
18:00 |
19:00 |
| 7PM to 8PM |
19:00 |
20:00 |
| 8PM to 9PM |
20:00 |
21:00 |
| 9PM to 10PM |
21:00 |
22:00 |
| 10PM to 11PM |
22:00 |
23:00 |
| 11PM to Midnight |
23:00 |
24:00 |
- Since you know the exact process and server names (HOURLY
and REGULAR, in that order), use a standard SLC to generate events
when your process, HOURLY, does not run.
Set the Start
and End Window Tolerance values to 1 hour. These values allow the
hourly Process to start or end as much as one hour early or late and
still be counted as running. If you do not want any tolerance at all,
you might set the Start and End Window Tolerance values to zero hours.
Check Generate
Notification if Event Has Not Occurred to cause SLC events
to be generated when HOURLY does not run.
- Select the Server REGULAR.
- Select all 24 calendar SLC schedules you created.
- On the Processess/Batches pane, specify
the process name HOURLY.