Rules can fail to work as expected for many reasons. Working is defined here as being triggered by the conditions under which a rule is expected to be triggered.
Here are some examples of why a rule might not be triggered as expected:
- A rule will not be triggered if the wrong Event Type is selected even though all of the other parameters are correct.
- A rule will not be triggered if no events matching its parameters have been generated.
- A rule will not be triggered even if an event matches its parameters if the event occurred outside of the schedule associated with the rule.
- A rule will not be triggered if the matching event has already triggered a rule that appears higher in the list.
- A rule must be enabled in order to be triggered.
- Back-level versions of managed servers, that is, managed servers not on current maintenance, may not generate statistics records, or statistics records with the needed information, for the events constructed by IBM® Sterling Control Center Monitor to have the information needed to trigger the rule.
- Process events (Process Started, Process Step Started, Process Step Ended, and Process Ended)
are all generated at the same time by IBM Sterling Control Center
Monitor for Sterling Connect:Enterprise® for z/OS®, Sterling Connect:Enterprise for UNIX, and most native FTP
When you write linked rules for process events of these server types, be aware that only the file transfer ending event is seen by IBM Sterling Control Center Monitor.