Alert Action III BEIM - panel fields

Journal Details

Specify that the ALERT details are written to the BBI Journal including

• the Rule Set and Rule ID that created the event
• the message text of the event
• the severity and Component Alias of the event
• the targets
• the Component Alias name

The default setting is for this field is NO (do not send messages to the BBI Journal). If you specify BIIZJRNL=Y in BBPARM member AAOPRMxx, messages for this event are written to the BBI Journal.

If you specify BIIZJRNL=N in BBPARM member AAOPRMxx, but you specify Y in the Journal Details field, messages for this event only will be written to the BBI Journal.

Target(s)

Specify that the Rule will send events to BMC Impact Manager cells.

You can specify up to six target cell names that can be up to 16-characters long each and can contain variables. If no targets are specified, the ALERT is sent to all cells.

Use the TGTNAME parameter in BBPARM member AAOGMExx to assign cells names. More than one cell can be assigned to the same target name.

To use wildcards in the target name:

• A plus sign matches a single character.
• An asterisk (*) indicates a the target name should match an unlimited number of characters.

For example, the target name IMPACT* matches all cell names that begin with the name IMPACT.

Additional considerations for sending ALERTs to cells follow:

• If a target is not specified, the ALERT is published by default to all connected cells
• An ALERT should always be published to the same cells
• An ALERT should always use the same PUBLISH parameter; if you choose to use ADD, use it consistently for all the ALERTS or use REPLACE consistently. Do not use ADD for some ALERTS and REPLACE for others

Event class

Specify a class to which all of the slots specified on the Event Action BEIM panel belong.

The class must be defined as a subclass of the default class which inherits all the slots from the default class (MV_EVENT_xxxx, where xxxx is the Rule or event type for this event.

If this value is not specified, the slots will be part of the default event class for the event (which is based on the type of Rule). Refer to the Help panels for examples of how to use this field.

When you specify an event class on this panel, you must also define the same class to the BMC Impact Manager cell as a subclass of the default class for this event.

The event class name should meet the following guidelines:

• 1 to 32 character class name (2 to 33 characters if the name begins with an ampersand, denoting a variable)
• valid characters include all upper and lower case alphabetic characters as well as numerics, national characters and most special characters
• lower case characters are not converted to uppercase (all characters are accepted exactly as received)

You can use variables but they must meet the following requirements:

• begin with an ampersand
• be 1 - 32 characters in length
• be either a LOCAL or SHARED variable

Event Classes: The following lists the default BMC Impact Manager event class and the corresponding Rule event type for which slots are defined for an event on the cell.

This field is optional and has no default.

Severity

Specify the severity of the event.

This Rule sends this value to the BMC Impact Manager cell along with any other specified fields.

This field is required; the default is WARNING and the following values are valid:

• UNKNOWN
• INFO
• MINOR
• CRITICAL
• OK
• WARNING
• MAJOR
• DOWN

You can also specify a LOCAL or SHARED variable. In addition, the variable must

• begin with an ampersand
• be 1 - 32 characters in length
• be defined when the Rule fires

Component Alias

Specify a value in the mc_smc_alias slot.

The event class name should meet the following guidelines:

• 1 to 55 character class name (2 to 55 characters if the name begins with an ampersand, denoting a variable)
• valid characters include all upper and lower case alphabetic characters as well as numerics, national characters and most special characters
• lower case characters are not converted to uppercase (all characters are accepted exactly as received)

You can use variables but they must meet the following requirements:

• begin with an ampersand
• be 1 - 32 characters in length
• be either a LOCAL or SHARED variable
• must be defined when the Rule fires

If you own the BMC product Discovery for z/OS, and you specified a VSAM data set name in BBPARM member AAOPRMxx with the DZDSN parameter, you can specify the variable &!QCIA.QSERVER.IMFCIJOB in this field. Refer to theMainView AutoOPERATOR BMC Impact Integration for z/OS User Guide for more information about the DZDSN parameter.

Event Slots and Slot Value

Specify additional data that you consider relevant to the particular event being sent to a BMC Impact Manager cell.

These fields are optional and have no default.

Both Event Slot name and a corresponding Slot Value must be specified together on the panel; you can specify

• a 1- to 32 character slot name
• a 1 - 38 character slot value

Refer to the BMC Impact Integration for z/OS User Guide for information about slot and class names.

You can also specify a LOCAL or SHARED variable. In addition, the variable must

• begin with an ampersand
• be 1 - 32 characters in length
• be defined when the Rule fires