Setting up SLCs for Max duration or Must End On time

Body

Two SLC's are needed and the associated Rules and Actions

SLC 1

Setting up SLCs for Max duration or Must End On time There are two types of SLCs needed (and two rules for each one)

1. Make sure things finish on time (SFG initiated work)

2. Make sure nothing runs too long (CD processes)

* For the "Make sure things finish on time" SLC, using a Workflow SLC:

* Make sure SLC is enabled is checked * Make sure "Generate notification if event has not occurred" is checked

* Make sure "Suppress Milestone Messages" is checked * Monitor Window Tolerances Start and End should be set to 0 hours

* The SLC's schedule should

1. Only have appropriate values set for Normal End Range (NER) start time and end time and the End Day should be set to Calendar Start Day.

2. Nothing should be specified for the Normal Start Range (NSR). And

3. Its Calendar Name should be set appropriately.

* SLC Parameter wise

1. Milestone times relative to scheduled start of Workflow SLC should be selected

2. Concurrence count should be set to 1 - unless multiple transfers that match the criteria are expected to run in which case this value should be set to the number expected to run - which is most likely 1

3. Correlator Source should not be set

4. Jeopardy list should not be set 5. Fire-Once list should not be set

* SLC Milestones - there should just be one milestone and for it

1. Its parameters should include the process name and server (not sure what all else but if what's there is not right things won't work correctly)

2. Its schedule should have a Dmin of 000:00:00 and a Dmax of whatever makes sense (000:04:00)

Two rules are needed for the "Make sure things finish on time" Workflow SLC.

The first rule is to watch for the SLC messages we "care" about:

* CSLC027E {1} did not start by NERe. SLC: {0}

* CSLC038E {1} did not end by NERe. SLC: {0}

NOTE! If both NSR and NER are specified, the first rule must also watch for CSLC228E Did not start before the end of the monitoring Window So it should have three keys.

* SLC Name, wildcard, *value* (where *value* is really a pattern that matches the SLC name - perhaps *DRF*?)

* Message ID, Reg Ex, CSLC038E|CSLC027E

* Event Type, matches, SLC Notification

This rule needs an appropriate action associated with it. One that should not cause a CC alert, but maybe send an email and run 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 keys.

* SLC Name, wildcard, *value*, and it's action should be set to "no operation"

* 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.

SLC 2

For the "Make sure nothing runs too long" SLC, using a Workflow SLC:

* Make sure SLC is enabled is checked

* Make sure "Generate notification if event has not occurred" is checked

* Make sure "Suppress Milestone Messages" is checked

* Monitor Window Tolerances Start and End should be set to 0 hours

* The specified SLC schedule should be a duration schedule

1. Minimum duration should be 000:00:00 and

2. Maximum duration should be 000:04:00.

* SLC Parameter wise

1. Milestone times relative to scheduled start of Workflow SLC should be selected

2. Concurrence count should be set to 99 - so 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 should not be set

* Milestones wise - there should just be one milestone and

1. Its parameters should include the process name and server (not sure what all else but if what's there is not right things won't work correctly)

2. Its schedule should have a Dmin of 000:00:00 and a Dmax of 000:04:00 Two rules are needed for the "Make sure nothing runs too long" Workflow SLC.

* The first rule is to watch for the SLC messages we "care" about:

1. CSLC043E {1} did not end by dMax. SLC: {0} It should have three keys.

1. SLC Name, wildcard, *value* (where *value* is really a pattern that matches the SLC name - perhaps *DRF*?)

2. Message ID, Matches, CSLC043E

3. Event Type, Matches, SLC Notification This rule needs an appropriate action associated with it. One that should not cause a CC alert, but maybe send an email and run 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 keys

1. SLC Name, wildcard, *value*, and it's action should be set to "no operation"

2. 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.