ZCOM Tables and Data Structures
Message Header
System Event Message (zevent_type)
A System Event Message (SEM) is a special message generated by the ZCOM subsystem to represent an alarm condition or type of event that has occurred within the ZCOM subsystem. Applications may request that ZCOM deliver these events to a program ZLU by issuing a zevent_rcvr call. A SEM is returned to the application as a normal data message with a message type of ZCOM_MSTYPE_LSEM (5) or ZCOM_MSTYPE_RSEM (13). See the zevent_rcvr routine for addition details.
The structure used to hold the system event messages is composed of a fixed header structure and a variable part that is specific to the type of event. See Table
Table | System Event Message (zevent_type) Structure |
| ||
|
|
|
|
|
Field Name |
| Field Description | Field Type | Size |
| (Bytes) | |||
|
|
|
| |
|
|
|
|
|
SETYPE |
| System Event Type | uns.char | 1 |
|
|
|
|
|
SEFLAG |
| Event flags (currently not used) | uns.char | 1 |
|
|
|
|
|
SENODE |
| Node where event was generated | uns.short | 2 |
|
|
|
|
|
SETIME |
| Time when the event occurred | uns.int | 4 |
|
|
|
|
|
SEDATA |
| Event specific data | union struct | 8 |
|
|
|
|
|
| SETYPE - System Event Type |
|
| |
This field contains the type of event represented by this message. Currently there are three defined types of events; a node status event (ZCOM_SETYPE_NODE), a card status change event (ZCOM_SETYPE_CARD), and a dynamic reconfiguration event (ZCOM_SETYPE_RECONFIG). The format of the variable part of the message is dependent on the event type.
SEFLAG - Event flags (currently not used)
This field is currently not used. It is intended to contain global information on the event (e.g. event priority, etc).
SENODE - Node where event was generated
Chapter 3 | 119 |