Default Local LU
Personal Communications and Communications Server support default local LUs for both dependent and independent
LU 6.2. The default LU is used when the TP_STARTED verb
(see TP_STARTED) is issued with a blank lu_alias field.
For independent LU 6.2, the default LU is the control point LU. Personal Communications also
allows the specification of a default local LU to be used instead
of the control point LU. For dependent LU 6.2, a local LU pool is
used. Refer to System Management Programming for details on the DEFINE_LOCAL_LU verb. Personal Communications choose an LU from the
default pool, or use the control point LU, as follows:
- If LUs have been configured as members of the default local LU pool, Personal Communications choose an LU from the pool that is not in use. If all the LUs in the pool are in use, the TP_STARTED verb fails.
- If no LUs have been configured as members of the default local LU pool, Personal Communications use the control point LU.
- For Personal Communications, a default Local LU can be specified. Refer to Configuration File Reference for details.
- The following information only applies to Communications Server Windows SNA
API clients.
The default local LU alias for each user can be assigned using the appropriate configuration utility, either INI configuration or LDAP.
APPC programs can choose to use a default local LU alias rather than specify one directly. When an APPC program issues a TP_START verb with the local LU alias field set to binary zeroes, the APPC API uses the configured default local LU alias.