Pathmaker Programming Guide

Requester Definition Tasks
Creating Requesters
067868 Tandem Computers Incorporated 5–9
After defining the requester, you will go on to:
1. Enhance the appearance of the screen by using the Screen Painter (optional).
2. Integrate requesters and services.
a. Define any parameters this requester will receive from another requester.
b. Define any parameters this requester will send to or receive from services.
3. Generate the final version of the requester.
Using the Screen Painter to enhance the appearance of the screen is discussed in detail
in Section 6.
Selecting a Requester Type The Pathmaker product provides four types of requesters:
DB (database requesters)
MENU (menu requesters)
REG (registered requesters)
TRNS (transaction requesters)
You must select a requester type when you add the requester to the project catalog; the
default requester type is TRNS. After a requester has been added to the catalog, you
cannot change its type or name. The function and appearance of the application screen
the Pathmaker product creates is affected by the requester type you specify.
DB, MENU, and TRNS requesters have a context, which consists of a set of reference
objects. These terms are defined as follows:
Reference object A data item defined by a DDL record statement, a DDL
definition statement, or a NonStop SQL table object; a logical
copy of such an item that is used by a requester, screen, or
service.
Requester context The set of all reference objects used in a requester, including
both the objects that are displayed on the screen and the objects
that are not displayed. Nondisplayed reference objects can be
used as parameters to other requesters and to services.