C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

HIGHPIN
The HIGHPIN pragma specifies that the object file should be run at a high PIN (256 or greater)
or at a low PIN (0 through 254)..
[NO]HIGHPIN
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
Not setNot setTNS C compiler
HIGHPINHIGHPING-series TNS c89 utility
HIGHPINHIGHPINTNS/R native C and C++ compilers
HIGHPINHIGHPINNative c89 and c99 utilities
HIGHPINHIGHPINTNS/E native C and C++ compilers
Usage Guidelines
For the TNS C compiler, Cfront, and the TNS c89 utility, the HIGHPIN pragma can be placed
in the source text or in the RUN command that executes the compiler.
When you bind several object files together, Binder sets the HIGHPIN attribute in the target
object file if, and only if, all the object files being bound together have the HIGHPIN pragma
specified.
For the native C and C++ compilers, the HIGHPIN pragma can be entered on the compiler
RUN command line (not in the source file) or be specified with the -Whighpin flag of the
c89 or the c99 utility.
The HIGHPIN attribute is set for native C and C++ programs only if an executable object file
is the output of the compilation. (Process attributes cannot be set for native relinkable object
files.)
When the operating system creates a process, it assigns a process identification number (PIN)
to the process. Systems running D-series RVUs or later support these ranges of PINs:
0 through 254Low-PIN range
256 through the maximum number supported for the
processor
High-PIN range
To run an object file at high PIN from the TACL prompt, these conditions must be met:
Your processor is configured for more than 256 process control blocks (PCBs).
High PINs are available in your processor.
Your object file has the HIGHPIN attribute set.
The TACL HIGHPIN built-in variable or the HIGHPIN run-time parameter is set.
If these four conditions are met, the operating system assigns a high PIN, if available. If no
high PINs are available, the operating system assigns a low PIN.
You can set the HIGHPIN flag of TNS and accelerated object files either:
During compilation by using the HIGHPIN pragma
After compilation using a Binder command
HIGHPIN 201