OTMA super members and parallel RESUME TPIPE support

Enabling MULTIRTP support in a super member group can improve both the throughput of the super member group during normal operations and the failover support of the super member group if a member of the group stops for any reason.

When MULTIRTP support is enabled, messages on the super member tpipe hold queue are sent immediately on any available connection with an active RESUME TPIPE request without waiting for an acknowledgement to the previously sent message. If your OTMA clients require the output that is received from the super member to be processed in chronological order, do not enable MULTIRTP support.

When MULTIRTP support is not enabled, only one RESUME TPIPE is active at a time and the messages are not sent until an acknowledgement for the previous message is received.

All OTMA clients that connect to the same super member in the same IMS system must use the same MULTIRTP setting for parallel RESUME TPIPE request support.

The first client to connect to the super member defines the MULTIRTP setting for the super member group. If a client that connects to the super member after the first client has a MULTIRTP value that is different, the client bid request is rejected with a NAK and sense code X'0037'.