|
|
|
|
The local LU that an invoking CPI-C TP uses can be specified in a number of ways which are described below.
The local LU for an invoked TP is not specified like this, but is defined by the partner LU value specified in the allocate request.
If the LU specified is a dependent LU, multiple concurrent conversations are not supported (because dependent LUs cannot support multiple sessions).
The different ways that you can set the local LU alias are described in the following sections. The methods are listed in order of precedence. This means that, if you specify a local LU alias using the first method, the CPI-C library uses this name and ignores any alias that you specify using the second or later methods. If you do not use the first method but specify a local LU alias using the second method, the CPI-C library uses this alias and ignores any alias that you specify using the third or later methods, and so on.
The program can issue this call to specify the local LU alias after the Initialize_Conversation call has completed. This call only affects the TP from which it is issued. It does not modify the side information stored in the configuration file.
This call is not part of the standard CPI-C specification, and may not be available in other implementations. You may want to avoid using this function, or to restrict it to a few specific routines which can be modified easily, if you need to ensure that your application can be used with other CPI-C implementations.
If there is another TP from which the context is copied, the local LU name is taken from that other TP. For more information about context, see Multiple Conversations.
The local LU alias can be specified using the
On Solaris systems this environment variable can be set in the following ways:
The program can issue a putenv call
You can set it in the Solaris shell. For example, in the Korn shell you would issue the following command:
export APPCLLU=MYLU
On Windows systems the local LU alias is specified in the registry. The registry
key is
The
The local LU alias is part of the side information configured for each symbolic destination name. TPs select which of these to use in the Initialize_Conversation call.
Programs can modify the side information. For more information, see Administering Side Information.
Local LUs can be configured to be a part of the default pool of APPC LUs. If no other local LU alias is specified, any suitable LU from this pool is used.
SNAP-IX normally has one control point (CP) LU defined on each node. If no other local LU alias is defined then the CP LU is used.
|
|
|
 |
|