Compiled XML Conversion artifacts generated by prior versions of IBM®Rational® Developer for System z®`are compatible with the IMS Synchronous Callout (ICAL) only if the mapped 01 level language structures begin with LL and ZZ fields.
IMS V10 SPE introduced the IMS Synchronous Callout function (ICAL). This function allows IMS applications to synchronously invoke web services through the IMS SOAP Gateway. Unlike the IMS Asynchronous Callout function (ISRT), where the response from the remote web service always starts a new transaction instance, the ICAL function allows an IMS application to wait for the response and immediately act on the response. In order to allow IMS applications to communicate synchronously with remote web services, the ICAL function bypasses traditional IMS message queues.
Because IMS Synchronous Callout (ICAL) function bypasses IMS message queues, the function requires that the request and response data for the remote web service are entirely contained in at most two 01 level language structures, one for the request and one for the response. In addition, language structures do not need to begin with LL and ZZ since these fields are only in used with asynchronous messaging; if these fields are defined in an 01 level language structure used with ICAL, the fields are treated as data.
When using IMS SOAP Gateway Single-service projects to generate Compiled XML Conversion artifacts for a service requester, specify either synchronous (SYNC) or asynchronous (ASYNC) messaging in the "Callout message type" combo-box on the "IMS SOAP Gateway Service Requester" wizard page.
When using the Enterprise Service Tools batch processor, specify the IMS SOAP Gateway Callout message type using the GEN_IMS_MESSAGE_TYPE attribute in CodegenProperty.