Guardian Application Conversion Guide

Creating and Managing a High-PIN Process
Converting COBOL85 Applications
4–14 096047 Tandem Computers Incorporated
Creating a High-PIN
Process
If you have already converted your program to run at a high PIN as described earlier
in this section under “Converting a COBOL85 Program to Run at a High PIN,” then
your program will automatically create any new processes at a high PIN, assuming:
The process you are creating is designed to run at a high PIN (that is, it has its
HIGHPIN object-file attribute set). See “Setting the HIGHPIN Object-File
Attribute” earlier in this section.
The program you are converting is not started by another low-PIN process that
has its inherited force-low characteristic set. See Appendix C, “System
Compatibility,” for a discussion of the inherited force-low characteristic.
Starting a new process at a high PIN is automatic because compiling with the CRE
forces the object file to make Guardian procedure calls through the D-series enhanced
interface rather than the C-series-compatible interface.
See “Selecting the Common Run-Time Environment (CRE)” earlier in this section for
details on how to compile with the CRE.
Managing a High-PIN
Process
Managing a process can involve suspending and activating the process, and stopping
or abending the process. To perform these operations on a high-PIN process, you
simply need to recompile your COBOL85 program to select the CRE. Doing so causes
the object code to use the D-series interface to the operating system, which is necessary
to manage a process at a high PIN.
See “Selecting the Common Run-Time Environment (CRE)” earlier in this section for
details on how to compile with the CRE.