Guardian Application Conversion Guide

Being Opened by and Communicating With a High-PIN Requester
Converting COBOL85 Applications
4–22 096047 Tandem Computers Incorporated
Being Opened by and
Communicating With a
High-PIN Requester
This subsection describes how to convert a COBOL85 server to communicate with a
high-PIN requester. Whether you need to convert the server process depends in part
on whether the server tracks its openers. If the server does keep track of its openers,
you should enable the server to run at a high PIN as described in “Converting a
COBOL85 Program to Run at a High PIN,” earlier in this section, and then convert the
server as described under “Converting a Server,” later in this subsection.
If the server does not track its openers, or if you choose not to perform the conversion,
then you can keep the server process at a low PIN and not convert it, except for setting
the HIGHREQUESTERS object-file attribute as described under “Setting the
HIGHREQUESTERS Attribute to Allow High-PIN Openers,” later in this subsection.
Setting this attribute enables a high-PIN requester to open a low-PIN server.
Converting a Server If your server program tracks its openers and uses the PIN to identify each opener,
then you must convert the server. Figure 4-5 shows the processes involved in
converting a typical application. The steps described in this subsection apply to the
server process $SRV.
Figure 4-5. Converting a COBOL85 Server to Communicate With a High-PIN Requester
$SRV
$REQ
Requester
Process
COBOL85
Server
Process
TACL
You must convert the following parts of your program:
The RECEIVE-CONTROL paragraph, so that
Your program accepts D-series enhanced interface messages instead of
C-series-compatible messages
The MESSAGE SOURCE clause identifies processes by process handle rather
than by process ID
The opener table, so that it identifies openers by process handle instead of process
ID
$RECEIVE handling, to have a read buffer large enough for D-series enhanced
interface system messages