These tips can help you troubleshoot SLCs.
- To prevent extraneous events being generated by the SLC service, define two of the following
items in the schedules associated with an SLC:
- Normal Start Range (NSR)
- Normal End Range (NER)
That is, if an SLC has a calendar schedule that specifies both an NSR and NER, do not also associate a duration schedule with the SLC. If an SLC has a duration schedule associated with it, and you want to associate a calendar schedule with it, the calendar schedule should specify either an NSR or an NER, but not both. Define only two items to avoid conflicts that can occur due to the inherent duration derived by taking the difference between the calendar schedule NSR and NER values and the explicit duration specified in the duration schedule.
- For workflow SLCs with a single milestone, specify only a duration time for the milestone. Do not specify any values for the time range, regardless of the schedule type that is associated at the workflow level. When only one milestone is associated with the workflow SLC, specifying values for the time range does not produce any useful events or alerts.
- It is a best practice to only use duration values for milestones that correspond to the maximum length of the workflow, regardless of the number of milestones in a workflow SLC.
- Review the predefined rules that are included with IBM® Sterling Control Center Monitor for SLC event types, and the actions that the rules specify. Ensure that the rules you want to be triggered are enabled and the actions that the rules specify are appropriate. Disable rules that watch for events that you consider unimportant.
For example, IBM Sterling Control Center Monitor has a predefined rule named Process Not Started Warn, which is triggered when an SLC event is generated at the start of the start range, NSRs, and specifies if an appropriate Process type event (Process started, or Process step started) does not transpire by that time. If you do not want to know that a Process or Process step has not started by NSRs, then disable the Process Not Started Warn rule. Otherwise, you can change the action that it refers to as no operation or change the action Alert Severity to no alert generated.