TCP/IP TELNET Management Programming Manual

Common Syntax Elements for the Subsystem
Elements of SPI Messages for the TELNET Subsystem
53474 Tandem Computers Incorporated 3–3
Note This manual uses the DDL to describe all tokens. For a brief review of DDL, refer to the appendix
“Overview of DDL for SPI” in the Distributed Systems Management (DSM) Programming Manual. In that
appendix, definition names contain hyphens. If you are programming in TAL or TACL, substitute a
circumflex (^) for each hyphen in a definition name as it appears in this manual. For example, ZCOM-
OBJ-WINDOW becomes ZCOM^OBJ^WINDOW in TAL and TACL.
Naming Rules and
Guidelines for
Applications
All items in definition files are assigned symbolic names as well as numbers. The
symbolic names are used to prevent transcription errors and to improve readability.
Tandem uses names beginning with the letter Z for all definitions and all component
fields of structures in its definition files. To avoid present and future conflicts with
names defined by Tandem, do not begin any name you define in your application with
an uppercase or lowercase Z.
Common Syntax
Elements for the
Subsystem
The remainder of this section contains subsystem-specific information about elements
of commands, responses, and event messages. These elements are in token form and
are referred to by their symbolic names. An advantage of using the symbolic name is
that you are not required to know the address or position of the element within the
buffer.
For more complete information about these elements as they relate to data
communications subsystems, refer to the Communications Management Programming
Manual.
Command Numbers Command numbers specify a command to the TELNET subsystem or a response to a
management application. The management application uses a symbolic name to
express the command number to the TELNET subsystem, and the subsystem uses the
symbolic name to identify the corresponding response. The symbolic name has the
form ZCOM-CMD-name, where name identifies the command. For example, ZCOM-
CMD-ADD identifies the ADD command in all data communications subsystems,
including the TELNET subsystem.
The command number specified by the management application is stored in the
header of the command message. The subsystem and management application can
read the command number from the header using the token ZSPI-TKN-COMMAND
in the SSGET SPI procedure.
Management applications should not use the token ZSPI-TKN-COMMAND to place
the command number in the message header because the command number that is
going to be specified is already known. Instead, your management application should
use the command’s symbolic name, ZCOM-CMD-name (which is the value of the token
ZSPI-TKN-COMMAND), in the SSPUT SPI procedure to place the command number
in the message.