Enabling and using OTMA

The following topics describe IMS tasks related to the OTMA environment, as well as how IMS operates in an OTMA environment.

Enabling OTMA
To enable IMS to use OTMA, specify the z/OS® cross-system coupling facility (XCF) group name and IMS OTMA member name during system definition.
OTMA descriptors
OTMA provides two types of descriptors: an OTMA client descriptor and an OTMA destination descriptor.
OTMA support for IMS-to-IMS communications
You can send OTMA messages from a local IMS system to a remote IMS system by using IMS-to-IMS TCP/IP communications.
OTMA-supported exit routines
Several exit routines delivered with IMS are specifically for OTMA. OTMA also supports several other exit routines delivered with IMS that are not specific to OTMA.
Administering IMS for OTMA
The following topics describe IMS administration considerations for OTMA.
IMS termination and OTMA
When IMS terminates, OTMA attempts to notify OTMA clients and might take additional actions depending on the circumstances.
OTMA restrictions and requirements
A number of general restrictions and requirements apply to OTMA.
Managing system resources and OTMA
OTMA uses IMS system resources. A variety of factors affect how well OTMA uses those resources and there are a number of ways to monitor that usage.
OTMA security
Security for OTMA is enforced by RACF® or a similar security product. The following topics describe implementing security for OTMA and OTMA clients by using RACF.
Using DL/I calls in an OTMA environment
Certain DL/I calls have special considerations when used with OTMA.
OTMA program-to-program switch processing
Two types of message switch occur in OTMA: commit-then-send, and send-then-commit.

Parent topic: Open Transaction Manager Access (OTMA)