Introduction to Pathmaker

2 Pathmaker Applications
067867 Tandem Computers Incorporated 2–1
An important part of understanding the Pathmaker product is knowing how an
application produced with the product looks and behaves. This section helps you gain
this knowledge by:
Explaining the architecture of an application produced with the Pathmaker
product.
Describing how an end user operates an application produced with the Pathmaker
product.
Discussing ways that an application developer can customize a Pathmaker
application.
Describing the types of applications that can be created using the Pathmaker
product.
Introducing additional capabilities of the Pathmaker product.
The Architecture of a
Pathmaker Application
A Pathmaker application has a specific architecture; that is, an application produced
with the Pathmaker product has a distinctive appearance, way of behaving, and is
constructed in a particular way. Every application created with the Pathmaker
product conforms to the Pathmaker style.
The Pathmaker product can produce Pathway requester-server applications that can
run in block mode on either the 6520/6530 family of Tandem terminals (including PCs
with 6530 emulators) or on 3270-type terminals (including PCs with 3270 emulators).
Pathmaker applications can also be produced for JET6530 terminals and 3270 terminals
that support Kanji.
Screen Layout The screen the Pathmaker product creates for most requesters is divided into four
major areas:
Title area
Data field area
Function key list
Message area
The title area contains the requester title, which is a brief description that helps the
end user identify the major purpose of a particular requester screen, and a page
designator (for example, Page 1/3), which shows the number of the current page and
the total number of pages for this screen. (Pages are explained in a subsequent
discussion.) The title area is usually the first line of the screen.
The data field area is usually found between the two rows of equal signs on the
screen. When the Pathmaker product creates a requester screen, it places all of the
data fields and the headings that identify them within this area. Data fields are the
places on the screen where data is entered by, or displayed to, the end user.