TRX - DECENTRALIZED TRANSACTION MONITOR ALSO FOR Z/LINUX
Simple removal of IMS/TM or CICS on the IBM mainframe
For IMS/TM applications on the mainframe, a compatible run-time environment on Linux and z/Linux is created, so that IMS/TM or CICS is practically no longer needed. As a result, CPU time and license costs on the mainframe can be saved.
Migration of IMS/TM or CICS application in a decentralized environment also for z/Linux
Online applications using IMS/TM or CICS can be ported to Linux without major modifications, meaning several Cobol run-time environments can be supported. This means that application programs on the target system generally only need to be recompiled.
Emulation of IMS/TM, i.e., CICS using Linux
The TRX Engine is a lightweight, highly robust, and scalable transaction monitor for Linux and z/Linux. It provides a run-time environment via LINUX whose API is compatible with IMS/TM such as CBLTDLI. CICS support is provided for basic functionality. Extremely short response times and very good load distribution are special characteristics of the TRX Engine.
Architecture of the TRX Engine
Lightweight and flexible architecture is the basis of an extremely robust and highly scalable system. As a result, high performance and stability is achieved.
Different front-ends are supported
Classic dialogue applications for emulation are just as possible as the simple integration of a JavaEE environment by using an IMS connect adapter.
Monitoring web interface
Using a clear web interface, the run-time behavior of the TRX Engine can be read in real time.
Admin web interface
In addition to intuitive usage and simple administration, numerous pieces of information are displayed. These can also be read using a JMX interface.
Significant cost savings though a quick, simple, risk-free migration of IMS/TM application programs to a decentralized platform and z/Linux
Valuable business logic lies in the existing programs. Therefore, new development is often associated with significant expenditure and risk. When carrying out a migration on the TRX Engine, there is no need to modify the programs. This way, expenditure and risk are minimized.
Seamless integration into the existing infrastructure and system landscape
The TRX Engine supports numerous standard interfaces, so that they can be integrated trouble-free into the existing system landscape such as into the TN3270 record, IMS connect adapter, JMX/HTTP, LDAP. On the one hand, this means that classic front-ends can be connected and, on the other hand, that it is easy to integrate into a Java/JavaEE environment. As an operating system, the TRX Engine requires Linux. As a database, DB2 z/OS, DB2 LUW, and Oracle are supported and can be used alongside each other.
The existing development process and employee know-how are still used
With the CM toolset from our product family, the familiar and proven mainframe development process is continued in the decentralized world. The programming language and run-time environment remain practically unchanged, so that employees can make progress in the new environment without expensive training or learning processes. Therefore, getting used to a new programming paradigm or release concept takes no time at all.