Guardian Application Conversion Guide

Allowing a High-PIN Creator
Converting TAL Applications
096047 Tandem Computers Incorporated 3–39
If You Do a Full Conversion
To use the D-series enhanced interface to allow your program to enable a high-PIN
creator, you need to convert your program to run at a high PIN as described in
“Converting a TAL Program to Run at a High PIN,” earlier in this section. In addition,
you might choose to make changes if your program obtains the identity of its creator
or if your program does not use the INITIALIZER procedure to process the startup
sequence of messages.
If your program directly obtains the identity of its creator, you should:
Convert all calls to the MOM procedure into calls to the PROCESS_GETINFO_
procedure.
Convert all calls to the LOOKUPPROCESSNAME procedure that return the
identity of the creator into calls to the PROCESS_GETPAIRINFO_ procedure.
PROCESS_GETINFO_ and PROCESS_GETPAIRINFO_ return process handles instead
of the process IDs that the MOM and LOOKUPPROCESSNAME procedures return.
Process IDs are unsuitable because the PIN field is too short to return a high PIN; you
get a synthetic process ID instead, which always has a PIN of 255. “Getting Your
Creator’s Process Identifier,” later in this section, provides details.
If your program does not use the INITALIZER procedure, you must:
Open $RECEIVE using the FILE_OPEN_ procedure instead of the OPEN
procedure and then read and process the D-series messages.
Convert calls to the RECEIVEINFO procedure and the LASTRECEIVE procedure
into calls to the FILE_GETRECEIVEINFO_ procedure.
“Converting a Startup Sequence That Does Not Use INITIALIZER,” later in this
section, provides details.
If You Use the HIGHREQUESTERS Attribute
If you choose to set the HIGHREQUESTERS object-file attribute, then the high-PIN
creator of your process is allowed to open your process. “Setting the
HIGHREQUESTERS Attribute to Allow a High-PIN Creator,” later in this section,
provides details on how to do this.
Further conversion is unnecessary if synthetic process IDs returned by the MOM,
LOOKUPPROCESSNAME, RECEIVEINFO, and LASTRECEIVE procedures are
enough to distinguish the creator process for the needs of your application.