Setting up 'Ensure something does not take too long' Workflow SLC

Run through the quick checklist given below to create a Workflow SLC to ensure a Process does not take too long.

  1. Make sure SLC is Enabled is checked
  2. Make sure Generate notification if event has not occurred is checked
  3. Make sure Suppress Milestone Messages is checked
  4. Monitor Window Tolerances: Start and End should be set to 0 hours
  5. Specified SLC schedule should be a 'Duration schedule'
    1. Minimum duration should be set to '000:00:00' and
    2. Maximum duration is set to an appropriate value. For example, for four minutes, it would be 000:04:00.
  6. SLC parameter wise
    1. Milestone Times Relative to: Scheduled Start of Workflow SLC should be selected
    2. Set Concurrence count to 99. Up to 99 simultaneously running processes can be watched to ensure they do not exceed the duration specified.
    3. Correlator Source should not be set
    4. Jeopardy list should not be set
    5. Fire-Once list: Message ID should not be set
  7. Milestone wise, there should be only one milestone:
    1. Ensure its parameters include a Process name and server. To ensure a file transfer does not take too long, a server should be specified but instead of specifying a process name, specify parameters that match the transfer - which may or may not include a process name
    2. Its schedule should have Dmin set to 000:00:00 and Dmax set to the appropriate value. For example, for four minutes, it would be 000:04:00.

Rules for 'Ensure something does not take too long' workflow SLC

Two rules are needed for the "Make sure nothing runs too long" Workflow SLC.

The first rule is to watch for the SLC messages:

  • CSLC043E {1} did not end by dMax. SLC: {0}
This will have the following three parameters:
Key Operator Value
SLC Name Matches <SLC Name>
Message ID Matches CSLC043E
Event Type Matches SLC Notification

This rule needs an action associated with it. It could be an alert, an email, or an OS command.

The second rule is to catch all the other SLC events related to this SLC and ensure they don't trigger other, lower priority rules. It needs two parameters:

Key Operator Value
SLC Name Matches <SLC Name>
Event Type Matches SLC Notification

The second rule should be lower priority than the first one and both should be higher priority than any default/built in SLC rules.