Introduction to Pathmaker

Glossary
067867 Tandem Computers Incorporated Glossary–7
registered (REG) service/server. A service or server written outside of the Pathmaker
environment but known to a Pathmaker project. It is possible to create a Pathmaker
application that accesses outside servers without registering them; however,
registering them allows the Pathmaker product to move their associated files during
import and export operations. Identifying the files used by a server through service
registration allows the Pathmaker product to generate statements in the Pathway
command file for running the servers.
release number. A code that designates the release date of a Tandem product. The
release number begins with a letter and is followed by a two-digit number. For
example, C20 is the release number for some products released in 1989. Look on the
title page of this manual to find out which release of the Pathmaker product this
edition documents.
reply message. A type of interprocess communication (IPC) message formatted by a
service and sent back to a requester after the service has completed its work. A reply
message is initiated in the COBOL85 server code by a WRITE statement to the
$RECEIVE file.
report. A listing of information from a project's catalog or from an application's
database. The Pathmaker product provides a number of standard Enform reports
showing such information as object types defined in the catalog, service and server
structure, relationships between requesters, and many more details. To create reports
that extract information from an application database, application developers must
create requesters and servers for this purpose.
requester. 1. A process controlling the interaction between servers and end users. A
requester can control terminal displays; accept, interpret, and validate input from the
end user; request database access through servers; and return information to the end
user. In Pathmaker and other Pathway environments, terminal control processes
(TCPs) interpret SCREEN COBOL programs to serve as requesters. 2. A Pathmaker
application module corresponding to a SCREEN COBOL program unit. A Pathmaker
requester contains presentation logic for a single logical screen (which can contain
several pages), manages terminal context associated with that screen, communicates
with services, and contains navigation logic. There are four types of Pathmaker
requesters: database (DB), transaction (TRNS), menu (MENU), and registered (REG).
requester copy library. An optional EDIT file that contains additional SCREEN COBOL
code written by an application developer for inclusion in a Pathmaker requester.
requester-server application. An application divided into two parts: the requesters, which
perform data collection, and the servers, which access and modify the database.
Requesters and servers communicate with interprocess communication messages.
requester skeleton. The framework for all generated requesters. The requester skeleton
consists of SCREEN COBOL source text lines plus special macro language command
lines.
The requester skeleton consists of two files: REQSKL and REQDBSKL. REQDBSKL
contains sections that only pertain to DB requesters. In discussions in which the term
requester skeleton is used without specifying a file, REQSKL is meant.