HP-UX SNAplus2 R7 Administration Guide

Configuring APPC Communication
Defining TPs
• The first string can be a complete SNA network name that matches the first part of the fully qualified
partner LU names exactly, or a wildcard prefix that matches the beginning of the network name for
the partner LUs. If you supply a wildcard prefix as the value for the first string, leave the second
string blank. For example, a wildcard entry of
A would match all LUs in the SNA networks named
A, ANT, or APPN (but not BUFFALO or ZEBRA).
• If you supply a complete SNA network name for the first string, you can also enter a value for the
second string. (You cannot specify the second string without supplying a valid SNA network name
for the first string.) The second string is treated as a wildcard prefix, which must match the start of
the second part of the fully qualified partner LU names. For example, a wildcard entry of A.F would
match partner LUs names A.FRED or A.FREDDY (but not APPN.FRED or A.B).
If you leave both strings blank, the wildcard partner LU definition matches any partner LU name.
Use partner LU name as a wildcard
Whether to use the partner LU name as a wildcard, rather than as a literal fully qualified LU name.
7.3.3 Additional Configuration
After performing the partner LU configuration, continue with the following configuration tasks:
• To define an invokable TP, see Section 7.4, Defining TPs.
• To define a mode, see Section 7.5, Defining Modes and Classes of Service.
• To define CPI-C side information, see Section 7.6, Defining CPI-C Side Information.
• To define APPC security, see Section 7.7, Configuring APPC Security.
• To configure 5250 communication, see Chapter 8, Configuring User Applications.
7.4 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 Section 7.4.2, 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 Section 7.4.1, TP Invocation Parameters on a Server.
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.
110