Additional Options for Setting Local_LU

CPI-C applications rely on the DEFAULT_LOCAL_LU for use with TP_STARTED. Unless set otherwise, this is always the LOCAL_LU which matches the LOCAL_CP CP_NAME. This is not always what is desired. For Personal Communications, the system environment APPCLLU may be used to refer to any defined LOCAL_LU. The value for APPCLLU must match the LOCAL_LU_ALIAS exactly. It is case and length sensitive. (Blanks are also counted in the length.) CPI-C functions use this value for any Operator_Started TP.

CPI-C applications rely on the DEFAULT_LOCAL_LU for use with TP_STARTED. Unless set otherwise, this is always the LOCAL_LU which matches the LOCAL_CP CP_NAME. This is not always what is desired.

Any defined LOCAL_LU can be used in place of the DEFAULT_LOCAL_LU by specifying the LOCAL_LU_ALIAS name of a defined LOCAL_LU in the CPI-C Side Information definition. The LOCAL_LU and CPI-C Side Information configuration's LOCAL_LU_ALIAS names must match exactly. They are case-sensitive and length-sensitive.

Personal Communications also supports the use of the system environment APPCLLU which may be used to refer to any defined LOCAL_LU. The value for APPCLLU must match the LOCAL_LU_ALIAS exactly. It is case-sensitive and length-sensitive (blanks are also counted in the length). CPI-C functions use this value for any Operator_Started TP.