Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting COBOL85 Applications
096047 Tandem Computers Incorporated 4–15
Opening and
Communicating With a
High-PIN Server
This subsection describes how to convert a COBOL85 requester to communicate with
and monitor a high-PIN server. For the requester, you have the following options:
The requester remains unconverted, but the server has the RUNNAMED object-
file attribute set.
The requester is converted to run at a high PIN and its interface with the server
process is also converted for communication with a high-PIN process.
If your requester does not need converting, then you can let it continue to run at a low
PIN by setting the RUNNAMED object-file attribute in the server. This attribute
makes sure that the server is named and therefore allows the requester to open it even
though the requester runs at a low PIN and the server at a high PIN. “Setting the
RUNNAMED Object-File Attribute” later in this subsection explains how to do this.
If your requester does need to be converted, you must first make it run at a high PIN
as described in “Converting a COBOL85 Program to Run at a High PIN” earlier in this
section. Then, if necessary, convert the following parts of the program:
Communication with the server
Server monitoring functions
System message reception
See “Converting a Requester,” later in this section, for details on how to convert these
parts of your program.
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.
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. Because you can then open the process by name,
you can run the process at a high PIN under the D-series operating system and have
that process opened by an unconverted process using the Guardian OPEN procedure.
For more information about how an unconverted process running on a D-series system
can communicate with a named high-PIN process, refer to Appendix C, “System
Compatibility.”
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
compiler directive in your source code or as a compiler option in the TACL RUN
command for the COBOL85 compiler. The BINSERV program then sets the
RUNNAMED attribute in the object file. An example of this directive (with the ENV
and HIGHPIN directives) in a source file is:
?ENV COMMON; HIGHPIN; RUNNAMED