Enabling or changing MULTIRTP support in an OTMA super member

Support for parallel active RESUME TPIPE requests (MULTIRTP) by an OTMA super member tpipe queue is determined by the MULTIRTP value in the client bid request of the first client to connect to the super member group.

To change the MULTIRTP value of an existing super member group, you must terminate all client connections and re-establish the client connections after the clients are configured with the intended MULTIRTP value.

Procedure

  1. If you are changing the MULTIRTP value of an existing super member group, terminate all data store connections to the super member group.
    For connections from IMS Connect, you can stop the data store connections by specifying any of the following commands:
    • Type-2 UPDATE IMSCON TYPE(DATASTORE) NAME(datastore_name) STOP(COMM)
    • WTOR STOPDS datastore_name
    • z/OS® UPDATE DATASTORE NAME(datastore_name) STOP(COMM)
  2. Configure the OTMA clients with the MULTIRTP value that you need.
    For IMS Connect, you can specify the MULTIRTP parameter in either the IMS Connect system configuration or in the definition of individual data store connections.
  3. Start the OTMA client connections to the super member.
    For connections from IMS Connect, you can start the data store connections by specifying any of the following commands:
    • Type-2 UPDATE IMSCON TYPE(DATASTORE) NAME(datastore_name) START(COMM)
    • WTOR STARTDS datastore_name
    • z/OS UPDATE DATASTORE NAME(datastore_name) START(COMM)

When the data store connections are started, the OTMA super member takes the MULTIRTP value of the first client to connect and processes the RESUME TPIPE requests from the OTMA clients according to the new MULTIRTP value.

If any client attempts to connect to the super member group with a MULTIRTP value that is different from the MULTIRTP value that is established in the super member group, is rejected by a NAK message with sense code X'0037'.