IPX/SPX Configuration and Management Manual

Glossary
IPX/SPX Configuration and Management Manual—425731-001
Glossary-13
summary state
summary state. In Distributed Systems Management (DSM) interfaces to Compaq data
communications subsystems, one of the generally defined possible conditions of an
object, with respect to the management of that object. Summary states for NonStop™
IPX/SPX objects include ABORTING, DEFINED, STARTED, STARTING, STOPPED,
and STOPPING.
TACL. See Tandem Advanced Command Language (TACL)
.
TAL. See Transaction Application Language (TAL)
.
Tandem Advanced Command Language (TACL). The user interface to the NonStop™
Kernel operating system. TACL is both a command interpreter and a command language
interface (CLI). The TACL command interpreter uses the ITI protocol. Users can write
programs in TACL as a way to perform complex tasks simply or to provide a consistent
user interface across independently programmed applications.
Tandem Failure Data System (TFDS). A diagnostic tool that is a component of the
NonStop™ Kernel operating system. TFDS isolates software problems and provides
automatic processor failure data collection, diagnosis, and recovery services. TFDS
monitors processors and automatically initiates a processor dump if a processor fails.
The failed processor is reloaded automatically, and the processor is analyzed along with
the incident.
Tandem Terminal Emulator (TTE). See Outside View with Tandem Terminal Emulator
(TTE).
TDP. See Transaction Delivery Process (TDP)
.
Telnet. The Internet standard protocol
for remote terminal connection service. Telnet allows a
user at one site to interact with remote timesharing systems at another site just as if the
user’s terminal were connected directly to the remote machine.
Telserv. A Compaq product that provides the Telnet
protocol for remote terminal connection
service.
TFDS. See Tandem Failure Data System (TFDS)
.
token. In Distributed Systems Management (DSM)
, a distinguishable unit in a Subsystem
Control Facility (SCF) message. Programs place tokens in a buffer using the SSPUT or
SSINIT procedures and retrieve them from the buffer with the SSGET procedure. A
token has two parts: an identifying code or token code, and a token value. In command
and response messages, a token normally represents a parameter to a command, an item
of information in a response, or control information for the subsystem. In event
messages, a token normally represents an item of information about an event or about
the event message itself.