System events: origin, type and meaning
Events are occurrences in the system that are eligible to be sent to TSOM, such as MVS WTO messages. BMC II for z/OS supports three system-based z/OS events:
- MVS WTO messages
- Alarm Management
- External (or DD SUBSYS=) messages
In general, BMC II for z/OS differentiates events based on where they originated in the system and distinguishes the origin of the event as a different event type. When these events occur, BMC II for z/OS formats them in the Basic Recorder of Objects in C (BAROC) language and sends them to the BMC IM cell.
BAROC-formatted events contain slots, which are fields that represent the original z/OS event. These BAROC events can be modified or enhanced by Impact Rules.
To help you determine which z/OS events might be available on your system. The following table describes the event and the origin or cause of the event.
Event origins
Event type | Caused by |
|---|---|
ALRM | Alarm messages created by the Alarm Management |
EXT | Externally generated messages directed at the PAS by using the SUBSYS parameter on a DD statement in JCL |
MSG | WTO and WTOR messages from MVS |
MSGa | Multiline WTO (MLWTO) messages This type represents a subset of the MSG event type that appears on some Rule Processor panels when an event type MSG Rule is created with MLWTO Minor = All specified. |
MSGs | Multiline WTO (MLWTO) messages This type represents a subset of the MSG event type that appears on some Rule Processor panels when an event type MSG Rule is created with MLWTO Minor = Single specified. |
For more information about BAROC events, see BMC-II-for-z-OS-event-class-definitions