Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting TAL Applications
096047 Tandem Computers Incorporated 3–31
An example of this directive as a compiler option is:
10> TAL /IN talsrc, ... / talobj; HIGHPIN, RUNNAMED
You need to specify the RUNNAMED directive only once during a compilation. The
TAL compiler ignores redundant RUNNAMED directives.
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 talobj
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.
Communicating With a
High-PIN Server
A requester can open and communicate with a high-PIN named server by opening the
server using the OPEN procedure. However, you must convert your requester to open
the server using the FILE_OPEN_ procedure if the server:
Is unnamed
Is on a remote D-series system and has a six-character name (a dollar sign and five
alphanumeric characters)
Figure 3-4 shows the processes involved in converting this part of a typical
application. The steps in this subsection apply to the requester process $REQ.
Figure 3-4. Converting a TAL Requester to Communicate With a High-PIN Server
$SRV
$REQ
TAL Requester
Process
Server
Process
TACL
This subsection discusses converting the following operations:
Opening and closing the high-PIN server
Opening and closing the high-PIN server for a backup process
Sending requests to the high-PIN server