Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting C Applications
5–16 096047 Tandem Computers Incorporated
Opening and
Communicating With a
High-PIN Server
Your existing program might be a requester that communicates with a server. For
example, you might open a server, send it a request, and then process its reply. You
might also open a server for a backup requester if your program is running as a
process pair.
The degree of conversion you need to perform depends on whether your server is
named or unnamed, and, if the server is named, on how long the name is. Your
options are as follows:
If the server is local and named or if the server is remote with a name of five
characters or less (including the dollar sign), then no conversion is necessary. You
can still open the high-PIN server using the Guardian C-series-compatible OPEN
procedure. See Appendix C, “System Compatibility,” for further information on
communicating with a named high-PIN process.
If the server is remote and has a six-character name, then you need to first convert
your requester to run at a high PIN as described under “Converting a C Program
to Run at a High PIN” earlier in this section, and then complete the conversion as
described under “Communicating With a High-PIN Server” and “Monitoring a
High-PIN Server,” later in this section. See Appendix C, “System Compatibility,”
for further information on communicating with a named high-PIN process.
If the server is unnamed, then you have the following options:
Set the RUNNAMED object-file attribute in the server so that the system
provides a name for the server, and pass the system-assigned name to the
requester; for example, in a DEFINE or an ASSIGN. See “Setting the
RUNNAMED Object-File Attribute” later in this section for details.
Convert the requester to run at a high PIN as described under “Converting a C
Program to Run at a High PIN” earlier in this section, and then complete the
conversion as described under “Communicating With a High-PIN Server” and
“Monitoring a High-PIN Server,” later in this section.
For information about converting a server to monitor a high-PIN requester process,
including maintaining an opener table, refer to “Being Opened by and Communicating
With a High-PIN Requester,” later in this section.