TS/MP 2.5 Pathsend and Server Programming Manual

primary process fails, the backup process is notified that it is now the primary, and it resumes
the application work from the last valid checkpoint message.
process type An attribute of a server-class indicating whether the server processes in that server-class are
Guardian processes or OSS processes. See also process.
program file An executable object file. See also object file.
PROGRAM object A template for creating and starting temporary TERM objects. See also temporary TERM object.
pseudo Pathsend
procedure
In the Extended General Device Support (GDSX) software, one of the TSCODE-supported
procedures that have Pathsend procedure counterparts.
pseudocode file A file containing compiled code that is interpreted by software instead of being executed by the
hardware. The SCREEN COBOL compiler produces pseudocode to be interpreted by the TCP.
See also object file.
pTAL See Portable Transaction Application Language (pTAL).
reduced
instruction-set
computing (RISC)
A processor architecture based on a relatively small and simple instruction set, a large number
of general-purpose registers, and an optimized instruction pipeline that supports high-performance
instruction execution. See also complex instruction-set computing (CISC).
relative pathname An OSS pathname that does not begin with a slash (/) character. A relative pathname is resolved
beginning with the current working directory. See also OSS pathname, absolute pathname, and
current working directory.
Remote Duplicate
Database Facility
(RDF)
The HP software product that assists in disaster recovery for OLTP production databases, monitors
database updates audited by the TMF subsystem on a primary system, and applies those updates
to a copy of the database on a remote system.
reply message The part of an interprocess communication message that is formatted by a server and returned
to the original requestor. The message contains the results of the server’s work. See also request
message.
reply translation
header
A group of header fields that the Pathway translation server for the NonStop Tuxedo system inserts
at the beginning of each reply message it relays from the application service to a SCREEN COBOL
or Pathsend requestor. This header indicates whether the request was processed successfully and
whether the reply contains data returned by the application service. See also request translation
header.
request message The part of an interprocess communication message that is formatted by a requestor and sent to
a specific server. The message contains any data and instructions needed by the server to perform
its processing. See also reply message.
request translation
header
A group of header fields that must be included at the beginning of each request message a
SCREEN COBOL or Pathsend requestor sends to the Pathway translation server for the NonStop
Tuxedo system. This header specifies the NonStop Tuxedo application service for which the
message is destined, the NonStop Tuxedo buffer types of the request and reply messages as seen
by the service, and options that modify the invocation of the service. The translation server removes
this header from the request message before sending it to the application service. See also reply
translation header.
request/response
model
A model for requestor/server communication in which a requestor passes a single request to a
server process and receives a single response. See also conversational model and
request/response server.
request/response
server
A server that provides request/response services. A service of type request/response is handled
like a procedure and has the following properties: it is executed until completion, it does not have
any dialog with the requestor, and it sends back a return value to the requestor. A request/response
server is analogous to a context-free Pathway server.
requestor A process or program that runs in the Guardian environment on a NonStop system and requests
services from a server process. For example, a SCREEN COBOL program is a requestor program
that is interpreted by the TCP, which provides link access to Pathway server-classes. Another type
of requestor program makes requests through Pathsend procedure calls; such a requestor uses
the ACS Subsystem process for link access to server-classes. A third type of requestor communicates
with server processes directly by calling the Guardian WRITEREAD procedure; this kind of requestor
does not use server-classes. A requestor is a specific type of client. See also client, server, and
requestor/server model.
216 Glossary