Welcome to the B.08.30 test release
Eloquence B.08.30 is currently in beta test stage and has not yet
been released for production use.
A production release is expected to be available in Q3/2018.
By making beta test versions available we hope to encourage wider
testing. Please contact
to share your feedback or report a problem.
This test release is available under the terms of the Eloquence Beta Test
Downloading and installing the software indicates your agreement to the
Beta Test terms and conditions.
This test release may not meet the release criteria for quality or
performance and is intended for test and non-critical use only.
The Eloquence B.08.30 release extends on the B.08.20 release and
delivers improved efficiency and scalability as well as updated technologies.
Major changes include:
Database server performance improvements.
The Eloquence database was further enhanced to improve performance and
efficiency on contemporary hardware.
The Eloquence B.08.30 database is expected to deliver noticeably improved
throughput with a lower CPU utilization for a variety of workloads.
The database adds speculative read-ahead to improve disk I/O rates
The replication slave server uses parallel disk I/O to improve
replication performance when disk latency was limiting performance.
Improved FTS scalability and new FTS dictionary pools.
Support for compressed forward log files.
On the HP-UX and Linux platform support for local sockets was
introduced as an alternative to local TCP sockets to connect
the database server. Local sockets are more efficient than regular
TCP sockets and do not require system configuration.
Database security improvements.
Most visibly, a new hashing scheme is used to secure database passwords.
A new DLG protocol was designed to improve JDLG usability
in cloud environments or using high latency networks (such as
Both the number of messages between JDLG and the application
backend is reduced as well as the amount of traffic.
The new protocol supports compressed bulk transfer, allows for
server side caching to reduce the number of round trips and
supports encrypted transport.
Information on the DLGv2 behaviour in eloqcore is
described in the DLGv2 document.
The Java based GUI (JDLG) comes in a new major version, and
delivers noticeably improved performance and efficiency.
JDLG improves performance with existing environments and is
noticeably faster when used with B.08.30 using the new
DLG protocol version.
The JDLG 2.0 beta version is
The terminal handling was enhanced to
support a Unicode environment on all platforms.
On Linux and Unix, the terminal subsystem supports UTF-8
The eqpcl utility was enhanced to support a subset of unicode characters.
Thread safe database client libraries.
The Eloquence image3k (and ftc) libraries
support an additional "Big Endian" byte order on "Little Endian" platforms.
This will simplify migration of Cobol based IMAGE applications to Linux.
Fixed a number of issues with more than 2 billion records in a table.
A number of database utilities had minor issues with database
tables with more than 2 billion records. query3k simply failed
and the database server could abort when exceeding 4 billion
records per table.
Systemd support on Linux.
The eloqsd server was enhanced to support
IPv6 and TLS-encrypted network connections.
Installation and Upgrade
Please refer to the Eloquence B.08.30 installation documents below
for an overview of Eloquence installation and platform specific details,
as well as information on updated License Keys.
Eloquence B.08.30 is upwards compatible with previous Eloquence versions.
A database created with B.08.30 should not be used with previous
However, it is supported to move databases to older releases when no new
functionality is used.
Please notice that creating additional FTS indexes (or re-creating
existing ones) with B.08.30 enables an enhancement for FTS keywords
with a large number of references.
This is currently not supported by the previous Eloquence releases
and requires rebuilding any FTS indexes created with B.08.30.
Eloquence B.08.30 includes or makes use of several third party and
open source projects. Details can be found in the following document:
The Beta Changes Document lists some
user visible changes introduced in the beta cycle.