TCP/IP TELNET Management Programming Manual
Data Communications Standard Definitions
Common Definitions
53474 Tandem Computers Incorporated 5–9
ZEMS-TKN-EMPHASIS
specifies whether the event message is considered critical. If the value of the token
is ZSPI-VAL-TRUE, the event is considered critical; if the value is ZSPI-VAL-
FALSE, the event is not considered critical.
ZEMS-TKN-EVENTNUMBER
specifies the event number of a TELNET event message. These event numbers and
their associated event messages are described in Section 7, “Event Management.”
ZEMS-TKN-GENTIME
is the time, in Greenwich Mean Time (GMT), that the subsystem created the event
message.
ZEMS-TKN-LOGTIME
is the time, in GMT, that the collector wrote the event message to its log files.
ZEMS-TKN-PIN
is the process identification number (PIN) of the subsystem that reported the
event.
ZEMS-TKN-SUBJECT-MARK
indicates that the token that follows is the subject token. The TELNET subsystem
uses two subject tokens: ZCOM-TKN-SUBJ-PROC and ZCOM-TKN-SUBJ-
WINDOW. See Section 7, “Event Management,” for a detailed description of this
token
ZEMS-TKN-SYSTEM
is the EXPAND system number of the system (node) on which the event was
reported.
ZEMS-TKN-USERID
specifies the user ID of the TELNET subsystem process.
Data Communications
Standard Definitions
Definitions whose names begin with ZCOM- are data communications standard
definitions. These definitions are available to all data communications subsystems,
such as TELNET, and are found in the ZSPIDEF.ZCOMDDL definition file and in the
files for other languages. Refer to “Definition Files” in Section 3, “Elements of SPI
Messages for the TELNET Subsystem,” for details on data communications standard
definitions.
Table 5-3 lists only those data communications standard definitions used in the
management-programming interfaces to the TELNET subsystem. The table does not
list data communications error numbers or definitions used only in error lists
associated with those error numbers. For a description of all data communications