TS/MP 2.5 System Management Manual

are two types of screen: base screens and overlay screens. See also base screen, overlay screen,
and screen description entry.
SCREEN COBOL A procedural language developed by Tandem and based on COBOL that is used to define and
control screen displays on terminals and other input/output devices. SCREEN COBOL allows
programmers to write requestor programs that communicate with operator terminals and intelligent
input/output devices, and that send data to server processes that manage application databases.
SCREEN COBOL programs are compiled into pseudocode form by the SCREEN COBOL compiler
and then interpreted by the TCP. See also terminal control process (TCP).
SCREEN COBOL
Utility Program
(SCUP)
A utility that provides control and manipulation of SCREEN COBOL object files.
screen description
entry
A declaration of a base screen, and, optionally, an overlay screen, in the Screen Section of a
SCREEN COBOL program. See also screen, base screen, and overlay screen.
screen overlay
area
See overlay area.
screen program A SCREEN COBOL requestor program. See also SCREEN COBOL.
Screen Section A section in the Data Division of a SCREEN COBOL source program that describes the types and
locations of fields in screens that can be displayed on a terminal.
screen-oriented
requestor
A SCREEN COBOL requestor that sends data from working storage to the display screen of a
terminal by way of screen templates defined in the Screen Section of the Data Division. Similarly,
such a requestor receives data from the terminal into working storage by way of Screen Section
templates. It uses ACCEPT and DISPLAY statements in the Procedure Division to interact with the
display terminals. Standard SCREEN COBOL requestors are screen-oriented. See also
message-oriented requestor.
SCUP See SCREEN COBOL Utility Program (SCUP).
SEND operation In SCREEN COBOL, an operation in which a transaction request message is sent to a server
process and a reply is received back from the server process. See also server-class send operation.
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
•
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.
• A combination of hardware and software designed to provide services in response to requests
received from clients across a network. For example, Tandem’s Himalaya servers provide
transaction processing, database access, and other services. (In the NonStop TS/MP and
Pathway/TS 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 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 object A definition of a server class within the configuration of a PATHMON process.
server-class send
operation
The sending of a message to a Pathway server class by making a call to the Pathsend
SERVERCLASS_SEND_ procedure. 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 Novell
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.
342 Glossary