An invoking TP can be located on any system on the SNA network. An invoking TP identifies itself by issuing TP_STARTED, which specifies the name of the invoking TP and can specify the LU alias that the TP uses. If the LU alias is not specified in TP_STARTED, SNA Server must be configured to supply it through one of two types of default local LU; otherwise, TP_STARTED will fail. For more information, see Invoking TPs and the SNA Server Configuration.
Next, the invoking TP initiates the invoking process by issuing ALLOCATE or MC_ALLOCATE, in which it specifies the name of the invokable TP, and can also specify the partner LU alias (the LU alias to be used by the invokable TP). If the partner LU is not specified in ALLOCATE or MC_ALLOCATE, SNA Server must be configured to supply one through the default remote APPC LU assigned to the user who started the invoking TP; otherwise, ALLOCATE or MC_ALLOCATE will fail. For more information, see Invoking TPs and the SNA Server Configuration.
After a TP successfully issues an ALLOCATE or MC_ALLOCATE verb, an allocation request flows. For more information about what happens after an invoking TP requests an invokable TP, see Matching Invoking and Invokable TPs.