Pathmaker Programming Guide

Modifying Requesters
Advanced Pathmaker Programming Topics
9–14 067868 Tandem Computers Incorporated
Files Used to Create a SEND to a Remote Node
As mentioned in the previous paragraphs, you must create a requester copy library file
on the home system and create or modify Pathway configuration files on the remote
system if you want to send a request to a server on a remote node.
These tasks must be done to invoke a server on a remote node correctly. The
Pathmaker product produces several other files that you might want to alter,
depending on how you plan to maintain the application.
The PMPROJECT INSTALL command produces several files that contain commands
that refer to the server and database files that you moved. The files are:
GENDATA
DUPCODE
SQLCODE
You can remove the commands that refer to the server and the database file (or files)
that it accesses from GENDATA, DUPCODE, and SQLCODE and place the commands
in corresponding files on the remote node. Consider, however, how you want to
handle revisions to the application before you remove these commands—you might
want to duplicate the server object code on the remote node and leave the original
object code file and its associated files on the home node for easier maintenance.
The following files contain references to the server or database file that you moved to
the remote system. Depending on how you plan to maintain the application, you
might want to edit:
DUPCODE To remove FUP DUP commands for the server object
code that is to reside on the remote node.
GENDATA For Enscribe users, to remove FUP file creation
commands for the database file that is to reside on the
remote node.
SQLCODE For SQL users, to remove ADD DEFINE and SQLCOMP
commands for the database table and server that are to
reside on the remote node.