TCP/IP Management Programming Manual

Elements of SPI Messages
HP NonStop TCP/IP Management Programming Manual—529636-001
3-7
Event Numbers
You can use wild-card characters in any combination.
You can use object-name templates in these commands:
•
ABORT
•
DELETE
•
INFO
•
LISTOBJECTS
•
RESETSTATS
•
START
•
STATISTICS
•
STATUS
•
STOP
Note that object-name templates cannot be specified for the PROC object type. There
is only one PROC object, and it must be fully specified.
Event Numbers
Event numbers identify event messages issued by the TCP/IP subsystem. Each event
message that can be reported by the TCP/IP subsystem has a different event number
assigned to it. The TCP/IP event numbers and their associated event messages are
described in Section 7, Event Management.
An event number is part of the header of an event message. The header token
ZEMS-TKN-EVENTNUMBER contains the event number. The value of the event
number is subsystem-specific and also has a symbolic name. Because event numbers
represent unique events for a particular subsystem, you must specify both the event
number and the subsystem ID of the subsystem that created the event to identify a
particular event message. The symbolic names of event numbers are of the form
Zsubsys-EVT-event, where subsys is a three-character abbreviation for the
subsystem and event identifies the event. The TCP/IP subsystem is represented by
the abbreviation TCI.
Subjects of Event Messages
The subject of an event message is always preceded by the
ZEMS-TKN-SUBJECT-MARK token and can be one of two tokens for the TCP/IP
subsystem: either ZCOM-TKN-SUBJ-PROC or ZCOM-TKN-SUBJ-SUBNET. The
subject is a string that contains the name of the TCP/IP process or subnet that is the
subject of the event message.
An application obtains the subject of an event message by passing the
ZEMS-TKN-SUBJECT token to the EMSGET procedure. For details on obtaining
subjects of event messages, see the EMS Manual.