Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting COBOL85 Applications
4–16 096047 Tandem Computers Incorporated
An example of this directive as a compiler option is:
10> COBOL85 / ... / cobobj; ENV COMMON; HIGHPIN; RUNNAMED
You need only specify the RUNNAMED directive 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 cobobj
If you are binding more than one object file into a single target object file, use the
Binder SET command to set the 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 the attribute in the target object file.
Converting a Requester This subsection describes how to convert your COBOL85 requester program.
Figure 4-4 shows the processes involved in converting a typical application. The steps
in this subsection apply to the requester process $REQ.
Figure 4-4. Converting a COBOL85 Requester to Communicate With a High-PIN Server
$SRV
$REQ
COBOL85 Requester
Process
Server
Process
TACL
This subsection describes the following topics:
Opening and communicating with a high-PIN server
Monitoring a High-PIN server
Opening and reading $RECEIVE
Converting the RECEIVE-CONTROL Paragraph