HP HP-UX SNAplus2, Administration Manual, Page: 187 / 398

Chapter 7 187
Configuring APPC Communication
Defining TPs
Defining TPs
This section explains how to define an APPC TP.
In most cases, you do not need to define TPs that run on the SNAplus2
system; but you do need to configure a TP definition in the following
cases:
APPC Characteristics
If the TP on the SNAplus2 computer is the invoking TP
(or source TP—the TP that starts the APPC
conversation) and you do not need to restrict access to
the TP, you do not need to define the TP. You can,
however, define an APPC TP, as described in “TP
Definition Parameters”, to specify the following
characteristics:
• To define conversation security for the TP.
• To indicate whether the TP uses basic or mapped
conversations.
• To specify sync point processing.
• To specify handling of PIP data.
Invokable TPs
To enable a TP to be started automatically in response
to an incoming allocation request, define it as an
invokable TP as described in “TP Invocation
Parameters”.
An invokable TP (or target TP) is one that is started in
response to an incoming allocation request. You must
create a TP definition for an invokable TP. An
invokable TP can be an APPC TP that issues
RECEIVE_ALLOCATE, or a CPI-C application that
issues Accept_Conversation or Accept_Incoming.
NOTE In this section, the phrase “Receive_Allocate” is used to indicate any of
these three API calls.
You can also define an invokable TP to route incoming
allocation requests to a running TP.