TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

The Pathmaker Application Generator
The Pathmaker product helps you create Pathway applications consisting of requester programs
written in SCREEN COBOL and server programs written in C or COBOL85. To create applications
with the Pathmaker product, you:
• Enter information about your application into a series of screen-based entry forms, which the
Pathmaker product then stores in a catalog
• Use the HP text editor, TEDIT, to create source files containing C or COBOL85 service code
At your command, the Pathmaker product uses the information from the catalog and the TEDIT file
to generate SCREEN COBOL requester code, C or COBOL85 server code, and command files to
configure and start the finished Pathway environment for testing.
The Pathmaker product simplifies the creation of Pathway applications by:
• Generating application code in a uniform structure for all requesters and servers, to help
simplify maintenance and modification
• Producing program statements for tasks that are specific to the Pathway environment
• Automatically generating TMF statements in your requester programs when you indicate that
you want your programs to have TMF protection
• Providing a central location for most application information
• Creating error-handling code for the most commonly encountered errors
• Letting you simulate application screens and navigate from one application screen to another
before you write a single line of code
Applications developed with the Pathmaker product can access data from databases managed
by either the NonStop SQL/MP relational database management system or the Enscribe database
record manager. If you are using Pathsend requesters, or clients that use RSC/MP or POET, you
can use the Pathmaker tool to create prototype servers.
Client/Server Development Tools
As mentioned earlier, the RSC/MP product facilitates client/server computing, allowing workstation
applications to access Pathway servers. A large number of packaged tools and utilities are
commercially available for use with RSC/MP, including POET.
Transaction Processing Scenario
Figure 3 (page 27) and the description that follows it provide an example of how transactions
from Pathsend requesters are processed. The figure shows the path of transactions from an IBM
system to a server class on a NonStop system.
NOTE: The figure does not reflect the actual flow of data from the Pathsend requester to the
Pathway server class. Only server-class control information is passed to the LINKMON process or
the ACS subsystem processes; the application data moves directly from the Pathsend process to
the server class.
26 Introduction to Pathway Application Programming