The synchronous callout function for IMS Version 10

For synchronous callout requests, an IMS application program that runs in an IMS dependent region issues an IMS call (the DL/I ICAL call) and waits in the dependent region to process the response. When the ICAL call is issued, IMS generates a correlation token for synchronous callout requests. This correlation token is included with the callout request and must be returned to IMS with the response to route the response back to the requesting IMS application program.

You can issue a callout request from an IMS application and synchronously receive the response by using any of the following approaches:

• IMS SOAP Gateway Version 10

  IMS SOAP Gateway enables IMS applications to interoperate outside of the IMS environment through SOAP to provide and request services independent of platforms, environments, application languages, or programming models. For IMS synchronous callout requests, IMS SOAP Gateway handles the correlation of requests and responses for you. IMS SOAP Gateway Version 10 iFix 2 is required.

  See the IMS SOAP Gateway Web site for more product details and download information.

• IMS TM Resource Adapter Version 10

  The IMS TM resource adapter enables you to easily create Java applications that access new and existing IMS transactions over the Internet, or process IMS callout requests to services or data over the Internet. IMS TM Resource Adapter Version 10.3 is required.

  See the IMS TM resource adapter Web site for more product details and download information.

• Your own IMS Connect TCP/IP client applications

  You can write your own IMS Connect TCP/IP clientapplications or use a vendor-supplied solution that uses TCP/IP and the IMSConnect protocol to retrieve callout requests. Your custom IMS Connect clientapplication must issue a RESUME TPIPE call to an OTMA routing destination,also known as a transaction pipe (or tpipe), that is defined in an OTMAdestination descriptor. This transaction pipe holds the callout requests.Your custom IMS Connect TCP/IP client application must poll the tpipe toretrieve the callout requests.

The IMS synchronous callout function is available in the following APARs.

APAR requirements for IMS Version 10

APAR requirements for IMS Version 11 QPP

APAR	Description
PK81543	OTMA support for synchronous callout
PK81544	IMS Connect support for synchronous callout
Not yet available	Synchronous callout IVP sample
PK85023	JBP and JMP support for issuing callout requests Important: Apply this APAR if you are issuing callout requests from Java applications that run in a JBP or JMP region. The JMS interface classes are also required. The interface classes are contained typically in the jms.jar file. You can download the bundle that contains the jms.jar file from http://java.sun.com/products/jms/docs.html, and click Downloadthe version 1.1 API Documentation, Jar and Source.
	IMS TM Resource Adapter support for synchronous callout Important: Use IMS TM Resource Adapter Version 10.3 for your testing. Download the IMS TM resource adapter from the IMS TM resource adapter Web site.
	IMS SOAP Gateway support for synchronous callout Important: Use IMS SOAP Gateway Version 10.1 with the latest iFix for your testing. Download IMS SOAP Gateway from the IMS SOAP Gateway Web site.

Synchronous callout documentation

The following table lists where you can find more information about the synchronous callout function for IMS Version 10.

Important: For IMS Version 11 QPP customers, before the IMS Version 11 QPP information center is updated in June, the same synchronous callout related content in the IMS Version 10 information center also applies to IMS Version 11. Refer to the Version 11 APAR closing text for additional Version 11 specific information for the two OTMA related enhancements.