The following table shows how the characteristics of the TPs and selection of the LUs for a conversation are controlled.
| Characteristic | How controlled |
|---|---|
| Type of conversation: basic or mapped |
Written into the code. For two TPs to communicate successfully, both must use the same type of conversation, basic or mapped. The default for conversation type is mapped; the type can be changed with the Set_Conversation_Type call. See Basic and Mapped Conversations Compared.
|
| Type of TP: invoking or invokable |
Written into the code. Invoking TPs start with Initialize_Conversation and Allocate. Invokable TPs start with Accept_Conversation. See Invoking TPs and Invokable TPs.
|
| The local LU alias to be used by an invoking TP | Three options:
See Invoking TPs and the SNA Server Configuration.
|
| The symbolic destination name used by an invoking TP
|
Written into the code, in Initialize_Conversation. |
| The invokable (partner) TP requested by an invoking TP
|
Specified within the symbolic destination name, which can be configured through SNA Server Manager. |
| The LU alias to be used by an invokable TP (the partner LU alias from the point of view of the invoking TP)
|
Specified within the symbolic destination name, which can be configured through SNA Server Manager. See Invoking TPs and the SNA Server Configuration and Matching Invoking and Invokable TPs. |
| Type of autostarted invokable TP: queued or nonqueued
|
Configured with registry or environment variables. See Configuring Invokable TPs. |
| Local LU and remote LU aliases | Configured in SNA Server Manager. For information, see the Microsoft SNA Server Administration Guide.
|
| The pairing of local and remote LUs, and the mode used for each LU-LU pair | Configured in SNA Server Manager. For information, see the Microsoft SNA Server Administration Guide. |