Routing asynchronous callout responses to an IMS Connect TCP/IP client
To route the response to the TCP/IP client, the IMS application program that issues the asynchronous callout request message must capture the IMS Connect TMEMBER and OTMA TPIPE names used by the initiating TCP/IP client.
Upon receipt of the response to the callout request, the IMS application program that processes the response uses the TMEMBER and TPIPE names to return the response to the correct TCP/IP client. To successfully route the response to the correct TMEMBER, you will also need to use either the OTMA destination descriptor or the OTMAYPRX user exit and DFSYDRU0 exit routine.
To make the TMEMBER and TPIPE names available to the IMS application program that processes the response, the names can be included as part of the data of the callout request and response messages or the names can be saved in a temporary database that is accessible to the IMS application program that processes the response.
If a temporary database is used, the IMS application program processing the response must use further correlation to retrieve the correct TMEMBER and TPIPE names when the response transaction is returned. When correlation is complete, the IMS application programs sends the response back to the original IMS Connect TCP/IP client by making a CHNG call and an ISRT using the TMEMBER and TPIPE names.