Pathmaker Programming Guide

Registering Servers Not Created With Pathmaker
Creating Services and Servers
4–74 067868 Tandem Computers Incorporated
Registering Servers
Not Created With
Pathmaker
By allowing you to create registered services and servers, the Pathmaker product
provides a way to enter information about Pathway servers that were not created
using the Pathmaker product, and the files or tables that they access, into a Pathmaker
catalog.
Registered Pathmaker services and servers are just entries in a Pathmaker catalog.
Code is not generated or compiled by the Pathmaker product for registered services
and servers.
Although registering a Pathway server is not necessary to access it from a Pathmaker
application, doing so is beneficial in several ways:
Because the Pathmaker catalog contains information about registered servers and
the physical files that they access, the Pathmaker product can generate the
statements necessary for running the registered servers in the Pathway command
files such as PATHCNFG and PATHSVRS.
Because the Pathmaker catalog contains the location of the object code of the
registered servers, the Pathmaker product is able to move these files whenever the
other components of the associated Pathmaker application are moved.
Defining Registered
Services
A Pathway server that has not been created with the Pathmaker product does not have
services, so you have to assign services to that server by labelling the tasks (or task)
that the server performs as services.
The number of registered services you create for a server not created with the
Pathmaker product is determined by the needs of the clients or requesters that will use
the server. You must create at least one registered service in order to register a server
not created with the Pathmaker product. This requirement exists because some of the
information needed by the Pathmaker product can only be specified on screens used
for service definition.
A useful guideline is to create one registered service for each unique IPC request
message that the server receives. For a client/transaction server application, creating
one registered service for each unique IPC request message makes it easy for you to
use components of the Pathway Open Environment Toolkit product to generate C
language type definitions and conversion code for each set of distinct IPCs for
inclusion in client code. Although not required for a Pathway requester/server
application, creating one registered service for each unique IPC request message
provides valuable documentation about the components of the messages between a
requester and a registered server.
Prior to creating a registered service, you must register the NonStop SQL tables and
views used by the server using the SQL Table Registration screen. You also must
define, using DDL, all IPCs used by the server if you will be using the IPC Definition
screen. (See Step 2 following.)