TCP/IP (Parallel Library) Migration Guide
Glossary
HP NonStop TCP/IP (Parallel Library) Migration Guide—522272-003
Glossary-11
summary state
interface procedures; and definition files in Data Definition Language (DDL) for
programmers writing their own subsystems.
summary state. In DSM interfaces to HP data communications subsystems, one of the
generally defined possible conditions of an object, with respect to the management of
that object. A summary state differs from a state in two ways. First, a summary state
pertains to the management of an object, whereas a state might convey other kinds of
information about the object. Second, summary states are defined the same way for all
HP data communications subsystems, whereas the set of possible states differs from
subsystem to subsystem. The management programming interfaces to HP data
communications subsystems refer to summary states rather than to states. Examples
of summary states are STARTED, STOPPED, SUSPENDED, and ABORTING.
SWAN concentrator. See ServerNet wide area network (SWAN) concentrator.
system configuration database (CONFIG). A database that stores generic processes in
the Kernel subsystem. The system configuration database is located in the
$SYSTEM.ZSYSCONF subvolume. The persistence manager ($ZPM) starts all
generic processes stored in the system configuration database and optionally
manages their persistence.
TCP (Transmission Control Protocol). The Internet standard transport-level protocol that
provides the reliable, full-duplex stream service on which many application protocols
depend. TCP allows a process on one machine to send a stream of data to a process
on another. It is connection-oriented, in the sense that before transmitting data
participants must establish a connection. Software implementing TCP usually resides
on the operating system and uses the IP protocol to transmit information across the
Internet. It is possible to terminate (shut down) one direction of flow across a TCP
connection, leaving a one-way (simplex) connection. The Internet protocol suite is
often referred to as TCP/IP because TCP is one of the two most fundamental
protocols.
TCPMAN. The manager process for Parallel Library TCP/IP named $ZZTCP. Provides the
configuration and management processing of the TCP/IP process.
TCPMON. The monitor object for Parallel Library TCP/IP with the naming convention
$ZPTMprocessor-number. Provides error recovery and adjunct protocol processing.
One monitor object is required for each processor in which Parallel Library TCP/IP is
configured.
TCPSAM. The socket access method process for Parallel Library TCP/IP. TCPSAM is a
process pair provided for backward-compatibility for socket applications, providing
applications with a name for a socket transport service provider.