Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting TAL Applications
3–30 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.
How much 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:
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 TAL
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
TAL 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.
Setting the RUNNAMED
Object-File Attribute
The RUNNAMED object-file attribute causes a process to run as a named process even
if you do not provide a name for it. Thus, a process can run at a high PIN under the
D-series operating system and be opened by an unconverted process using the OPEN
procedure.
You set the RUNNAMED object-file attribute either during compilation using a
compiler directive or after compilation using the Binder program.
To set the attribute when you compile your program, specify the RUNNAMED
directive in your source code or as a compiler option in the TACL RUN command for
the TAL compiler. The BINSERV program then sets the RUNNAMED attribute in the
object file. An example of this directive (with the HIGHPIN directive) in a source file
is:
?HIGHPIN, RUNNAMED