TS/MP 2.5 Pathsend and Server Programming Manual

requestor/server
model
A model for application design that divides the tasks of data input, data manipulation, and data
output between two basic types of process: requestors and servers. A requestor sends a request
to a server. The server takes the requested action and then replies to the requestor. The requestor
and server might reside on the same processor or on different processors. This model is used for
interprocess communication in the Guardian environment. See also requestor and server.
reserved word A word that can be used only as a keyword.
resources The components of a computer system that work together to process transactions. Terminals,
workstations, CPUs, memory, I/O controllers, disk drives, processes, files, and applications are
examples of resources.
response time The amount of time it takes to receive a response from the system after initiating a request message
(for example, by pressing a function key).
retryable operation An operation that can be interrupted and repeated an indefinite number of times without affecting
the consistency of the database; for example, all read operations are retryable.
RISC See reduced instruction-set computing (RISC).
root directory An OSS directory associated with a process that the system uses for pathname resolution when
a pathname begins with a slash (/) character. See also OSS pathname.
RSC/MP See Remote Server Call (RSC).
scalability The ability to increase the size and processing power of an online transaction processing system
by adding processors and devices to a system, systems to a network, and so on, and to do so
easily and transparently without bringing systems down. Scalability is also sometimes called
expandability.
SCOBOLX The object file for the SCREEN COBOL compiler program. This name is given in a TACL command
to invoke the compiler. See also SCREEN COBOL.
screen A group of data fields that represent formatted data to be displayed on a terminal. A screen is
defined by a screen description entry in the Screen Section of a SCREEN COBOL program. There
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 HP 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.
217