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 BMC II for z/OS extension to the BAROC event class structure contains one super class, MV_BMC AMI Ops, and three major subclasses of events. The MV_BMC AMI Ops super class is common to all BMC Impact Integration for z/OS connections. The subclasses are described in the following table.
BMC II for z/OS event major classes
BAROC event subclass | Description |
|---|---|
MV_ALERT | Stateful events representing BMC AMI Ops Automation |
MV_EVENT | Class of events that represent stateless BMC AMI Ops Automation events |
MV_CTRL | Class of events that represent control or meta data to be sent between BMC AMI Ops Automation and the TSOM cell |
This section contains the following topics :
Related topic