New enhancements in the Release 4.2.1 from 1st March, 2012 ...
TABEX/4 loads tables into ESA data space (IBM zSeries Mainframe, z/OS) or in main memory (Linux, Unix).
Using tables in this main memory optimizes access time and minimizes CPU consumption. This results in significantly less mainframe maintenance cost.
TABEX/4 offers
API interfaces for JAVA, C/C++, Cobol, PL/1, Assembler and for the product internal 4GL, the programming language SSL. With the help of this language, customer specific logic for exits can be programmed directly on the user interface or by special batch functions.
For tables which are accessed for read-only purposes, TABEX/4 generates local table replicates. This reduces the I/O on the server where the database is located. Network load decreases because data are locally available and do not have to be transported through the network.
By reducing I/Os, CPU usage decreases drastically. On average, compared to direct DB2 access, a decrease of 10%, and in some cases to 2%, is achieved, resulting in savings to license and maintenance costs, especially on mainframes.
Significant costs arise from the time and effort needed to program and test application programs.
With the TABEX/4 table access technology, you can source out
into TABEX/4 tables.
Independent of the data source (e.g., DB2), data access performs similar to direct data input in the program.