Pathmaker Programming Guide

Defining Data for a Pathmaker Project
Preparing for Pathmaker Application Development
2–30 067868 Tandem Computers Incorporated
The advantage of this approach is that it provides a single location where all data used
by the application is described.
If you want to create both a file containing NonStop SQL data definition statements
and a file containing Enscribe DDL statements, there are several approaches that can
be used. You must make sure, however, that the data is defined consistently in both
places.
Additional Information for NonStop SQL Applications
Appendix C lists additional considerations for designing data for a Pathmaker
application that accesses a NonStop SQL database. Refer to this appendix if you are
creating an application that accesses NonStop SQL tables.
Creating Additional DDL
Structures
If you design a screen that does not closely resemble an existing DDL definition or
record or a row in a table, you will probably want to create a DDL definition for it. For
example, if you want to create a screen that lists employees, you will want to create a
DDL definition using the OCCURS clause.
Suppose that the existing DDL definition looks like this:
DEF employee.
02 emp-last-name TYPE last-name.
02 emp-first-name TYPE first-name.
02 emp-num TYPE emp-num.
02 dept-num TYPE dept-num.
END.
For the screen that lists employees, you could write the following DDL definition:
DEF employee-list-screen.
02 emp-list TYPE employee
OCCURS 15 TIMES.
END.
You should add EMPLOYEE-LIST-SCREEN to the list of objects that belong to the
requester and set the screen format to tabular. The data fields on the application
screen will look like this:
EMP-LAST-NAME EMP-FIRST-NAME EMP-NUM DEPT-NUM
____________________ ____________________ ____ ____
____________________ ____________________ ____ ____
____________________ ____________________ ____ ____
____________________ ____________________ ____ ____
. . . .
. . . .
. . . .