TCP/IP TELNET Management Programming Manual

Relationship With Other Subsystems
Introduction
53474 Tandem Computers Incorporated 1–3
Once you have acquired this information, you can make informed decisions about
controlling the TELNET subsystem. You can take action either programmatically or
interactively with the available commands. You control your subsystem by
performing the following kinds of tasks:
Terminating the operation of windows
Adding windows to the subsystem
Adding a set of windows to the subsystem to provide a class of service
Changing certain attributes of a window or the process
Removing windows from the subsystem
Resetting the statistics counters
Initiating the operation of windows
Tracing the activity of a window or the process
Taking remedial action, if necessary, in response to event information previously
retrieved
Relationship With
Other Subsystems
The TELNET process provides a GUARDIAN 90 file-system interface to the TELNET
protocol. The TELNET protocol provides services at the application layer of the
TCP/IP protocol (corresponding to layers 6 and 7 of the OSI model). The TELNET
subsystem relies on the TCP/IP subsystem for the network and transport layers
(layers 3 and 4 of the OSI model); the TLAM I/O process (MLAM) for the link layer
(layer 2); and the TLAM controller process (MLMUX) for the physical layer (layer 1).
Note that the TELNET subsystem is built on top of the TCP/IP process, that the
TCP/IP subsystem is built on top of the TLAM I/O process, and that the TLAM
subsystem provides the interface to the Ethernet LAN. Figure 1-1 shows the
relationship between the TCP/IP subsystem, the TLAM subsystem, and the Ethernet
LAN. Note that Figure 1-1 also shows the relationship between the TELNET
subsystem and the TLAM Manager process (MLMAN). MLMAN is used indirectly
by the SCF or an SPI application to add the #IP and #ARP ports. It is through these
port that the TCP/IP subsystem can interface with the Ethernet LAN.