Defining an IMS Connect super
member group for OTMA IMS-to-IMS TCP/IP connections
Using a super member group, you can configure OTMA to send
output messages to a remote IMS installation
through up to eight local instances of IMS Connect.
The use of a super member group is transparent to both the IMS application that sends the messages
and the remote IMS installation
that receives the messages.
The following figure illustrates the
use of a super member group with an IMS-to-IMS TCP/IP connection.
To configure a super member group to send OTMA ALTPCB messages
to a remote IMS installation
by way of an IMS-to-IMS TCP/IP connection:
Procedure
Define an OTMA destination descriptor in the DFSYDTx member
of the IMS.PROCLIB data set that
includes the following specifications:
SMEM=YES, to enable a super member group.
TMEMBER=super_member_name, to name the super
member group. For example, TMEMBER=SM01.
In the IMS.PROCLIB
data set, specify SMEM=super_member_name in the
DATASTORE statement of the configuration member for each local IMS Connect instance
that participates in the super member group. For example, if the super
member group is named SM01, specify SMEM=SM01 for each IMS Connect instance.
Modify the IMS application
program to specify the OTMA destination descriptor that you defined
as the destination for the output messages that it sends to the remote IMS system.
After the super member group is defined and the IMS application begins sending output messages,
OTMA distributes the output messages to each participating IMS Connect instance
in turn by using a round-robin algorithm.
OTMA dynamically
updates the super member round robin list each time an IMS Connect instance
joins or leaves the super member group.