TS/MP 2.5 Pathsend and Server Programming Manual

server A process or program that provides services to a client or a requestor. Servers are designed
to receive request messages from clients or requestors; perform the desired operations, such
1.
as database inquiries or updates, security verifications, numerical calculations, or data
routing to other computer systems; and return reply messages to the clients or requestors. A
server process is a running instance of a server program.
2. A combination of hardware and software designed to provide services in response to requests
received from clients across a network. For example, NonStop servers provide transaction
processing, database access, and other services. (In the TS/MP and Pathway/iTS manual
set, the word “server” is generally used only when definition 1 is meant; for definition 2,
“system” is usually used instead of “server.”) See also client, requestor, client/server model,
and requestor/server model.
SERVER object A definition of a server-class within the configuration of a PATHMON process.
server-class A group of duplicate copies of a single server process, all of which execute the same object
program. server-classes are configured through the PATHMON process.
server-class send
operation
The sending of a message to a Pathway server-class by making a call to a Pathsend procedure.
The SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, and SERVERCLASS_DIALOG_SEND_
procedures perform server-class send operations. See also SEND operation.
service A function performed by a server process or program on behalf of a requestor or client. A server
can perform one or several services. The concept of a service is built into the design of the BEA
Tuxedo system and the NonStop Tuxedo system; for these products, a service is a module of
application code that carries out a service request.
simple token In the Subsystem Programmatic Interface (SPI), a token consisting of a token code and a value
that is either a single elementary field, such as an integer or a character string, or a fixed
(nonextensible) structure. See also extensible structured token and token (definition 2).
single-threaded A programming model that provides a single thread of control within a program. For example,
a single-threaded server handles only one request at a time and must complete that request before
accepting another. See also thread and multithreaded.
special register A data item defined by the SCREEN COBOL compiler, rather than explicitly in the program. Each
special register has a particular purpose and must be used only as defined. The SCREEN COBOL
language defines a different set of special registers from those defined by the standard COBOL
language.
SPI See Subsystem Programmatic Interface (SPI).
static server A server process that the PATHMON process creates when a START SERVER command is issued.
The PATHMON process starts the number of static servers defined by the NUMSTATIC attribute
for the server-class. See also dynamic server.
Structured Query
Language (SQL)
A relational database language used to define, manipulate, and control databases.
subsystem In the context of the Subsystem Programmatic Interface (SPI) and the Event Management Service
(EMS), a process or collection of processes that gives users access to a set of related resources
or services. A subsystem typically controls a cohesive set of objects. The Pathway subsystem
includes PATHMON processes, TCPs, and all other components of the PATHMON environment.
subsystem ID In management applications, a data structure that uniquely identifies a subsystem. The subsystem
ID is specified in SPI commands to identify the target subsystem, and in EMS event messages to
identify the source of the event message. The Pathway subsystem ID applies to all components
of the PATHMON environment, including PATHMON processes and TCPs.
Subsystem
Programmatic
Interface (SPI)
A set of Guardian procedures, message formats, and definition files that allows management
applications to communicate directly with subsystem processes, such as the PATHMON process,
for configuration and control of objects and for event management.
subtype 30 process A nonprivileged process that simulates terminals and communications devices.
subvolume A related set of files, as defined by the user, within the Guardian environment. The name of a
subvolume is the third of the four parts of a file name.
swap file A temporary file created by a process for temporary storage: for example, by the Kernel Managed
Swap Facility (KMSF) on behalf of a TCP for temporary storage of terminal context.
218 Glossary