Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting C Applications
096047 Tandem Computers Incorporated 5–17
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
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 pragma or after compilation using the Binder program.
To set the attribute when you compile your program, specify the RUNNAMED
pragma in your source code or as a compiler option in the TACL RUN command for
the C compiler. The BINSERV program then sets the RUNNAMED attribute in the
object file. An example of this pragma (with the HIGHPIN pragma) in a source file is:
#pragma HIGHPIN, RUNNAMED
An example of this pragma as a compiler option is:
10> C /IN csrc, OUT $s.#clst, NOWAIT/ cobj; HIGHPIN, RUNNAMED
You need to specify the RUNNAMED pragma only once during a compilation.
However, you can specify it any number of times and the compiler will not generate
an error.
If you do not set the RUNNAMED attribute when you compile your program, you can
set it after compilation using Binder. For a single object file, use the Binder CHANGE
command:
@CHANGE RUNNAMED ON IN cobj
If you are binding more than one object file into a single target object file, use the
Binder SET command to set the RUNNAMED object-file attribute. If any of the
constituent object files used to build the target file has the RUNNAMED object-file
attribute set, Binder sets this attribute in the target object file.