How do I fix SLCs?

SLCs can sometimes fail to work as expected.

There are many ways to set up SLCs incorrectly. Read the following topics to troubleshoot and correctly set up your SLCs.

SLC not enabled
It might be obvious, but sometimes SLCs do not work properly simply because they are not enabled. Always check SLCs that do not function correctly and make sure that they are enabled.
Match criteria
The primary reason SLCs fail to work as planned (assuming they are enabled) is that the data in the events that are supposed to trigger them does not exactly match the criteria specified.
A.M. versus P.M.
When constructing calendar schedules for use with SLCs, or specifying Normal Start Range (NSR) or Normal End Rage (NER) values for workflow SLC milestones, remember that you must specify times using the 24-hour clock.
Monitor windows
Another reason an SLC might not work as planned is that the events expected to trigger it occur outside its monitoring window.
Monitored servers
Back-level versions of monitored servers that are not on current maintenance may not generate statistics records correctly if they generate them at all.
Rules and actions
SLCs by themselves cause SLC events to be generated rather than alerts.
Milestone times
Values specified for Workflow SLC Milestone Normal Start Range and Normal End Range are offsets to the scheduled or actual start of the monitored workflow. These range values are durations, as opposed to clock times.
SLC order
Unlike standard SLCs, wildcard and workflow SLCs must be ordered the way IBM® Sterling Control Center Monitor rules are.
Time zones
SLCs will not work properly during the change from daylight saving time to standard time, and vice versa.

Parent topic: Troubleshooting SLCs