Pathmaker Programming Guide

Defining a Custom Server
Creating Services and Servers
4–68 067868 Tandem Computers Incorporated
Defining a Custom
Server
The Pathmaker product has three types of servers:
Standard servers Servers provided to process requests by DB requesters
Custom servers Servers that contain custom services
Registered servers Servers created outside the Pathmaker environment but
known to a Pathmaker project
The only types of servers that you can define using the Pathmaker product are custom
servers (servers made up of custom services) and registered servers. If you are using a
DB requester, you do not need to define either services or servers.
Refer to “Registering Servers Not Created With Pathmaker” later in this section for
information about registered servers. The remainder of this subsection explains the
procedures for defining custom servers. Although custom Pathmaker servers can be
created using either the Pathmaker full screen interface or PMADL, this subsection
only discusses using the full screen interface for these tasks.
Before defining a server, you should define the services that will be included in the
server. To define and generate a server, follow these steps:
1. Name and describe the server and specify the programming language (COBOL or
C), server type (custom or registered), and destination files for the server source
code, for the server object code, and for the server compilation listing (optional)
using the Server Definition screen. Specify any necessary compiler directives.
Then add the server by pressing F1.
2. Designate which custom services are to be packaged into this server using the
Service Assignment screen.
3. Direct the Pathmaker product to generate and, optionally, compile the server by
pressing shifted F6 on the Server Definition screen.
4. Verify that the generation and compilation were successful by viewing the
compilation listings.
Note You can generate any server with services that have been entered into the Pathmaker project catalog.
You do not need to write the Custom Source File code before you generate the server source code.
The code that you produce at this stage could be installed in a test application, but it cannot access the
database. If you try to invoke the service from the application, the server returns an advisory reply
because the Custom Source File that you specified is incomplete.