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 verb: synchronous or asynchronous | Written into the code. Synchronous verbs use blocking calls; asynchronous verbs avoid blocking calls. See Receiving Data Asynchronously and WinAsyncAPPC.
|
Type of conversation: basic or mapped |
Written into the code. The MC_ prefix is used on verbs in mapped conversations and omitted on verbs in basic conversations. For two TPs to communicate successfully, both must use the same type of conversation, basic or mapped. See Basic and Mapped Conversations Compared.
|
Type of TP: invoking or invokable |
Written into the code. Invoking TPs start with TP_STARTED, which identifies the invoking TP, and ALLOCATE or MC_ALLOCATE, which identifies the requested invokable TP. Invokable TPs start with RECEIVE_ALLOCATE, which identifies the invokable TP. 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 invokable TP requested by an invoking TP
|
Written into the ALLOCATE or MC_ALLOCATE request in the invoking TP. |
The LU alias to be used by an invokable TP | Two options:
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. |