The OTMA feature is installed with IMS TM as a part of the product, so it does not require any specific action to get installed. Also, any IMS system generation specifications for the OTMA implementation are not necessary. OTMA is a transaction-based connectionless client-server protocol that provides an access path and an interface specification for sending and receiving transactions and data from IMS.
OTMA is implemented for IMS in a sysplex-capable environment and as such it is restricted to the domain of MVS Cross System Coupling Facility (XCF). OTMA provides the facility for IMS to communicate efficiently with MVS applications other than VTAM. These MVS applications are named OTMA clients. These OTMA clients can be an IBM written application, independent software vendor's application, or user-written code. IMS Connect is a commonly used the OTMA client.
The OTMA client handles all device dependencies for a particular network protocol, which can be TCP/IP or System Network Architecture (SNA) and IMS TM can operate without needing any device-characteristic information. The OTMA client communicates with IMS by sending and receiving messages. It adds the OTMA message prefix to the input messages and it uses the message prefix to route the output data to the originating device or program. The application data section follows the message prefix, which can be the data sent to the IMS application, or the response sent to the client.
Messages that are destined for IMS/OTMA fall into the following categories:
When security checking is turned on in IMS/OTMA all messages received using OTMA clients must include security-related information in the OTMA prefix.
|
Copyright © 2014 CA.
All rights reserved.
|
|