Pathmaker Programming Guide

Merging Pathmaker Projects
Finishing and Installing the Application
7–30 067868 Tandem Computers Incorporated
Summary of Steps for
Merging Pathmaker
Projects
The following list summarizes the steps for creating a single Pathmaker application
using multiple Pathmaker projects:
1. Establish naming conventions for projects and objects within projects.
2. Create a master project:
a. Add a main menu that calls root requesters in the subsidiary projects.
b. Create other requesters and services for this portion of the application.
c. Create the registered requesters to register root requesters in the subsidiary
projects.
3. Create subsidiary projects:
a. Create a dummy initial requester to call root requesters in the project.
b. Create other requesters and services for this portion of the application.
4. Integrate and generate the requesters and servers in separate projects. Portions of
the application can be installed and tested separately.
5. Merge the projects by merging requester object code:
a. Delete the initial requester object code from the POBJ library of subsidiary
projects.
b. Use SCUP to move the requester object code from every project to the central
subvolume on the production system.
6. Move the server object files, help databases, command files, and required
Pathmaker files to the production system.
a. Use FUP to move the server object files, including one copy of the help server
and one copy of the DB standard server (if needed), to the central subvolume
on the production system.
b. Use FUP to move the help databases and command files for subsidiary
projects to unique subvolumes on the production system. Use FUP ALTER to
alter the file labels of the help database files so that they indicate the new
location of the alternate key file.
7. Create one PATHCNFG file on the central subvolume of the production system
containing information for the merged projects.