ZCOM C I/F Library Routines
ZEVENT_RCVR (3X)
NOTES | When an Application program issues a zread call, it can differentiate the |
| type of information it is receiving by looking at the type of the message. |
| ZCOM Event messages will return a message type of 5 |
| (ZCOM_MSTYPE_LSEM) for a local system event, and a message type of |
| 13 (ZCOM_MSTYPE_RSEM) for a remote system event. The difference |
| between local and remote event messages is where the event was |
| generated. Local event messages were generated locally and remote |
| event messages were generated at a remote node. The content of the |
| message will contain additional information about the event. |
| The ‘C’ structure for a ZCOM Event Message is shown below: |
typedef struct |
|
|
| |
uint8 | setype; | /* Event type. */ | ||
uint8 | seflag; | /* Event flags (reserved for now). */ | ||
uint16 | senode; | /* Node where event was generated. */ | ||
uint32 | setime; | /* Event time (Epoc time). */ | ||
union |
|
|
|
|
{ |
|
|
|
|
struct { |
| /* Node Status change Event data. */ | ||
| uint16 | node_num; | /* Node whose state has changed. */ | |
| int8 | nstat; | /* Node state change indicator. */ | |
| int8 | spare; | /* Reserved for future use. */ | |
| int8 | hstat[ZCOM_NHOST]; | /* Link state change indicator */ | |
| } node; |
|
|
|
struct { |
| /* Dynamic Reconfiguration Event data. */ | ||
| uint32 | cfg_class; |
| /* User supplied config class |
|
|
| /* | |
| uint32 | cfg_info1; |
| /* User supplied class specific info. */ |
| } recfg; |
|
| |
} sedata; |
| /* Event class specific data. */ | ||
} zevent_type; |
|
|
| |
For the field setype there are two defined event types:
ZCOM_SETYPE_NODE | - Node Status Change Event. |
ZCOM_SETYPE_RECONFIG | - Reconfiguration Complete Event. |
See the ZCOM Programmer’s Reference Manual for a detailed description of the fields in this data structure.
230 | Chapter 4 |