XATMI has been standardized by X/Open and is a program interface for a communication resource manager which enables transaction-logged client/server communication.
The XATMI program interface is based on the X/Open CAE Specification “Distributed Transaction Processing: The XATMI Specification” of November 1995. Knowledge of this specification is essential for understanding this chapter. This chapter describes the XATMI interface for openUTM clients using UPIC.
For information on OpenCPIC, please refer to the manual “openUTM-Client for the OpenCPIC Carrier System”.
With a few exceptions, the description of the XATMI interface is platform-independent. The exceptions are indicated in the text.
Terms
The following terms are used in this description:
Service | A service function that is programmed in C or COBOL in accordance with the XATMI specification. XATMI distinguishes between two different types of services: end services and intermediate services.
|
Client | An application that calls service functions. A UTM application containing the service functions in C and/or COBOL. The service functions can comprise a number of program units. |
Request | A request is a service call. This call can be initiated by a client or by an intermediate service. |
Requester | The XATMI specification uses the term “requester” to refer to the application that calls a service. A requester can be either a client or a server. |
| Typed buffers | Buffers for exchanging type-encoded and structured data between communication partners. With these typed buffers, the structure of the exchanged data is implicitly known to the carrier system and the application, and is also adapted automatically (encoded, decoded) in heterogeneous connections. |