Examples of IMFEXEC ALERT escalation

The ALERT in this example will be upgraded from Informational to Critical priority over five time intervals.

The following list describes the properties of the ALERT:

• The original priority of the ALERT is Informational (PRIORITY(info)).
• The ALERT’s priority will be upgraded ( Escalate(up)).
• The priority will be upgraded gradually over the intervals of 10 minutes, 20 minutes, 30 minutes, 30 minutes, and 40 minutes (Interval(10,20,30,30,40)).

• When the ALERT reaches the final priority level, the ALERT should be deleted

  ( Dispose(delete)).

REXX example:

CLIST example:

In this example, the INTERVAL() keyword has 5 parameters passed.  This indicates 5 points of escalation, with the last associated with the final disposition. When the EXEC that schedules this ALERT is scheduled, the ALERT’s original priority is Informational. The sequence is:

1. After 10 minutes (1), the priority automatically is upgraded from Informational to Warning.
2. The ALERT stays at the Warning priority for 20 minutes (2) and is upgraded to Minor.
3. The ALERT stays at Minor priority for 30 minutes (3) before being upgraded to Major.
4. It stays at Major priority for 30 minutes (4) before being upgraded to Critical.
5. After remaining at Critical for 40 minutes (5), the ALERT is deleted.

Example 2: Downgrading ALERT priority over two intervals

The ALERT in this example will be downgraded over two time intervals.

The following list describes the properties of the ALERT:

• The original priority of the ALERT is Minor (PRIORITY(minor)).
• The ALERT’s priority will be downgraded (Escalate(down) ).
• The priority will be downgraded over the intervals of 10 minutes and 20 minutes ( Interval(10,20)).
• When the ALERT reaches the final priority level, the ALERT should be deleted ( Dispose(delete)).

REXX EXEC example:

CLIST example:

When the EXEC that schedules this ALERT is scheduled, the ALERT’s original priority is Minor. After 10 minutes (1), the priority automatically is downgraded from Minor to Warning. The ALERT remains at the Warning priority for 20 minutes (2) and is deleted at the end of the interval.

The intervals in this example also can be validly coded as follows:

Example 3: Upgrading an ALERT and scheduling an escalation EXEC

The ALERT in this example will be upgraded over two time intervals and, at the end of the second interval, an escalation EXEC will be scheduled. The following list describes the properties of the ALERT:

• The original priority of the ALERT is Minor (PRIORITY(minor) ).
• The ALERT’s priority will be upgraded ( Escalate(up) ).
• The priority will be upgraded over the intervals of 10 minutes and 20 minutes ( Interval(10,20) ).
• When the ALERT reaches the final priority level, the ALERT should be kept until it is manually deleted ( Dispose(keep) ).
• When the ALERT completes its final interval, an EXEC named e100 with three parameters is scheduled ( Escexec('e100 p1 p2 p3') ).

REXX EXEC example:

CLIST example:

When the EXEC that schedules this ALERT is scheduled, the ALERT’s original priority is Minor. After 10 minutes (1), the priority automatically is upgraded from Minor to Major. The ALERT remains at the Major priority for 20 minutes (2) and the EXEC e100 with its three parameters is scheduled at the end of the interval. The ALERT remains at the Major priority until it is manually deleted.

Example 4: Skipping ALERT priorities during ALERT escalation

The ALERT in this example will be upgraded from Informational to Major while skipping the intermediate ALERT priorities. The following list describes the properties of the ALERT:

• The original priority of the ALERT is Informational (PRIORITY(info) ).
• The ALERT’s priority will be upgraded ( Escalate(up) ).

• The priority will be upgraded over the two intervals of 10 and 20 minutes.

  However, to skip ALERT priorities, you must specify an interval of zero minutes for each of the intervals you want to skip.

In this example, the ALERT will skip two priorities and change from Informational priority directly to Major after a 10-minute interval (Interval(10,0,0,20) ).

• When the ALERT reaches the final priority level, the ALERT should be kept until it is manually deleted ( Dispose(keep) ).
• When the ALERT completes its final interval of 20 minutes, an EXEC named e100 with three parameters is scheduled ( Escexec('e100 p1 p2 p3') ).

CLIST example:

When the EXEC that schedules this ALERT is scheduled, the ALERT’s original priority is Informational. After 10 minutes (1), the ALERT’s priority automatically is upgraded from Informational to Major. To skip the intermediate priorities, you must code zero minutes for both Warning and Minor priorities (2 and 3).

The ALERT remains at the Major priority for 20 minutes (4) and the EXEC e100 with its three parameters is scheduled at the end of the interval. The ALERT remains at the Major priority until it is manually deleted.

The intervals in this example also can be validly coded as follows:

Example 5: Showing the elapsed time for an escalated ALERT

The ALERT in this example will be upgraded from Minor to Major in one 10-minute interval. The following list describes the properties of the ALERT:

• The original priority of the ALERT is Minor (PRIORITY(minor) ).
• The ALERT’s priority will be upgraded (Escalate(up) ).
• The priority will be upgraded over one interval of 10 minutes (Interval(10)).
• When the ALERT reaches the final priority level, the ALERT should be deleted ( Dispose(delete) ).
• When the ALERT completes its final interval, an EXEC named e100 with three parameters is scheduled (Escexec('e100 p1 p2 p3')).

CLIST example:

The following example shows the life of the ALERT over time: