HP-UX SNAplus2 R7 Administration Guide

Configuring APPC Communication
Defining TPs
For information about using the snaptpinstall or tpinst32 command, see Appendix C, Configuring an
Invokable TP from the Command Line.
7.4.1 TP Invocation Parameters on a Server
This section describes the parameters required by the Motif administration program or the command-line
administration program when configuring an invokable TP on a server. For information about configuring an
invokable TP on a client, see Appendix C, Configuring an Invokable TP from the Command Line.
The following parameters are required for a TP that can be invoked on the local node:
TP name
A TP name in one of the following forms:
Application TP
If the TP is a user application, supply the name as normal characters (up to 64 characters in length).
Service TP
If the TP is an SNA service transaction program, enter the name in hexadecimal (up to eight hexadecimal
digits, representing 4 bytes).
You can define multiple APPC invokable TPs that have the same TP name, provided each TP definition
specifies a different LU alias. You cannot do this for CPI-C invokable TPs, because you cannot specify a
particular LU alias to use; each CPI-C invokable TP must have a different name.
Parameters are for invocation on any LU/on specificLU
If the TP is an APPC TP, this parameter specifies whether to make the TP invokable on any LU or only on
a specific LU. By default, the TP can be invoked on any LU.
Note
If the TP is a CPI-C application, this field must be set to make the TP invokable
on any LU. CPI-C does not support accepting incoming Attaches from a particular
local LU; attempting to specify this option for a CPI-C application will cause errors
in routing the incoming Attach to the TP.
LU alias
This field must not be used if the TP is a CPI-C application. If the TP is an APPC application, it applies
only if you specify that the parameters for this TP definition are for invocation on any LU.
The local LU alias from which the TP is to accept incoming Attaches. This name must match the name of a
local APPC LU on the SNAplus2 node. If you do not specify an LU alias, the TP accepts incoming Attaches
from any local LU.
If a non-blank LU alias is specified, the TP must use the extended form of the RECEIVE_ALLOCATE verb
and specify this LU alias as a parameter to the verb. This enables SNAplus2 to route the incoming Attach to
the correct TP. For more information about the different forms of RECEIVE_ALLOCATE, refer to HP-UX
SNAplus2 APPC Programmer’s Guide. If you need to permit the TP to determine the correct LU alias at
run-time rather than building it into the application, you can do this by setting an environment variable to
contain the appropriate LU alias (using the Environment parameter), and designing the application to read
this environment variable in order to determine how to issue RECEIVE_ALLOCATE.
You can define multiple TPs that have the same TP name, provided each TP definition specifies a different
LU alias.
112