TCP/IP TELNET Management Programming Manual

Common Syntax Elements for the Subsystem
Elements of SPI Messages for the TELNET Subsystem
3–6 53474 Tandem Computers Incorporated
You can use wild-card characters in any combination; for example, $ZTNT.*1?? selects
all windows associated with the process $ZTNT that have names ending with a 1
followed by two characters. You can use object-name templates in the following
commands:
ABORT
DELETE
INFO
LISTOBJECTS
RESETSTATS
START
STATISTICS
STATUS
STOP
Note that object-name templates cannot be specified for the PROC object type as there
is only one PROC object, and it must be fully specified.
Event Numbers Event numbers identify event messages issued by the TELNET subsystem. Each event
message that can be reported by the TELNET subsystem has a different event number
assigned to it. The TELNET 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. Symbolic names of event numbers have the form Zsss-EVT-event, where sss
is a three-character abbreviation for the subsystem and event identifies the event. The
TELNET subsystem is represented by the abbreviation TNT.
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 TELNET subsystem: ZCOM-TKN-
SUBJ-PROC or ZCOM-TKN-SUBJ-WINDOW.
An application obtains the subject of an event message by passing the ZEMS-TKN-
SUBJECT token to the EMSGET procedure. Refer to the Event Management Service
(EMS) Manual for details on obtaining subjects of event messages.
Tokens The TELNET subsystem uses tokens for parameters and responses to commands and
for elements of event messages. Each token has a token code and a token value. The
token code is the identifying tag that programs use to refer to the token. The token
value is the actual data item assigned to the token code. The token code has two parts:
a token type that specifies the data type and length of the token value, and a token
number that uniquely identifies the token for the subsystem. See Section 5, “Common
Definitions,” for a list of the token types used in the TELNET subsystem.