<
  Manycom DTS
 
Manycom Solutions

Home > Products > Manycom DTS

 
 

Product Description

Contents
Introduction | Benefits | Technical Description | Cases and References | System Requirements | Prices | Availability and Support | Manuals and Documentation | License and Maintenance Agreements

Introduction

  • Manycom DTS is an AS/400 implementation of DTS (Distributed Transaction System) - a set of compatible communication middleware software for real-time messaging and distributed processing in multi-platform and multi-vendor environments.
  • DTS allows using TCP/IP socket, SNA/APPC and DECnet connections, and is available for practically all 'relevant' platforms such as the IBM AS/400 and iSeries, IBM MVS/CICS, IBM RS/6000/AIX, Compaq OpenVMS and VAX/VMS, Compaq Tru64 UNIX, Compaq/Digital ULTRIX, HP-UX and HP MPE/iX, Intel PC/LINUX, Windows 3.1, 3.11, 95, 98, Windows NT and 2000.
  • Each DTS can be used in two different modes: DTS 'front-end' (client mode) and DTS 'back-end' (server mode). DTS provides also ASCII/EBCDIC character code conversion, data compression, automatic message queuing ('spooling' or store-and-forward of the data messages), logging, file copy, 'echo test' application, network monitor and traffic statistics functions.
  • DTS client provides for a 'client' application a high-level API and the necessary communications functions, which make it extremely easy for the client application to exchange and process data messages with the 'server' application via the DTS/client-to-DTS/server connection.
  • A client application can handle the entire real-time transaction with a single program call to the DTS client API program: open the connection to the selected DTS server node, start the selected server application, send a data message (data buffer) to the server application, receive the response data processed and returned sent by the server application and DTS server, and close the connection.
  • DTS is based on the Remote Procedure Call (RPC) principle. The client application can via the DTS client and DTS server start the remote server application in order to exchange and process data with it.
  • DTS opens and closes the communications session automatically and separately for each call to the DTS API. The corresponding physical connection is opened and closed as configured for the line type.
  • The DTS client and server APIs are so easy to use, that all programmers can without special training build solutions where the client and server applications in different systems (AS/400, UNIX, Windows…) co-operate and communicate with each other by exchanging data messages.
  • DTS communication based on exchanging data messages is the simplest and most effective way for real-time application-to-application communication facilitating optimal use of system and line resources thus providing optimal throughput and response time.

The following figure describes the role of DTS.

DTS for real-time communications

The entire DTS transaction (time between the call to the DTS client API program and return from the call) can take less than ten milliseconds, typically less than one second, or sometimes few seconds depending on the load of the systems, processor speeds, connection type, line capacity and the complexity and processing time needed by the server application.

Easy synchronization

One of the benefits of DTS is, that the client application always gets the response message (return data) from the server application during the same call. This means that the input and output (response) messages are automatically 'synchronized'.

High-level and easy to use API

The client application always calls the DTS client API program with four parameters: two for the 'input data' and 'input data length' and two for the 'output data' and 'output data length'. The DTS server when calling and passing the data to the server application uses the same four parameters.

This is how DTS actually makes the location of the server application and server system and type transparent to the client application. The client application doesn't need to know anything about the 'technique' behind the DTS client interface!

DTS client can be seen as a ready-made communications component available for your client applications, and can be called from any client application regardless of the programming language such as RPG, CL, C, or COBOL. The same applies to the DTS server. DTS server can call any server application, which provides the call interface with the specified four parameters.

The main benefit of DTS is that the programmers do not need to program and test the necessary communications functions in their applications or know anything about the lower-level TCP/IP socket, SNA/APPC or DECnet programming. DTS is robust software already tested in hundreds of applications.

Since the execution of the whole transaction is performed during the single and simple call with only four parameters, any programmer can learn to use DTS in fifteen minutes without special training!

DTS takes care of the complicated communications functions and operations in the lower-level communications interfaces, interprets and maps the return codes to DTS return codes passing them to the applications, and keeps on the communication and error logs.

Where to use DTS

Real-time messaging based on DTS applies very well to be used with all the supported communications architectures and network types including the TCP/IP connections and Internet. DTS provides an excellent communications solution for practically all 'traditional' real-time communications needs.

The effective communications based on data messages, the data integrity provided by the 'automatic synchronization' of the input and output messages with the program call, and the proven DTS spooling system make DTS ideal also for connecting WEB, WAP and other servers to communicate with the operative 'back-office' systems - be they local or remote.

 
Top of the page