1. Data Management Library
Pathmaker
Programming Guide
Abstract This manual explains, in detail, how to design, develop, and maintain a Pathmaker application.
Part Number 067868
Edition Fourth
Published September 1993
Product Version Pathmaker D20
Release ID D20.00
Supported Releases This manual supports D20 and all subsequent releases until otherwise indicated in a new edition.
3. New and Changed Information
The Pathmaker Programming Guide provides detailed instructions for using the
Release 3 version of the Pathmaker product. The manual includes the product
information previously located in the Pathmaker Programming Manual C30 and also
contains detailed information about product features new for this release. Several new
sections containing high-level product usage information, task check lists, and screen
summaries have also been added.
If you have already used previous versions of the Pathmaker product and want to
quickly learn about the new features and capabilities of the product for Release 3, read
the summary of new Pathmaker features included in this section. This summary is
written specifically for readers who are already very familiar with the product's basic
features. If you have not used previous versions of the Pathmaker product, it is
recommended that you read the Introduction to Pathmaker Release 3 manual first and
then read Section 1 of this guide.
The operating system for Tandem NonStop systems, formerly called the Guardian
operating system, is now called the Tandem NonStop Kernel. This change reflects
Tandem's current and future operating system enhancements that further enable open
systems and application portability.
Summary of New This summary provides a brief overview of the new features and capabilities of the
Pathmaker Features Pathmaker product for Release 3 and indicates where in the Pathmaker manual set
you can locate detailed information about the Release 3 enhancements.
New Interface to Pathmaker In addition to the full screen interface, the Pathmaker product now provides the
Catalogs Pathmaker Application Definition Language (PMADL), which is a syntax based
interface to Pathmaker catalogs. PMADL can be used to represent the contents of an
existing Pathmaker catalog in a textual form. PMADL is especially efficient for
making mass changes to a Pathmaker application and for quickly creating an
application modeled after an existing Pathmaker application. See “Managing
Pathmaker Application Development” in Section 1 for more information about using
PMADL.
New Features for The Pathmaker product for Release 3 provides many enhancements intended to
Developing a Pathmaker further simplify the creation of requesters, services, and servers; a list of these
Application enhancements follows:
Pathmaker requesters can now be produced for JET6530 terminals and PCs and
3270 terminals that support Kanji. See “Creating Requesters for Kanji Terminals”
in Section 5 for details.
The Pathmaker product can now be used to generate C language services and
servers as well as COBOL85 services and servers. C language services can even be
separately generated and compiled. See Section 4 for more information about
coding custom services using the C language.
Embedded SQL statements that implement typical database operations for a single
NonStop SQL table can be generated by the Pathmaker product. Application
developers enter detailed information about the database operations needed into
067868 Tandem Computers Incorporated iii
4. New and Changed Information
several new Pathmaker screens. The Pathmaker product uses this information to
generate SQL statements that are eventually included in the generated server
source code. The application developer writes statements in a Custom Source File
(formerly called a Transaction Copy Library) to execute the generated SQL
statements. See “Defining a Custom Service” in Section 4 for details.
The Pathmaker product provides a new macro language that uses English words,
rather than codes, making it easier to use and read. The skeletons provided with
Release 3, which are used to generate Pathmaker requesters, servers, and C
services are written in the new macro language. Any changes made to these
skeletons are made using the new language. See “Deciding Whether to Modify
Files Used for Code Generation” in Section 2 for more information.
Macros can now be registered in a Pathmaker project. Macros exist as source code
in TEDIT files. Pathmaker macros can contain code in a programming language
only (such as COBOL, C, or TAL) or can contain a combination of Pathmaker
macro language statements and programming language statements. The
registration feature provides a convenient way to document, report on, and track
code that is meant to be shared. Additional benefits of registration include the
mapping of logical name to physical file name during invocation as well as the
automatic moving of the registered files during export and import operations. See
“Preparing Shared Code for a Pathmaker Project” in Section 2 for more
information.
Two new sections, one for setup and one for cleanup, are now included in each
Custom Source File. See “Coding Custom Services” in Section 4 for more
information.
The ability to register services and servers written outside of the Pathmaker
product is provided with Release 3. Source and object code for registered services
and servers is automatically moved when a Pathmaker project is exported or
imported. Registering services also provides physical file information that allows
the Pathmaker product to generate server definitions in the Pathway configuration
file. See “Service and Server Types” in Section 4 for details.
The Pathmaker product for Release 3 can be used to create services and servers
that will be used in conjunction with clients generated with the Pathway Open
Environment Toolkit (POET). In addition, several other enhancements have been
made to the Pathmaker product to support the development of client/transaction
server applications for Tandem systems. See “Using Pathmaker for
Client/Transaction Server Application Development” in Section 1 for details.
The Pathmaker product now provides support for the new DDL JUSTIFIED
clause. See “Defining Data for a Pathmaker Project” in Section 2 for more
information.
Other internal product enhancements, such as more efficient extent sizes for the
generated source code files, dynamic memory allocation during Pathmaker
operations, and improved locking granularity during code generation are included
as part of Release 3.
iv 067868 Tandem Computers Incorporated
5. New and Changed Information
Pathmaker Full Screen Seven new screens have been added to the Pathmaker full screen interface and several
Interface Changes existing screens have been modified to support the new product features for Release 3.
Refer to the screen descriptions in the Pathmaker Reference Manual for more
information.
New Auditing Requirement The Pathmaker product for Release 3 requires that project catalogs be created on or
for Pathmaker Catalogs imported to disk volumes that are audited by the Transaction Monitoring Facility
(TMF) product. An existing Pathmaker project can be converted to Release 3 only if
the catalog for that project resides on an audited volume. Refer to the PMPROJECT
utility in the Pathmaker Reference Manual for more information.
Requirement for DEFs and The Pathmaker product requires DEFs and RECORDs used in C services to be
RECORDs Used in compiled by DDL with the CFIELDALIGN_MATCHED2 command. As a
C Services consequence of this requirement, field alignment of existing DEFs and RECORDs
could change when they are recompiled with the CFIELDALIGN_MATCHED2
command, making them incompatible with services, clients, requesters, and database
files that use old versions of the DEFs and RECORDs.
Pathmaker Utility The enhancements to the Pathmaker utilities for Release 3 are summarized in the
Enhancements following list. Refer to the appropriate utility in the Pathmaker Reference Manual for
more information.
The PMINSTAL utility has been enhanced to allow utility process configuration
for the C compiler, to provide a cleanup option for removing unneeded software
distribution subvolumes, and to properly secure the installation files.
The PMPROJECT utility allows you to specify a static execution priority for a
Pathmaker project. (Execution priority can be either static or dynamically
determined.) In addition, you can designate a swap volume for each Pathmaker
project.
The PMPROJECT utility INSTALL option now generates a master Pathway
configuration source file and subordinate source files for the target application’s
Pathway TCP, program and server object definitions. A source file that can
contain custom Pathway object definitions and commands is also generated. This
new approach allows most of an application’s Pathway configuration information
to be regenerated when changes are made to an application without disturbing the
custom Pathway object definitions and commands you have defined.
The PMPROJECT INSTALL command now uses the Pathmaker name of an initial
requester (if it is 15 characters or less) as the Program Name in the Pathway
configuration file for the generated application.
PMPROJECT now provides an INFO command that you can use to list
information about a project.
The PMPROJECT utility provides a CONVERT option that can be used to convert
a Release 2 (C20, C30, C31, or D10) Pathmaker project to Release 3 (D20). An
existing Pathmaker project can be converted to Release 3 only if the catalog for that
project resides on an audited volume.
067868 Tandem Computers Incorporated v
6. New and Changed Information
vi 067868 Tandem Computers Incorporated
7. Contents
About This Manual xix
About the Pathmaker Manual Set xxiii
Section 1 Pathmaker Tasks
Preparing for Pathmaker Application Development 1-1
Prerequisites 1-1
Task Summary 1-2
Developing a Pathmaker Application 1-3
Prerequisites 1-3
Task Summary 1-3
Managing Pathmaker Application Development 1-4
Prerequisites 1-4
Task Summary 1-4
Using Pathmaker Reports 1-4
Using Pathmaker Utilities 1-5
Using PMADL 1-5
Controlling Multiple Versions of Pathmaker 1-5
Using Pathmaker for Client/Transaction Server Application
Development 1-6
Section 2 Preparing for Pathmaker Application Development
Prerequisites 2-1
Task Summary 2-2
Installing the Pathmaker Product 2-3
Designing a Pathmaker Application 2-3
What Belongs in the Design Specification 2-3
Creating Application Prototypes 2-4
Designing Custom Services 2-5
Designing Custom Servers and Server Classes 2-5
Designing Requesters 2-9
Establishing Naming Conventions 2-12
Rules for Naming Objects in Pathmaker 2-12
Deciding Whether to Modify Files Used for Code Generation 2-19
Modifying Files Used for Requester Generation 2-19
Modifying Files Used for Service and Server Generation 2-20
067868 Tandem Computers Incorporated vii
8. Contents
Creating and Customizing a Pathmaker Project 2-21
How Many Pathmaker Projects Should You Create? 2-21
Project Size Limitations 2-21
Adding a Pathmaker Project 2-21
Ownership of a Pathmaker Project 2-22
Loading a New Project From an Existing Project 2-22
Modifying a Project 2-22
Adding User-Supplied Functions 2-23
Defining Data for a Pathmaker Project 2-24
Documenting Enscribe Data 2-25
Documenting NonStop SQL Data 2-27
Creating Additional DDL Structures 2-30
Creating the Physical Database 2-31
Describing Data to Pathmaker 2-31
Preparing Shared Code for a Pathmaker Project 2-41
Registered Macros 2-41
User Conversion Routines 2-43
Creating a Master Requester, Service, or Server 2-44
Section 3 Pathmaker Application Development Overview
Prerequisites 3-1
Before You Begin 3-2
Pathmaker Application Types 3-3
Bottom-Up versus Top-Down 3-4
How to Operate the Full Screen Interface 3-8
Creating a Custom Pathmaker Application 3-15
Creating a DB Requester Application 3-17
Limitations for DB Requester Applications 3-18
Single-File and Multifile DB Requesters 3-22
Standard Services 3-28
Restrictions for DB Requester Applications Accessing NonStop SQL
Databases 3-30
Additional Considerations for DB Requesters Accessing NonStop SQL
Tables 3-31
viii 067868 Tandem Computers Incorporated
9. Contents
Section 4 Creating Services and Servers
Service and Server Types 4-1
Standard Services and Servers 4-1
Registered Services and Servers 4-2
Custom Services and Servers 4-3
Server Type Summary 4-3
The Structure of Pathmaker Custom Services and Servers 4-4
Custom COBOL85 Servers 4-4
Custom COBOL85 Services 4-8
Custom C Servers 4-11
Defining a Custom Service 4-18
Coding Custom Services 4-21
Custom Source File 4-21
Guidelines for Custom Source Files 4-44
Invoking Macros From a Custom Source File 4-46
Additional Considerations for Coding NonStop SQL Services 4-48
File Error Handling 4-54
Generating NonStop SQL Statements 4-63
SQL Operations Screen 4-63
Operation Attributes Screen 4-64
Usage Considerations for UPDATE Operations 4-64
Usage Considerations for DELETE Operations 4-65
Usage Considerations for INSERT Operations 4-65
Usage Considerations for SELECT Operations 4-65
Usage Considerations for FETCH Operations 4-66
Defining a Custom Server 4-68
Generating Custom Servers 4-70
Server Generation Phases 4-70
C Server Generation 4-71
Files Used to Generate a Server 4-71
Registering Servers Not Created With Pathmaker 4-74
Defining Registered Services 4-74
Defining a Registered Server 4-75
Writing Requester Code to Access a Registered Service 4-75
Supplying Application Configuration Information 4-76
067868 Tandem Computers Incorporated ix
10. Contents
Section 5 Creating Requesters
Requester Development Overview 5-1
Defining the Requester and Its Screen 5-1
The Default Screen 5-2
Modifying the Default Screen 5-2
Coordinating IPC Messages and Parameters 5-3
Generating and Compiling SCREEN COBOL Source Code 5-3
Screen and Task Summaries 5-5
Requester Definition Tasks 5-8
Defining Requesters 5-8
Selecting a Requester Type 5-9
Initial Requesters 5-13
Controlling Default Screen Layout 5-15
DDL Clauses That Affect Default Screen Layout 5-15
Attributes that Affect Default Screen Layout 5-17
Modifying the Default Screen 5-31
Specifying CALL and SEND Parameters 5-32
Requester Parameters 5-33
CALL Parameters 5-34
SEND Parameters 5-36
Generating Requesters 5-41
Requester Generation Phases 5-41
Files Used to Generate a Requester 5-42
Creating DB Requesters 5-44
DB Requester Guidelines 5-44
Record Instance Detail Screen 5-44
Creating Requesters for 3270 Terminals 5-46
Creating Requesters for Kanji Terminals 5-48
Defining Data for a Kanji Application 5-48
Developing a Kanji Application 5-48
Running a Kanji Application 5-49
Considerations for the IBM 5550 Family of Terminals 5-50
x 067868 Tandem Computers Incorporated
11. Contents
Section 6 Using the Screen Painter
Screen Painter Components 6-1
Screen Elements 6-2
Paging Information 6-3
Basic Screen Painter Editing Functions 6-4
Assigning Video Attributes 6-4
Defining or Modifying a Data Field 6-5
Defining or Modifying a Paging Area 6-8
Defining or Modifying a Point Field 6-10
Defining or Modifying a Pseudofield 6-11
Deleting a Block of Screen Elements 6-13
Moving a Block of Screen Elements 6-13
Drawing a Box or Line 6-13
Moving a Page Within the Paging Area 6-14
Moving or Deleting a Screen Element 6-14
Converting a Simulated Screen to an Actual Screen 6-15
Re-Creating the Screens 6-15
Turning Decorations Into Functioning Data Fields 6-16
Section 7 Finishing and Installing the Application
Servers and Server Classes 7-4
Assigning Server Classes 7-4
Assigning an Active Server Class 7-5
Generating the Mapping Requester 7-6
Installing an Application for Testing 7-8
Running a Pathmaker Application 7-11
Installing an Application in the Production System 7-12
Steps for Installing a Production Application 7-12
Example of Installing a Production Application 7-13
Merging Pathmaker Projects 7-20
Establishing Naming Conventions 7-20
Creating the Pathmaker Projects 7-21
Merging the Pathmaker Projects 7-23
Summary of Steps for Merging Pathmaker Projects 7-30
067868 Tandem Computers Incorporated xi
12. Contents
Section 8 Maintaining Pathmaker Applications
Changing Screen Decorations or Screen Layout 8-2
Reassigning the Active Server Class for a Service 8-2
Repackaging Services Into Servers 8-4
Repackaging Services Into Existing Servers 8-4
Packaging Services Into New Servers 8-5
Adding Help Text 8-7
Adding, Modifying, or Deleting Requesters 8-8
Adding Requesters 8-8
Modifying Requesters 8-11
Deleting Requesters 8-12
Adding, Modifying, or Deleting Services 8-13
Adding New Services to New Servers 8-13
Adding New Services to Existing Servers 8-14
Modifying Services 8-14
Deleting Services 8-15
Modifying the Database 8-16
Modifying Definitions 8-16
Modifying Records 8-17
Modifying NonStop SQL Tables 8-18
Section 9 Advanced Pathmaker Programming Topics
Modifying Requesters 9-1
Using a Requester Copy Library 9-3
Sending to Servers Over a Network 9-13
Coding USER Actions 9-17
Creating User Conversion Routines 9-22
Editing T9154CPY 9-24
Modifying the Requester Skeleton 9-30
Modifying a Server Skeleton or Service Skeleton 9-32
Adding SPECIAL-NAMES Entries for COBOL Servers 9-33
Including Additional Libraries for C Services 9-33
Rewriting and Reformatting Existing Error Messages 9-33
Changing the Maximum Number of Requesting Processes 9-38
Inserting Global COBOL Service Procedures 9-40
Modifying the COBOL Server Skeleton for NonStop SQL
Applications 9-41
Modifying PMSVCULC for C NonStop SQL Applications 9-47
xii 067868 Tandem Computers Incorporated
13. Contents
Modifying the SQL Generation Macro 9-52
Modifying Requester/Server Pairs 9-54
Using Pathmaker Pseudofields 9-54
Using Reason Codes (T9154-REASON-CODE) 9-59
Creating Screens That Display Lists 9-60
Section 10 Sample Pathmaker Sessions
Creating a Simple Application 10-1
Summary of Application Creation Steps 10-3
Application Creation Steps 10-4
Creating a Custom Application 10-18
Summary of Application Creation Steps 10-20
Application Creation Steps 10-22
Creating a NonStop SQL Pathmaker Application 10-34
Summary of Application Creation Steps 10-36
Application Creation Steps 10-38
Appendix A Reference Summary
Appendix B How to Operate a DB Requester Application
Reading Rows B-1
READ FIRST (F4) B-2
READ NEXT (F5) B-2
READ APPROXIMATE (F6) B-3
READ EXACT (F7) B-4
READ GENERIC (F8) B-5
Inserting Rows B-7
INSERT (F10) B-7
INSERT BOX B-9
Deleting Rows B-12
DELETE (F12) B-12
DELETE BOX B-12
DELETE Considerations for Applications With Several Boxes B-13
Updating Rows B-14
UPDATE (F14) B-14
UPDATE BOX B-14
UPDATE Considerations for Applications With Several Boxes B-15
067868 Tandem Computers Incorporated xiii
14. Contents
Undoing an INSERT, DELETE, or UPDATE (Shifted F13) B-16
Undoing a DELETE Operation B-16
Undoing an UPDATE Operation B-16
Undoing an INSERT Operation B-16
Operator Display and Error Messages B-17
Terminal Function Keys B-18
Appendix C Defining Data for a NonStop SQL Pathmaker Application
Using Null Values C-1
General Guidelines for Using Null Values C-2
Using Null Values in Database Requesters C-4
Using Null Values in Transaction Requesters C-8
Using Clustering Keys C-9
Using Date and Time Data Types C-10
Index Index–1
Figures Figure 2-1. Linkage for User-Supplied Functions 2-23
Figure 2-2. Macro Example 2-43
Figure 3-1. Creating Pathmaker Applications Bottom-Up 3-5
Figure 3-2. Creating Pathmaker Applications Top Down 3-7
Figure 3-3. Accessing Pathmaker Projects 3-9
Figure 3-4. Pathmaker Main Menu 3-11
Figure 3-5. Creating a Custom Pathmaker Application 3-16
Figure 3-6. Tasks for Creating DB Requester Applications 3-17
Figure 3-7. DB Requester Application Screen 3-18
Figure 3-8. Application Screen Based on a Single-File DB Requester 3-23
Figure 3-9. Application Screen Based on a Multifile DB Requester 3-24
Figure 3-10. Alternate Default Screen Layout for a Multifile DB
Requester 3-27
Figure 4-1. Structure of a Pathmaker COBOL85 Server Procedure
Division 4-6
Figure 4-2. COBOL85 Server Generation for NonStop SQL 4-7
Figure 4-3. Contents of a COBOL85 Custom Service 4-9
Figure 4-4. Structure of a Pathmaker C Server 4-12
xiv 067868 Tandem Computers Incorporated
15. Contents
Figure 4-5. C Server Generation for NonStop SQL 4-14
Figure 4-6. Contents of a Generated C Service 4-16
Figure 4-7. C Service Generation and Compilation for NonStop SQL 4-17
Figure 4-8. Custom Source File COBOL85 Sample Code 4-32
Figure 4-9. Custom COBOL85 Server Sample Code 4-33/34
Figure 4-10. Example of Invoking a Registered Macro 4-47
Figure 4-11. Generating INVOKE Statements for IPCs 4-49
Figure 4-12. Generating Host Variables 4-51
Figure 4-13. Generating and Compiling a Pathmaker Custom Server
(NonStop SQL) 4-72
Figure 4-14. Generating and Compiling a Pathmaker COBOL85 Custom
Server (Enscribe) 4-73
Figure 5-1. Generating and Compiling a Pathmaker Requester 5-4
Figure 5-2. Recommended Use of REG Requesters 5-12
Figure 5-3. Two Uses of an Initial Requester 5-14
Figure 5-4. Sample MENU Requester Application Screen 5-22
Figure 5-5. Sample TRNS Requester Application Screen 5-23
Figure 5-6. Sample DB Requester Application Screen 5-30
Figure 5-7. SCREEN COBOL for Requester Parameters 5-33
Figure 5-8. CALL Parameter Mapping 5-35
Figure 5-9. Sample SCREEN COBOL Code for Requester Calls 5-36
Figure 5-10. SEND Parameter Mapping 5-39
Figure 5-11. Sample SCREEN COBOL and COBOL Code for Invoking a
Service 5-40
Figure 5-12. Files Used to Generate a Requester 5-43
Figure 5-13. Sample TRNS Requester for 3270 5-46
Figure 7-1. Service to Server to Server Class Mapping 7-5
Figure 7-2. Code Resolving Server Class 7-7
Figure 7-3. Creating a Single Application Using Multiple Projects 7-22
Figure 9-1. Requester Copy Library Sample Code 9-12
Figure 10-1. Screens for a Simple Pathmaker Application 10-2
Figure 10-2. Requester Definition Screen 10-5
Figure 10-3. Application Screen Viewed Through Screen Painter 10-7
Figure 10-4. Requester Definition Screen 10-8
067868 Tandem Computers Incorporated xv
16. Contents
Figure 10-5. Record Instance Detail Screen 10-10
Figure 10-6. Application Screen Viewed Through Screen Painter 10-12
Figure 10-7. Requester Definition Screen 10-13
Figure 10-8. Function Key Assignments - 6520/6530 Screen 10-14
Figure 10-9. Application Screen Viewed Through Screen Painter 10-15
Figure 10-10. Screens for a Sample Pathmaker Session 10-18
Figure 10-11. SEND Parameter Definition Screen 10-26
Figure 10-12. SEND Parameter Definition Screen 10-27
Figure 10-13. SEND Parameter Definition Screen 10-28
Figure 10-14. Screens for a Sample NonStop SQL Pathmaker Session 10-34
Figure 10-15. Display Field List Screen 10-43
Figure 10-16. Application Screen Viewed Through Screen Painter 10-44
Figure 10-17. SEND Parameter Definition Screen 10-45
Figure 10-18. SEND Parameter Definition Screen 10-46
Figure 10-19. Display Field List Screen 10-48
Figure 10-20. Display Field List Screen 10-49
Figure 10-21. Application Screen Viewed Through Screen Painter 10-50
Figure 10-22. SEND Parameter Definition Screen 10-51
Figure A-1. Pathmaker Screen Map (Page 1 of 3) A-2/4
Figure B-1. Inserting a Record in a Nested Box B-8
Figure B-2. Example of INSERT BOX Operation for Multiple Repetitions in
a Single Box B-10
Figure B-3. INSERT BOX Operation for a Nested Box B-11
Tables Table 2-1. Preparing For Pathmaker Application Development—Task
Summary 2-2
Table 2-2. Logical and Disk File Name Examples 2-17
Table 2-3. SQL Constraints and Pathmaker MUST BE Checks 2-28
Table 2-4. Related NonStop SQL Data Definition Language Features 2-28
Table 2-5. Related Enscribe DDL Clauses 2-33
Table 2-6. Related Enscribe DDL Commands 2-35
Table 2-7. Pathmaker Screens for Defining Data 2-40
Table 2-8. Pathmaker Screens for Registered Macros 2-42
Table 3-1. Pathmaker Informational Screens 3-14
xvi 067868 Tandem Computers Incorporated
17. Contents
Table 3-2. Summary of Standard Services 3-29
Table 4-1. Custom Application Service Check List 4-19
Table 4-2. Pathmaker Screens for Creating Custom Services 4-20
Table 4-3. Pathmaker Common Service Utility Library 4-24/28
Table 4-4. Video Attributes for Advisory Messages 4-31
Table 4-5. Enscribe File Error Messages 4-55
Table 4-6. Common NonStop SQL Messages 4-59/61
Table 4-7. Pathmaker Screens for Creating Custom Servers 4-69
Table 4-8. Custom Application Server Check List 4-69
Table 5-1. Pathmaker Screens for Creating Requesters 5-5
Table 5-2. Custom Application Requester Check List 5-6
Table 5-3. DB Requester Application Check List 5-7
Table 5-4. Requester Type Summary 5-10
Table 5-5. DDL Clauses Affecting Default Screen Layout 5-15
Table 5-6. Attributes Affecting Default Screens 5-17
Table 5-7. Function Key Assignments for IBM 3270 Terminals 5-47
Table 7-1. Pathmaker Screens for Completing and Installing an
Application 7-2
Table 7-2. Files Produced by PMPROJECT INSTALL 7-9/10
Table 9-1. Files Used to Modify Requesters 9-2
Table 9-2. Requester Copy Library Sections 9-5/7
Table 9-3. Accessible Pathmaker Variables and Paragraphs 9-8
Table 9-4. Pathmaker Pseudofields 9-55
Table A-1. Preparing For Pathmaker Application Development—Task
Summary A-5
Table A-2. Pathmaker Screens for Defining Data A-6
Table A-3. Pathmaker Screens for Registered Macros A-6
Table A-4. Pathmaker Informational Screens A-7
Table A-5. Summary of Standard Services A-8
Table A-6. Custom Application Service Check List A-9
Table A-7. Pathmaker Screens for Creating Custom Services A-10
Table A-8. Pathmaker Common Service Utility Library A-11/15
Table A-9. Pathmaker Screens for Creating Custom Servers A-16
Table A-10. Custom Application Server Check List A-16
067868 Tandem Computers Incorporated xvii
18. Contents
Table A-11. Pathmaker Screens for Creating Requesters A-17
Table A-12. Custom Application Requester Check List A-18
Table A-13. DB Requester Application Check List A-19
Table A-14. Pathmaker Screens for Completing and Installing an
Application A-20
Table B-1. Example of Enscribe Records Returned for READ
GENERIC B-6
Table B-2. Standard Services Summary B-19
Table C-1. Default Null Value Display Characters for DB Requesters C-7
xviii 067868 Tandem Computers Incorporated
19. About This Manual
The Pathmaker product is a tool that assists in the creation of Pathway applications for
computer systems that use the Tandem NonStop Kernel. The Pathmaker Programming
Guide is a comprehensive task-oriented guide for the effective use of the Pathmaker
product. The Pathmaker Programming Guide provides not only instructions for creating
applications with the Pathmaker product, but also guidelines and procedures for
preparing for and a controlling Pathmaker application development effort.
Objectives of This Given this manual, readers will be able to:
Manual
Locate instructions for installing the Pathmaker product.
Design an application to be implemented with the Pathmaker product.
Establish naming conventions and other standards.
Create a thorough application design document containing all of the essential
information that application developers need to know before creating an
application with the Pathmaker product.
Locate instructions for creating Pathmaker projects.
Customize a Pathmaker project.
Prepare and register shared application code.
Create a Pathmaker application.
Install a Pathmaker application for testing.
Create and use Pathmaker reports.
Know when and why to use the Pathmaker utilities and the Pathmaker
Application Definition Language (PMADL).
Install a Pathmaker application into production.
Customize the application online help.
Maintain a Pathmaker application.
Audience The Pathmaker Programming Guide is designed for anyone directly involved in a
Pathmaker application development effort, including individuals who design, plan,
create, maintain, or install Pathmaker applications.
To successfully complete a Pathmaker application development effort using the
detailed information in the Pathmaker Programming Guide, those involved must possess
a variety of prerequisite skills. All participants should understand the information
presented in the Introduction to Pathmaker manual, including basic Pathway and
Pathmaker concepts and terminology, and should know how to use Tandem utilities
such as TEDIT, FUP, and PERUSE.
Individuals who are designing a Pathmaker application should already understand
Pathway requester-server application design principles and how Pathway applications
created with the Pathmaker product are structured.
067868 Tandem Computers Incorporated xix
20. About This Manual
Application developers who are creating services and servers for a Pathmaker
application must already know how to code in COBOL85 or C, and NonStop SQL, if
applicable. They must also know how to test and debug a Pathway server. If
additional code is to be incorporated into a Pathmaker requester, application
developers must know how to write and debug SCREEN COBOL code.
Individuals who are responsible for setting up a Pathmaker project, managing the
development effort, or installing the application for testing or production must have a
thorough knowledge of Pathway and the Data Definition Language (DDL) in addition
to the prerequisite skills listed for application developers.
Organization of This The Pathmaker Programming Guide is divided into ten sections and three appendixes.
Manual These are:
Section 1—Pathmaker Tasks
Section 2—Preparing for Pathmaker Application Development
Section 3—Pathmaker Application Development Overview
Section 4—Creating Services and Servers
Section 5—Creating Requesters
Section 6—Using the Screen Painter
Section 7—Finishing and Installing the Application
Section 8—Maintaining Pathmaker Applications
Section 9—Advanced Pathmaker Programming Topics
Section 10—Sample Pathmaker Sessions
Appendix A—Reference Summary
Appendix B—How to Operate a DB Requester Application
Appendix C—Defining Data for a NonStop SQL Pathmaker Application
Section 1, “Pathmaker Tasks,” presents an overview of the major tasks performed
during a Pathmaker application development effort. This section is especially helpful
to anyone using the Pathmaker product for the first time. The details required to
complete the tasks outlined here are provided in the remainder of this manual and in
the Pathmaker Reference Manual.
Section 2, “Preparing for Pathmaker Application Development,” describes the tasks
that should be completed and itemizes the issues that need to be addressed while
planning and setting up a Pathmaker application development effort. Details about
the activities performed to prepare for a Pathmaker application development effort
such as designing a Pathmaker application, naming Pathmaker objects, and creating
shared code are presented. The portions of the Pathmaker product used for each of
these activities are identified. This information is of interest to individuals who are
responsible for organizing a development effort or designing a Pathmaker application.
xx 067868 Tandem Computers Incorporated
21. About This Manual
Section 3, “Pathmaker Application Development Overview,” provides an overview of
the tasks that must be completed to create and maintain a Pathmaker application. This
section is of interest to individuals who are responsible for implementing and
maintaining a Pathmaker application.
Section 4, “Creating Services and Servers,” describes in detail how to create Pathmaker
custom services and servers and includes directions for using Pathmaker to generate
SQL data manipulation statements. This section is of interest to individuals who are
responsible for creating or designing services and servers for a Pathmaker application.
Section 5, “Creating Requesters,” describes in detail how to create and generate
Pathmaker requesters, including how to integrate requesters and services. This section
is of interest to individuals who are responsible for creating or designing requesters
for a Pathmaker application.
Section 6, “Using the Screen Painter,” describes in detail how to use the Pathmaker
Screen Painter. This section is of interest to individuals who are responsible for
creating or designing requesters for a Pathmaker application.
Section 7, “Finishing and Installing the Application,” describes in detail how to
complete a Pathmaker application after the application developers have created the
services, servers, and requesters for the application. This section is of interest to
individuals who are responsible for preparing a Pathmaker application for testing.
Section 8, “Maintaining Pathmaker Applications,” describes procedures for some of
the most common changes that an application developer would make to an existing
Pathmaker application. This section is of interest to individuals who are responsible
for maintaining a Pathmaker application.
Section 9, “Advanced Pathmaker Programming Topics,” describes the details of
several advanced Pathmaker programming tasks including creating a requester copy
library, changing a Pathmaker skeleton, and providing national language support.
Section 10, “Sample Pathmaker Sessions,” illustrates how to use Pathmaker to create
three small applications.
Appendix A, “Reference Summary,” contains the screen map for the Pathmaker
screens and several summary charts and check lists from the body of this manual.
Application developers are encouraged to print this appendix and use it as a quick
reference while using the Pathmaker product.
Appendix B, “How to Operate a DB Requester Application,” explains how to operate a
Pathmaker application created with DB requesters and standard services. This
appendix is of interest to designers and end users of such applications.
Appendix C, “Defining Data for a NonStop SQL Pathmaker Application,” contains
information about how a Pathmaker application interacts with NonStop SQL columns
that allow null values, and about using clustering keys and date and time data types in
a NonStop SQL Pathmaker application.
067868 Tandem Computers Incorporated xxi
22. About This Manual
How to Use This If you are new to the Pathmaker product, you should read Section 1, “Pathmaker
Manual Tasks” for an overview of the major tasks performed during a Pathmaker application
development effort. Then use the appropriate sections of this manual, the online help,
and the Pathmaker Reference Manual to learn how to complete the tasks for which you
are responsible. You are encouraged to make copies of the check lists and summaries
included in Appendix A and use these to track your progress.
If you have used previous releases of the Pathmaker product, you already know most
of the information presented in this manual. If so, it is recommended that you consult
the New and Changed Information section of this manual for an overview of the new
product features and for the locations in the Pathmaker manual set of detailed
information about these features and capabilities.
xxii 067868 Tandem Computers Incorporated
23. About This Manual
About the Pathmaker The Pathmaker manual set for Release 3 consists of four Pathmaker manuals. Figure 1
Manual Set is a documentation map that shows how the Pathmaker manuals are related to each
other and to other Tandem manuals. The map, read from the top down, indicates the
order in which the manuals should be read. Manuals grouped by brackets are
corequisites.
Figure 1. Documentation Map
Introduction to
Pathmaker
Pathmaker
Programming
Guide
Pathmaker Pathmaker
Reference Messages
Manual Manual
COBOL85 DDL Enform Guardian
Reference Reference Manuals User's Guide
Manual Manual
C NonStop SQL Pathway
Reference Manuals Manuals
Manual
000
067868 Tandem Computers Incorporated xxiii
24. About This Manual
The following chart explains the purpose of each Pathmaker Release 3 manual and its
intended audience:
Pathmaker Manual Description Audience
Introduction to Pathmaker Provides a comprehensive Anyone who needs an
introduction to the Pathmaker overview of the product,
product. This manual explains how including all individuals
an application created with the involved in a Pathmaker
Pathmaker product looks and application development
behaves, defines basic Pathmaker effort.
terminology, and suggests several
general approaches for successfully
using the product. In addition, basic
information about Pathway and
online transaction processing
(OLTP) is included. The
information in this manual provides
the foundation needed to effectively
use the other manuals in the
Pathmaker manual set.
Pathmaker Programming Provides a comprehensive task- Individuals who are directly
Guide oriented guide for the effective use involved in a Pathmaker
of the Pathmaker product. This application development
manual explains, in detail, how to effort.
use the Pathmaker full screen
interface, how to design, develop,
and maintain a Pathmaker
application, and how to prepare for
and manage a Pathmaker
application development effort.
Pathmaker Reference Provides detailed descriptions of all Pathmaker users who need
Manual Pathmaker screens, Pathmaker detailed information about
utilities, the Pathmaker Application Pathmaker screens,
Definition Language (PMADL), and Pathmaker utilities, PMADL,
the macro language. Pathmaker or the macro language.
screen descriptions are arranged
alphabetically by screen title and
include details about screen fields
and function keys. Descriptions of
Pathmaker utilities, PMADL, and
the macro language include syntax
diagrams and usage information.
Pathmaker Messages Provides an alphabetical list of the Pathmaker users who need
Manual Pathmaker messages, explaining assistance in understanding
the cause of the message, the a Pathmaker message.
effect of the error, and suggestions
for recovery.
xxiv 067868 Tandem Computers Incorporated
25. About This Manual
Related Manuals The Pathmaker product interacts with several other Tandem products. In addition to
the Pathmaker manuals, you might need these other Tandem manuals when using the
Pathmaker product:
COBOL85 Reference Manual
C Reference Manual
Data Definition Language (DDL) Reference Manual
Enform Manuals
Enform User’s Guide
Enform Reference Manual
Guardian User’s Guide
NonStop SQL Manuals
Pathway Manuals
Pathway Application Programming Guide
Pathway SCREEN COBOL Reference Manual
Pathway System Management Guide
Your Comments Are After you have had a chance to use this manual, please take a moment to fill out the
Invited Reader Comment Card at the back and send it in. Your comments will be used to
improve future editions of the Pathmaker Programming Guide.
067868 Tandem Computers Incorporated xxv
27. Notation Conventions
The following list summarizes the conventions for syntax presentation in this manual.
Notation Meaning
UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these
items exactly as shown.
lowercase italic letters Lowercase italic letters represent variable items that you supply.
Brackets [ ] Brackets enclose optional syntax items. A group of vertically aligned
items enclosed in brackets represents a list of selections from which you
can choose one or none.
Braces { } Braces enclose required syntax items. A group of vertically aligned
items enclosed in braces represents a list of selections from which you
must choose one.
Vertical line | A vertical line separates alternative syntax items in a horizontal list.
Such a list, enclosed in either brackets or braces, is an alternative to a
vertical list for presenting selections.
Ellipsis ... An ellipsis immediately following a pair of brackets or braces indicates
that you can repeat the enclosed syntax items any number of times.
Percent sign % A percent sign precedes a number that is not in decimal notation.
% indicates octal notation. %B indicates binary notation. %H indicates
hexadecimal notation. (%D at the end of a hexadecimal value denotes
double precision. %F at the end of a hexadecimal value denotes a fixed
numeric constant.)
I and O In procedure calls, input parameters (those passing data to the called
procedure) are followed by an I; output parameters (those that return
data to the calling program) are followed by an O.
Spaces If a space separates two items, that space is required. If one of the
items is a punctuation symbol, such as a parenthesis or a comma,
spaces are optional.
Punctuation Parentheses, commas, semicolons, and other symbols not described
above must be entered precisely as shown. Quotation marks around
any symbol indicate that it is not a syntax descriptor but a required
character, and you must enter it as shown.
067868 Tandem Computers Incorporated xxvii
28. 1 Pathmaker Tasks
This section presents an overview of the three major groups of tasks performed during
a Pathmaker application development effort. These tasks are based upon the
suggested life cycle for a Pathmaker application outlined in the Introduction to
Pathmaker manual. Some of the tasks listed here are optional, others are required.
Which optional tasks you choose to perform depends upon the complexity of the
application being implemented, the experience level of the application developers
working on the project, and the requirements of your organization. After reading this
section you should have a clear idea of the flow of a typical Pathmaker application
development effort. The details required to complete the tasks outlined in this section
are provided in the remainder of this manual and in the Pathmaker Reference Manual.
This section also briefly discusses using the Pathmaker product during the
development of client/transaction server applications for a Tandem system.
Preparing for There are several major tasks that should be completed during preparation for a
Pathmaker Application Pathmaker application development effort. These tasks, summarized in this
Development subsection, are discussed in detail in Section 2 of this manual, “Preparing for
Pathmaker Application Development.”
Prerequisites Individuals preparing for a Pathmaker application development effort should be
familiar with the following Tandem products:
Data Definition Language (DDL)
Pathway
COBOL85 or C
NonStop SQL or Enscribe
Enform, FUP, PERUSE, TEDIT, SCUP
In addition the following skills and knowledge are needed:
Understanding of the architecture of applications produced using the Pathmaker
product and the concept of a Pathmaker project, as described in the Introduction to
Pathmaker manual.
Ability to design a Pathway application.
Tandem recommends that individuals who are new to the Pathmaker product should
use the product to develop a simple test application before designing a production
application or planning a production application development effort. Developing a
simple test application provides an opportunity for you to look at the source code that
the Pathmaker product generates, to understand what information an application
developer needs to most efficiently use the product, and to decide how Pathmaker
projects should be customized for your particular development environment.
067868 Tandem Computers Incorporated 1–1
29. Pathmaker Tasks
Preparing for Pathmaker Application Development
Task Summary To prepare for a Pathmaker application development effort, complete these tasks:
Install the Pathmaker software
Design a Pathmaker application
Decide whether to modify the Pathmaker files used for code generation (optional)
Create and customize a Pathmaker project
Create one or more Pathmaker projects
Load a new project catalog from an existing catalog (optional)
Add user-supplied functions (optional)
Define data for the project
Prepare shared code (optional)
Create a master service, server, or requester to be copied (optional)
Task check lists are provided in this manual to help you track the progress of and
record information about these preparation tasks.
1–2 067868 Tandem Computers Incorporated
30. Pathmaker Tasks
Developing a Pathmaker Application
Developing a The development tasks for a Pathmaker application and the skills needed to complete
Pathmaker Application those tasks are summarized in this subsection. These tasks are outlined in greater
detail in Section 3, “Pathmaker Application Development Overview.” Sections 4, 5, 6,
7, 8, and 9 of this manual contain detailed instructions for completing the tasks in this
group.
Prerequisites Individuals using Pathmaker to develop an application should understand:
Basic Pathway and Pathmaker concepts
The architecture of applications produced using the Pathmaker product
The concept of a Pathmaker project
These topics are described in the Introduction to Pathmaker manual.
They should be able to code using COBOL85 or C, and NonStop SQL, if applicable. In
addition, they should be able to use Enform, FUP, PERUSE, TEDIT, Inspect, and
SCUP.
It is recommended that application developers who are new to the Pathmaker product
use the product to develop a simple test application before creating a production
application.
Task Summary To develop a Pathmaker application, complete these tasks:
Develop services (for custom applications only)
Develop servers (for custom applications only)
Develop requesters
Use the Screen Painter (optional)
Finish the application and install it for testing
Maintain the application
Task check lists and Pathmaker screen summaries are provided in other sections of
this manual to help you track the progress of application development.
067868 Tandem Computers Incorporated 1–3
31. Pathmaker Tasks
Managing Pathmaker Application Development
Managing Pathmaker Some of the most common tasks involved in managing a Pathmaker application
Application development effort are summarized in this subsection. Details about how to
Development accomplish these tasks appear in various places in the Pathmaker manual set and are
identified in this section.
Prerequisites Individuals managing a Pathmaker application development effort should be familiar
with the following Tandem products:
Pathway
Enform, FUP, PERUSE, TEDIT, SCUP
In addition, individuals managing a Pathmaker application development effort
should understand:
Basic Pathway and Pathmaker concepts
The architecture of applications produced using the Pathmaker product
The concept of a Pathmaker project
These topics are described in the Introduction to Pathmaker manual.
Task Summary Tasks for effectively managing a Pathmaker application development effort can
include:
Using the Pathmaker reports
Using the Pathmaker utilities
Starting and stopping Pathmaker projects
Determining project status
Reconfiguring projects
Converting a Pathmaker project to Release 3
Moving the development environment
Using the Pathmaker Application Definition Language (PMADL)
Merging Pathmaker projects (see Section 7 of this manual for details)
Installing an application in the production environment (see Section 7 of this
manual for details)
Controlling multiple versions of Pathmaker
Using Pathmaker Reports The Pathmaker product supplies a set of Enform queries that you can use to produce
reports about the contents of a Pathmaker project catalog. These reports were
designed to allow you to examine different subsets of information found in a
Pathmaker project catalog. For example, one of the queries lists all the help text
associated with a particular requester, another shows all the DDL records and
NonStop SQL tables referred to by services in a project, and another shows the
generation status of every server in a project catalog.
1–4 067868 Tandem Computers Incorporated
32. Pathmaker Tasks
Managing Pathmaker Application Development
These reports can provide valuable information during the development of a
Pathmaker application and can also be used to produce documentation when a
Pathmaker application development effort has been completed. For a detailed
description of each Enform query provided with the Pathmaker product and
information about how to use the queries to produce reports, refer to the project
catalog information in the Pathmaker Reference Manual.
Using Pathmaker Utilities The Pathmaker product includes three Pathmaker utilities. These are:
PMINSTAL, which is used to install the Pathmaker product on a development
system
HELPUTIL, which can be used to modify help text for a completed Pathmaker
application
PMPROJECT, which is used to manage Pathmaker projects
Individuals who are responsible for managing a Pathmaker application development
effort use PMPROJECT often. The PMPROJECT utility is used to manage a Pathmaker
project, which is a running Pathway system.
The PMPROJECT utility can be used to perform a variety of tasks, including adding a
Pathmaker project, listing project attributes, altering project attributes, and starting,
restarting, and downing a Pathmaker project. Refer to the utilities information in the
Pathmaker Reference Manual for complete details about using the PMINSTAL utility, the
HELPUTIL utility, and the PMPROJECT utility.
Using PMADL In addition to the full screen interface, the Pathmaker product provides the Pathmaker
Application Definition Language (PMADL), which is a syntax based interface to
Pathmaker catalogs. PMADL can be used to represent the contents of an existing
Pathmaker catalog in a textual form. PMADL is especially efficient for making mass
changes to a Pathmaker application and for quickly creating an application modeled
after an existing Pathmaker application.
Refer to the PMADL section of the Pathmaker Reference Manual for details about using
PMADL.
Controlling Multiple You can install more than one version of the Pathmaker product on a system. Having
Versions of Pathmaker multiple Pathmaker versions lets application developers create new applications with
the most recent version and maintain existing applications in the version with which
they were developed.
If more than one version of the Pathmaker software is on a development system, the
release number should be specified each time the Pathmaker full screen interface,
PMADL, or a Pathmaker utility is invoked. For example, an application developer
who is maintaining a Pathmaker application developed with the C30 version of the
Pathmaker software would enter the following command to access the C30 version of
the Pathmaker full screen interface for the Pathmaker project named MYPROJECT:
2> PATHMAKER /RELEASE C30/ MYPROJECT
067868 Tandem Computers Incorporated 1–5
33. Pathmaker Tasks
Using Pathmaker for Client/Transaction Server Application Development
If no release number is specified, the most recent version is invoked. Ensure that
application developers are told which version of the Pathmaker software they should
use.
Refer to the Utilities section of the Pathmaker Reference Manual for details about using
the PMINSTAL utility to install more than one version of the Pathmaker software.
One of the Enform queries provided with the Pathmaker product can be used to
produce a report that lists all of the Pathmaker versions found on a system. Refer to
the Project Catalog section of the Pathmaker Reference Manual for information about this
query.
Note The Pathmaker product, versions 1 and 2, are not supported on D20 systems. You must convert all
projects to Release 3 of the Pathmaker product if you are running D20 Tandem software. Versions 1 and
2 will continue to be supported on their previous releases until Tandem discontinues support for the
release as a whole.
Using Pathmaker for If you are creating client/transaction server applications for a Tandem system, you can
Client/Transaction use the Pathmaker product to create the servers for the application. The clients for the
Server Application application can be created manually or with a number of products.
Development
A Tandem product that can be used to create clients is the Pathway Open
Environment Toolkit (POET). POET is a set of programs and utilities that enable you
to create clients and run client/transaction server applications on a Tandem system.
The C31 version and D20 versions of the Pathmaker product have been enhanced to
work in conjunction with POET; however, you do not need POET to use the
Pathmaker product.
If you are using the Pathmaker product in conjunction with POET, you are mainly
interested in the portions of the Pathmaker product used to:
Define the application data (see “Defining Data for a Pathmaker Project” in
Section 2)
Create services and servers (see Section 4)
Define the IPC messages (see Section 4)
Supply application configuration information (see Section 7)
Consult the Pathway Open Environment Toolkit (POET) Programming Manual for more
information about using the Pathmaker product with POET.
1–6 067868 Tandem Computers Incorporated
34. 2 Preparing for Pathmaker
Application Development
Proper design, planning, and setup are critical to the ultimate success of a Pathmaker
application. This section describes the tasks that should be completed and itemizes the
issues that need to be addressed while preparing for a Pathmaker application
development effort. This section is of interest to you if you are responsible for
organizing a development effort or for designing a Pathmaker application.
Prerequisites Individuals preparing for a Pathmaker application development effort should be
familiar with the following Tandem products:
Data Definition Language (DDL)
Pathway
COBOL85 or C
NonStop SQL or Enscribe
Enform, FUP, PERUSE, TEDIT, SCUP
In addition the following skills and knowledge are needed:
Understanding of the architecture of applications produced using the Pathmaker
product and the concept of a Pathmaker project, as described in the Introduction to
Pathmaker manual.
Ability to design a Pathway requester-server application.
Naming conventions for Pathmaker objects (services, requesters, and so on).
Details are in this section.
Note Anyone new to the Pathmaker product should use the product to develop a test application before
designing a production application or planning a production application development effort. Developing a
test application provides an opportunity for you to thoroughly understand the process of creating
Pathmaker services, servers, and requesters, to look at the source code that the Pathmaker product
generates, to understand what information an application developer needs to most efficiently use the
product, and to decide how Pathmaker projects should be customized for your particular development
environment. Refer to Section 3 of this manual for an overview of Pathmaker application development.
067868 Tandem Computers Incorporated 2–1
35. Preparing for Pathmaker Application Development
Task Summary
Task Summary Table 2-1 summarizes the preparation tasks for a Pathmaker application development
effort. Some of these tasks are required, the remainder are optional and provide ways
for you to customize Pathmaker projects to meet your particular requirements. These
tasks are discussed in detail in this section.
A combination of the Pathmaker utilities, the Pathmaker full screen interface, the
Pathmaker Application Definition Language (PMADL), and other Tandem products is
used to complete the tasks. (This list applies to application development efforts where
the database has already been designed.)
Table 2-1. Preparing For Pathmaker Application Development—Task Summary
Task Tools Additional References Required ?
Install Pathmaker product PMINSTAL utility Pathmaker Reference Yes
Manual, Utilities section
Design application Screen Painter, Section 6 of this manual Yes
Simulation
Modify code generation files Pathmaker macro Pathmaker Reference No
language, Manual, Macro Language
TEDIT section
Create Pathmaker project PMPROJECT utility (ADD Pathmaker Reference Yes
subcommand) Manual, Utilities section
Add user-supplied functions None None No
Define data TEDIT, Data Definition Language Yes
DDL (through the (DDL) Reference Manual,
Pathmaker Full Screen NonStop SQL Reference
Interface) Manual
SQL Table Registration
screen and Table Access
Paths screen
Prepare shared code TEDIT, Pathmaker Reference No
Pathmaker macro Manual, Macro Language
language or other host section and Screens
language, section
Macro Registration, and
Macro Syntax screens
Create master service, Service, server, and Sections 4, 5, and 6 of No
server, requester requester definition this manual
screens
The remainder of this section provides detailed information about these tasks.
2–2 067868 Tandem Computers Incorporated
36. Preparing for Pathmaker Application Development
Designing a Pathmaker Application
Installing the One of the first tasks that should be completed while preparing for a Pathmaker
Pathmaker Product 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 Producing a thorough application design is an important part of preparing for a
Pathmaker Application 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 The following items should be included in the design specification for a Pathmaker
Specification 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
067868 Tandem Computers Incorporated 2–3
37. Preparing for Pathmaker Application Development
Designing a Pathmaker Application
Requester Information
The description of the requesters for an application should include:
Chart of the application screen hierarchy
Type of terminal where the application will be run (6520, 6530, 3270, or terminals
that accept Kanji characters)
Description of requester, including requester type, requester name, picture of the
screen layout, including function keys, and name of the service or requester a
function key accesses
Name of a master requester to copy (if applicable)
Name of modified requester skeleton to use (if applicable)
For a DB requester application, a very brief design specification is usually sufficient;
however, for a custom Pathmaker application, the design specification should also
include the items listed in the next subsection.
Custom Service and Server Information
The description of the services and servers for a custom application should include:
Programming language to be used (COBOL85 or C)
Whether TMF is to be used for all services
Descriptions of services, including service name, its function, IPC message content,
and names of files and tables accessed
Name of master service to copy (if applicable)
Name of modified C service skeleton to use (if applicable)
Name of modified server skeleton to use (if applicable)
Description of servers, including server name, which services to include, and
related server class name
Whether the Pathmaker product is to be used be used to generate SQL statements
Creating Application The Screen Painter and simulation features of the Pathmaker product are very effective
Prototypes tools for previewing the screens of a proposed application, but end users might also
want to preview some of the functionality of an application being designed. One of
the best ways you can demonstrate application functionality is to create a prototype of
a proposed application. A prototype is a simplified working model on which a custom
application will be based. A prototype is not intended for use in production.
Using Pathmaker DB requesters and the standard services and servers provided with
the product, you can quickly create a working prototype that demonstrates basic
application functionality such as adding, updating, and deleting information in a
database.
2–4 067868 Tandem Computers Incorporated
