Pathmaker Programming Guide

New and Changed Information
iv 067868 Tandem Computers Incorporated
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.