BAROC events
By using the Basic Recorder of Objects in C (BAROC) language, the administrator defines each possible event class and its slots.
Each slot has a data type and can have specific attributes, called facets, that can control the values that the slot can have or control aspects of an event processing. The event source (adapter, integration, another cell, API, or the BMC Impact Manager CLI) must provide the events in the BAROC format and structure. The cell checks whether the incoming source event data matches a BAROC definition in the Knowledge Base. A data class defines the class and slots of dynamic data instances and service model component instances.
The BAROC event class structure contains one super class, MV_MainView, and two major subclasses, MV_EVENT and MV_CTRL.
BMC II for z/OS event major classes
BAROC event subclass | Description |
|---|---|
MV_EVENT | Class of events that represent stateless events |
MV_CTRL | Class of events that represent control or meta data to be sent between BMC II for z/OS and the BMC Impact Manager cell |
The following image shows the BAROC event class hierarchy.
BAROC event class hierarchy
|
+--- MV_MainView <--- Common MainView class (common data)
+--- MV_EVENT <--- Common Events class
| +--- MV_EVENT_ALARM
| +--- MV_EVENT_EXT
| +--- MV_EVENT_MSG
+--- MV_CTRL <--- Control Events (Meta Data)
+--- MV_CTRL_REQUEST
+--- MV_CTRL_WTO_REQUEST