Invoking TPs and the SNA Server Configuration

For an SNA server to support the beginning of the invoking process, the following parameters must be configured correctly:

• If the invoking TP specifies the LU alias that it uses (in a registry or environment variable), that LU alias must match a local APPC LU alias on the supporting SNA server. If the invoking TP does not specify a local LU alias, one of two methods for designating a default LU must be carried out on the supporting SNA server:
  1. Assign a default local APPC LU to the user or group that starts the invoking TP (that is, the user or group logged on at the system from which Initialize_Conversation is issued).

     —or—

  2. Designate one or more LUs as members of the default outgoing local APPC LU pool. SNA Server first attempts to determine the default local APPC LU of the user who started the TP, then attempts to assign an available LU from the default outgoing local APPC LU pool; if these attempts fail, SNA Server rejects the request.
• In most situations, the supporting SNA server must contain an appropriate connection to another system (host or peer). Sometimes, for testing purposes, the SNA server contains two local LUs paired together (for invoking and invokable TPs that are in the same domain); in this situation, a connection to a host or peer is not necessary.
• The partner LU alias specified in the symbolic destination name must match an LU alias that is paired with the local LU alias used by the invoking TP.

The preceding parameters support the beginning of the invoking process. For the invoking process to successfully complete, additional parameters must be configured as described in Invokable TPs and the SNA Server Configuration.