Skip to Content

Event grouping

During automation processing, events are generated and issued.

Depending on the criteria that you defined in the solution, a large number of events can be generated and sent to various destinations. which might not be desirable (that is, sending 100 event messages to a TSO session). Event grouping enables you to send one single event that represents a large number of events.

Related topic

Using-BMC-AMI-Storage-Automation

A group event is an event definition (EVENTID) that has been identified in another event definition (within the same SMEVNT member) by the use of the GRP_EVENT keyword. The end result is one event paired up with another event: one event that is issued for each match of the criteria that is defined in an AUTO function solution and the other (group event) issued when the AUTO function processing that solution ends.

The two event definitions have similarities and differences. The similarities are the keywords that are used to define the events. Other than the use of the keyword GRP_EVENT, the keywords available for both types of definitions are the same, although they may be coded differently. Accordingly, the DEST keyword is of particular value. Because both definitions can contain the DEST keyword, the events can be sent to different locations. For example, the single event, that which is issued for each match, could be sent to an automated operations product for further processing, while the one group event, which is issued at completion of the AUTO function processing, could be sent to a TSO user. Using the example in the first paragraph, 100 events could be sent to an automation product (such as BMC AMI Ops Automation) and one event could be sent to the TSO session informing the user that 100 events have been sent to BMC AMI Ops Automation.

The difference between the two types of events is the processing that occurs with them and the result of that processing. A single event is processed as the criterion in the solution is being met, which allows the event text to contain variables that are replaced by information that is specific to the resource that is being processed (that is, values for the INC and or EXC parameters coded in the solution). A group event is processed at the completion of the function and is initiated solely because it is related to the single event that was defined in the solution. Also, a group event represents any number of related single events, each of which might contain any number of (INC or EXC) variables replaced by as many values. It is for these reasons that group events use specific variables different from those of single events. That is, they do not use INC or EXC parameter variables. The values for group event variables contain information about the related single event that was issued.

For more information, see:

Variables for use in group event text

Variable

Description

&GRP_REVENT

Is replaced with the single event ID that identified this event as a group event

&GRP_EVCNT

Is replaced with the count (number) of single events that were issued

&GRP_FUNC

Is replaced with the name of the auto function that was executed

SMEVNTxx examples

Information
Example

In this example, event ID AD080 will be used in a solution processed by the AUTODS function. Event AD080 has defined event AG001 as its group event.

SET EVENTID=AD080
    SEV=W
    MODE=ACT
    EVNT_HDR=NO
    DEST=(AO)
    GRP_EVENT=AG001
    TEXT='SOL=COMPRLSE &AD_DSN EXTS=&AD_EXTS DSORG=&AD_DSORG'
*
SET EVENTID=AG001
    SEV=W
    MODE=ACT
    EVNT_HDR=NO
    DEST=(TSO)
    DEST_USER=(TSU123,TSU456)  
    TEXT='&GRP_FUNC ISSUED &GRP_EVCNT &GRP_REVENT EVENTS'

Results


SVWAD080W SOL=COMPRLSE MYDSN.DATASET EXTS=5 DSORG=PO
Information
Example

This example shows the event message as it might appear after the variables have been replaced with values. For example, assume 35 such messages were sent to BMC AMI Ops Automation (and the Logger).


SVWAG001W AUTODS ISSUED 35 AD080 EVENTS

This example shows the group event message as it would appear after the variables were replaced. Following the example, this one message would be sent to TSU123, TSU456, and the Logger.

Event group view

Use the following procedure to display the 

BMC AMI Storage

 group events that were written to the 

Logger

.

  1. From the EZSRM main menu, select Tools and Menus > Automation.

  2. From the EZSRMAU Automations Menu, select Group Events.The GRPEVENT view is displayed as shown in the following figure.

    Event group view (GRPEVENT)

    17JUL2013  16:29:06 ------ BMC AMI Ops WINDOW INTERFACE (V7.0.00) ----------------
    COMMAND  ===>                                                 SCROLL ===> PAGE
    CURR WIN ===> 1        ALT WIN ===>                                            
    >H1 =GRPEVENT==========SJSGPD75=*========17JUL2013==16:29:05====MVSRM====D====1
    Event      Event    Event     Function Event Text                             
    Date       Time     --------- -------- ----------                             
    2013/07/17 14:20:32 SVWAG081W AUTODS   ISSUED 3 AD081 EVENTS FOR FUNCTION AUTO
    Success

    Tip

    Select the Event column in a selected row to display the EVENTMSG view that displays the events related to the selected group event.

Event messages view

Use the following procedure to display the 

BMC AMI Storage

 events that were written to the 

Logger

.

  1. From the EZSRM main menu, select Tools and Menus > Automation.

  2. From the EZSRMAU Automation Options menu, select Events.The EVENTMSG view is displayed as shown in the following figure.

    Event messages view (EVENTMSG)

    17JUL2013  16:30:09 ------ BMC AMI Ops WINDOW INTERFACE (V7.0.00) ----------------
    COMMAND  ===>                                                 SCROLL ===> PAGE
    CURR WIN ===> 1        ALT WIN ===>                                            
    >H1 =EVENTMSG==========SJSGPD75=*========17JUL2013==16:30:09====MVSRM====D===28
    Event      Event    Event     Function Event Text                             
    Date       Time     --------- -------- ----------                             
    2013/07/17 14:20:32 SVWAD081W AUTODS   SOL=TEST1 VAM3.ISPTLIB EXTS=1 DSORG=PO
    2013/07/17 14:20:32 SVWAG081W AUTODS   ISSUED 3 AD081 EVENTS FOR FUNCTION AUTO
    2013/07/17 14:20:32 SVWAD081W AUTODS   SOL=TEST1 RXA32.BASE.LINKLIB EXTS=1 DSO



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Storage Automation 8.2