Pathmaker Programming Guide

Designing a Pathmaker Application
Preparing for Pathmaker Application Development
067868 Tandem Computers Incorporated 2–3
Installing the
Pathmaker Product
One of the first tasks that should be completed while preparing for a Pathmaker
application development effort is the installation (or upgrade) of the Pathmaker
product on a development system. This task is normally handled by a system
administrator or other qualified person. The PMINSTAL utility is the tool used both
to install and upgrade the Pathmaker product. Consult the Pathmaker Reference
Manual, Utilities section for details about using PMINSTAL.
Designing a
Pathmaker Application
Producing a thorough application design is an important part of preparing for a
Pathmaker application development effort. The design should consider the
architecture of a Pathmaker application and contain all the necessary details about the
application and the development and production environments.
This subsection outlines the decisions that must be made and recorded while
designing an application that is to be implemented with the Pathmaker product. If
you are designing a DB requester application, you should be familiar with the
additional information about DB requester applications found in Section 3 and
Appendix B.
What Belongs in the Design
Specification
The following items should be included in the design specification for a Pathmaker
application.
General Information
The design specification should include the following general project information:
Pathmaker application type (DB Requester, custom or combination)
Standards and naming conventions
File locations (project work subvolumes, DDL source file , source and object code,
and so on)
Documentation and help-text standards
Error-handling standards
Description of the Data
The description of the data accessed by the application should include:
The name of each NonStop SQL table and view accessed by the application (and
related DEFINE name and Pathmaker name)
The name of each Enscribe file accessed by the application
Descriptions of the columns and fields
Statement of integrity rules
Entity relationship diagram