Introduction to SNAplus2
SNAplus2 Components
APPC APIAn APPC application uses the node's LU type 6.2 resources to communicate with another APPC or
If the TP on the SNAplus2 computer is the invoking TP (the TP that starts the APPC conversation), the additional node resources required depend on the APPC features used by the TP, and on the type of remote system it is communicating with:
•If the local node or the remote system with which the TP communicates is a LEN node, you need to define directory entries for the remote node and its LUs.
•If the TP specifies its local APPC LU using an LU alias, you need to define the partner LU in order to associate this alias with a fully qualified LU name.
•If the TP uses a dependent local LU to communicate with a host, you need a partner LU definition on the local node that specifies the uninterpreted name for the LU on the host. When the TP requests a conversation from the local LU, the local LU sends the host a session initialization request that contains the uninterpreted name for the host LU.
In the Motif administration program, directory entries and partner LUs are not shown explicitly, but are included under the “Remote Systems” heading in the Node window for the local node.
If the TP on the SNAplus2 computer is the invoked TP (the TP that accepts a conversation started by the invoking TP), the additional resources required depend on the APPC features used by the TP, and on how it is to be started:
•To restrict the TP to using particular options for conversation security, confirm synchronization, or conversation type (mapped or basic), or to restrict the number of instances of the TP that can be running at any time, you must define the TP as a node resource.
•To start the TP automatically when another TP requests a conversation with it, you must provide the information that SNAplus2 needs to start the TP. For more information, see Chapter 7, “Configuring APPC Communication.”
82 | Chapter 2 |