Managing multiple LUs for a single IMS system
An IMS system can be represented on a network by more than one LU name. If more than one LU name exists for a single IMS system, you might need to specify which LU should process asynchronous outbound messages.
When more than one LU is defined for an IMS system, one of the LUs serves as the default, or base, LU. Normally, the base LU handles all allocation requests for outbound conversations. However, in some cases the remote partner LU might expect the outbound conversation to come from an LU other than the base LU, you can control which LU handles outbound conversation allocation requests. There are three methods for controlling which LU handles outbound conversation allocation requests:
- By specifying an LU name in the OUTBND parameter of the LU 6.2
descriptor in the DFS62DTx member of the IMS.PROCLIB
data set. IMS routes outbound
messages sent to the LU 6.2 descriptor by using the local LU name
specified in the OUTBND parameter.
Use the
/CHANGE DESCcommand to change the local LU for a LU 6.2 descriptor.Use the
/DISPLAY DESCcommand to display the local LU and other descriptor specifications. - By specifying an LU name in the OUTBND parameter of the DFSDCxx startup procedure. When an LU name is specified in the OUTBND parameter of the DFSDCxx startup procedure, the specified LU serves as the default LU for all asynchronous outbound conversation messages, regardless of which LU received the original inbound conversation.
- By specifying the local LU option APPCLLU=Y in the DFSDCxx startup procedure. When the local LU option is specified, IMS routes asynchronous outbound conversations through the LU that received the original inbound conversation.
- By overriding any LU name specifications in the LU 6.2 Edit exit routine (DFSLUEE0).