TS/MP 2.5 Pathsend and Server Programming Manual
At your command, the Pathmaker product uses the information from the catalog and the TEDIT file
to generate SCREEN COBOL requestor 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 an uniform structure for all requestors 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 requestor programs when you indicate that
the programs need to have TMF protection.
• Providing a central location for most application information.
• Creating error-handling codes for most commonly encountered errors.
• Allowing to 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 requestors, 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. Including POET, a large number of packaged tools and
utilities are commercially available for use with RSC/MP.
Transaction Processing Scenario
Figure 3 (page 26) and the description that follows it provide an example of how transactions
from Pathsend requestors 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 requestor to the
Pathway server-class. Only server-class control information is passed to the ACS subsystem ROUT
process; the application data moves directly from the Pathsend process to the server-class.
Transaction Processing Scenario 25










