Examples of invalid coding with the IMFEXEC ALERT Interval parameter - Documentation for BMC AMI Ops Automation 8.3.01

Example 1

The interval keyword must contain at least one value.

"IMFEXEC ALERT key4 'test alert' Priority (info) Escalate(up) Interval(,)"

CLIST example:

IMFEXEC ALERT key4 'test alert' Priority (info) Escalate(up) Interval(,)

Example 2

You can only specify as many intervals as there are between an originating priority and the end priority.

"IMFEXEC ALERT key4 'testalert' Priority(major) Escalate(up) Interval(10,10,10)"

CLIST example:

IMFEXEC ALERT key4 'testalert' Priority(major) Escalate(up) Interval(10,10,10)

In this example, there is only one priority that a major ALERT can be upgraded to (Critical) and yet three intervals are specified.

Example 3

The interval keyword cannot have null values for intervals.

"IMFEXEC ALERT key4 'test alert' Priority(major) Escalate(up) Interval(,10,10)"

or

"IMFEXEC ALERT key4 'test alert' Priority(info) Escalate(up) Interval(,10,,20)"

CLIST example:

IMFEXEC ALERT key4 'test alert' Priority(major) Escalate(up) Interval(,10,10)

or

IMFEXEC ALERT key4 'test alert' Priority(info) Escalate(up) Interval(,10,,20)

Example 4

The intervals cannot have negative values.

"IMFEXEC ALERT key4 'test alert' Priority(info) Escalate(up) Interval(,10,-20)"

CLIST example:

IMFEXEC ALERT key4 'test alert' Priority(info) Escalate(up) Interval(,10,-20)