Application programming for asynchronous callout requests

An application program issuing an asynchronous callout request must include in the callout request message any data required by the external application it is calling.

If the correlation of a response from the external application is required, the calling application program must also capture any data required for correlation purposes. The application program must also include the tpipe name of the dedicated OTMA asynchronous hold queue for the callout request function.

If any correlation data is included in the callout request message, you must ensure that the external application program tolerates the data and sends it back with the response.

Optionally, the application program might also store data in a database for correlation purposes or for the results of any IMS processing that must be returned with the callout response.

An application program processing a response to a callout request can process any correlation data returned by the external application program, retrieve any correlation data or IMS data stored in the callout database, and return the final data to the appropriate queue, terminal, or user as appropriate.

If you are using IMS TM Resource Adapter, a Java™ application that processes a callout request externally can be configured to listen to the OTMA asynchronous hold queue by issuing a looping RESUME TPIPE call with an appropriate wait time. The Java application program might also be designed to preserve the correlation data and send it back with the callout response.