Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

Event Management
Safeguard Management Programming Manual—422086-028
8-6
Event-Message Buffers
For example, an application written in COBOL needs these definition files:
For more information about the SPI, EMS, and data communications definitions, see
the SPI Programming Manual, the EMS Manual, and the SPI Common Extensions
Manual, respectively. This section describes the Safeguard definitions.
Event-Message Buffers
The minimum Safeguard event-message buffer size is 128 words. The entire event-
message buffer is contained in the token ZEMS-TKN-EVENT. In turn, this token is
contained in the response buffer for the syntax of the GETEVENT command. For more
information, see the EMS Manual.
Essentially event-message buffers are like any other SPI buffers. They contain header
tokens and data portion tokens. The header and data portion tokens that appear in all
Safeguard event messages are listed in Table 8-1.
These tokens also appear in each of the individual message descriptions later in this
section even though their values are the same for all event messages. Data-portion
tokens that appear only in certain messages are listed in the individual message
descriptions.
ZSPIDEF.ZSPICOB SPI definitions
ZSPIDEF.ZEMSCOB EMS definitions
ZSPIDEF.ZGRDCOB Guardian definitions
ZSPIDEF.ZFILCOB File-system definitions
ZSPIDEF.ZCOMCOB Data communications definitions
ZSPIDEF.ZCMKCOB Common kernel definitions
ZSPIDEF.ZSFGCOB Safeguard definitions
Table 8-1. Tokens That Appear in All Event Messages (page 1 of 2)
Header Tokens Token Type
ZSPI-TKN-MAX-FIELD-VERSION ZSPI-TYP-UINT
ZSPI-TKN-SSID ZSPI-TYP-SSID
ZSPI-TKN-USEDLEN ZSPI-TYP-UINT
ZEMS-TKN-CONSOLE-PRINT ZSPI-TYP-BOOLEAN
ZEMS-TKN-CPU ZSPI-TYP-UINT
ZEMS-TKN-CRTPID ZSPI-TYP-CRTPID
ZEMS-TKN-EMPHASIS ZSPI-TYP-BOOLEAN
ZEMS-TKN-EVENTNUMBER ZSPI-TYP-ENUM
ZEMS-TKN-GENTIME ZSPI-TYP-TIMESTAMP
ZEMS-TKN-LOGTIME ZSPI-TYP-TIMESTAMP