DSM/SCM Event Management Programming Manual

SPI Programming Considerations for DSM/SCM
DSM/SCM Event Management Programming Manual—529844-003
3-2
Considerations for DSM/SCM Event Management
c. Call SSMOVE or SSMOVETKN to move the context token from the response
buffer to the GETEVENT command buffer. The context token is needed later,
when your application resends the command to get the next event message.
d. Call SSGET or SSGETTKN to retrieve the token containing the event message
(ZEMS-TKN-EVENT) from the response buffer.
e. Call EMSGET or EMSGETTKN to retrieve the subsystem ID (ZSPI-TKN-SSID)
and the event number (ZEMS-TKN-EVENTNUMBER) from the event
message. Together these two tokens identify the event message and
determine what information tokens it contains.
f. Call EMSGET or EMSGETTKN to retrieve the values of the other tokens from
the event message.
g. If you encounter the error list token (ZSPI-TKN-ERRLIST), make another call
to EMSGET or EMSGETTKN to retrieve the tokens in the error list.
h. Take action appropriate to the information in the event message.
For more information on the retrieval of tokens from event messages, see the EMS
Manual.
Considerations for DSM/SCM Event
Management
When an application receives and decodes DSM/SCM event messages:
•
All DSM/SCM event messages are reported to the alternate collector. No
DSM/SCM events are sent to the primary collector unless communication with the
alternate collector is unavailable. If the alternate collector is down, all event
messages are sent to the primary collector.
•
The maximum buffer size needed for any DSM/SCM event is 4000 bytes.
•
Most header tokens are common to event messages in C-series and D-series
RVUs. However, some header tokens are unique to C-series or D-series RVUs.
For example, the token ZEMS-TKN-SYSTEM is used only by C-series RVUs, and
the token ZEMS-TKN-NODENUM is used only by D-series RVUs. For more
information on how the differences between C-series and D-series RVUs can affect
your use of EMS, see the EMS Manual.