[z/OS]

Calling existing IMS transactions with optimized local adapters over OTMA

Existing unchanged IMS transactions that run as Message Processing Programs (MPPs) or fast path programs (IFPs) can be called using the WebSphere® Application Server for z/OS® optimized local adapters over Open Transaction Manager Access Callable Interface (OTMA C/I) support. This support is provided by a new set of native modules introduced with optimized local adapters that use the IMS OTMA C/I.

Applications that are deployed on WebSphere Application Server for z/OS and must call existing IMS transactions, use the ola.rar file to reach the OTMA C/I interfacing modules. There are several new connection factory attributes that allow applications to supply the name of the target IMS system and the associated OTMA XCF information. There is also an attribute added that allows the application to set the Sync Level that is used for the exchange. See the topic Connection factory considerations for optimized local adapters for more details about these parameters.

Message Format Requirements

Current support requires that request and response messages be single segment, with maximum send, and receive segment size of no larger than 32760 bytes, including the message header.

The following is the message format expected for calls to IMS from applications in WebSphere Application Server:
<----------------- HEADER ---------------->   <------ DATA ------>
LL        + ZZ        + IMS Transaction Name + Message request data
(2 bytes) | (2 bytes) | (8 bytes)            | (up to 32744 bytes)

The Transaction Name in the message is used for the call to OTMA C/I and must be a transaction defined and reachable in either an IMS MPR or fast path dependent region.

Response data is always returned with the following format:
<----- HEADER ----->   <------------------ DATA ----------------->
LLLL                  + Message response data
(4 bytes)             | (up to 32756 bytes) 
The CICS/IMS Java Data Binding wizard in Rational® Application Developer is used to create helper classes with setter and getter methods that can be used to handle mapping data to and from Java objects and binary form for both messages sent to IMS from WebSphere Application Server and response data.
Attention: The response message is always preceded by the 4 byte integer message length, followed by the response message that is the area mapped by the Data Binding wizard.



Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=cdat_callexisttrans
File name: cdat_callexisttrans.html