A UTM application can communicate with a variety of partners. Communication partners of an openUTM application are for example:
Terminals
The KDCS interface enables you to connect character-oriented terminals directly. You can use these terminals in line mode or - in openUTM on BS2000 systems - you can use screen forms (masks).
UPIC clients
UPIC clients are programs that use the CPI-C interface with the UPIC carrier system to communicate with the UTM application.
Transport system (TS) application
Transport system applications are programs that use the transport system interface directly to communicate with the UTM application, e.g. sockets. TS applications can also be other UTM applications.
- HTTP clients
HTTP clients are programs that use the HTTP protocol to communicate with the UTM application via the socket interface. Printers
You can create output jobs for printers from openUTM services (see section "Programming error routines"). Print jobs are also part of the transaction concept.
OSI TP, LU6.2 or LU6.1 partners
The partner may be another openUTM application or a UTM-Client application with the OpenCPIC carrier system, or it may be an application that uses a transaction system from a different manufacturer.
Message queues
In UTM services, messages can be written to message queues, from where they can be retrieved by the recipient at any time. These queues are also included in the transaction concept.
You use the same KDCS calls for communication with all these partners:
MPUT | to send a dialog message to the partner |
FPUT/DPUT | to send an asynchronous message to the partner or a message queue |
MGET | to receive a dialog message from the partner |
DGET | to read an asynchronous message from a message queue |
FGET | to receive an asynchronous message from the partner |
The following calls can also be used for communication within a UTM application:
You can use MPUT to send a message to a follow-up program unit which then can use MGET to read this message. However, you can also use service-specific storage areas to exchange information between program units of a service (KB and LSSB, see section "KDCS storage areas in openUTM").
You can use FPUT/DPUT to send asynchronous messages to local asynchronous services or message queues. The messages can then be read with FGET/DGET.