|
This document provides an overview on new features and enhancements in Eloquence B.08.10
(including B.08.10 Update 1) and major user visible changes by product component.
The Eloquence B.08.10 release includes all applicable B.08.00 bug fixes up to June 2010.
Contents:
Installation
The Eloquence B.08.10 product release is installed in a separate location
(similar to B.08.00) and may be installed concurrently with a previous
Eloquence release.
This has a few consequences in the Eloquence installation
-
An existing installation of a previous Eloquence release is not updated or replaced
when installing Eloquence B.08.10.
-
A separate start/stop script and startup configuration file is used.
-
Any customizations in the config files of a previous Eloquence release are not carried
over and must be adapted manually. However, as the Eloquence config files are
backwards compatible, the previous config files could be copied or linked to the
Eloquence B.08.10 config directory.
-
Eloquence B.08.10 uses a different path for its binaries and the PATH environment
variable (or any absolute paths in scripts) may need to be adpated to take advantage
of Eloquence B.08.10. Though Eloquence B.08.10 is closely compatible with the
previous release and binaries may be mixed, it is recommended to make these changes.
-
Eloquence B.08.10 uses a different path for its shared libraries. To use the B.08.10
libraries, the SHLIB_PATH / LD_LIBRARY_PATH environment variables need to be set
appropriately. Though Eloquence B.08.10 is closely compatible with the previous release
and previous libraries may be used, it is recommended to make these changes.
Please refer to the following documents for details:
When updating from the B.7.10 release, please also read the upgrade hints
from the B.08.00 release notes.
Database server
Major database server changes include
-
The database server was enhanced to support item masking.
-
The database server was enhanced to support item encryption.
Other database server changes include
-
The server was enhanced to implicitly grant a DBA user administrative
capabilities on all databases (DADMIN and DBPRIV privileges).
-
The "operator" user property was added. This may be used to indicate
user accounts permitted to perform operational tasks. This allows to
be more restrictive with administrative accounts.
-
Added support for user password modification timestamp.
-
The HTTP status display has been enhanced and optional filter expressions similar
to the "dbctl list" command have been added (with update B.08.10.01).
Please refer to the following documents for details:
Database Client Libraries
Changes to the database client library include
-
The DBINFO mode 114 was added to support obtaining field status.
DBINFO mode 114 is similar to DBINFO mode 104 but returns field specific
status information rather than item numbers. DBINFO mode 114 is available
in both the image3k and the native client library.
See Database Server document for details.
-
A DBOPEN of an encrypted database returns status -812:0 if one or more
master keys are unavailable.
-
The DBUPDATE mode 2 on a master set was changed to return status 43:0 instead
of -804:0 when a duplicate key item value was found.
Changes to the image3k library include:
-
Corrected error message on db status -31 from "illegal mode" to "bad mode"
-
A compatibility problem with the DBFIND mode 4 when using wildcard search
was fixed (#3860).
DBFIND mode 4 allows to provide information on the length of its arguments.
However, with a wildcard search this only specifies the max. argument length.
A wildcard character may terminate the argument.
Previous Eloquence versions used the argument length to determine the search
term, possibly allowing multiple wildcard characters. However, this behaviour
differs from TurboIMAGE and might result in an unexpected status 17 returned.
-
The DBINFO mode 114 was added to support obtaining field status.
DBINFO mode 114 is similar to DBINFO mode 104 but returns field specific
status information rather than item numbers. DBINFO mode 114 is available
in both the image3k and the native client library.
See Database Server document for details.
-
A DBOPEN of an encrypted database returns status -812:0 if one or more
master keys are unavailable.
-
The DBUPDATE mode 2 (or DBUPDATE using the CIUPDATE flag for image3k) on a
master set was changed to return status 43:0 instead of -804:0 when a
duplicate key item value is specified.
TurboIMAGE did not support changing
a key item in a master set, the CIUPDATE flag only applied to detail sets.
With Eloquence, update of key items was supported but returned a status -804:0
in previous versions.
Database Utilities
Database utility changes include
-
The dbutil utility was enhanced to support item masking.
-
The dbutil utility was enhanced to support item encryption.
-
The dbkeyutil utility was added to support item encryption.
Other changes to database utilities include
-
dbctl was enhanced for encryption status and key management.
-
dbbexp, dbcfix, and fwaudit have been added a -M option for
specifying master keys when working with encrypted databases.
-
dbutil and dbdumpcat were enhanced for tracking
password change timestamps.
Please refer to the following documents for details:
Eloquence Language
Changes to the Eloquence programming language include
-
Fixed a limitation of the COMMAND statement that could result in
overflowing the symbol table, causing an ERROR 2 (#3376).
A COMMAND statement may grow the symbol table of the current program
segment (SUB/FN). This may eventually result in an ERROR 2 when
reaching the size limit of the symbol table. This enhancement limits
new entries to the symbol table to variables whenever possible.
-
Extend valid PRINTER numbers from -2:99 to -2:999 (#3843).
Previously, printer numbers were limited to the range of -2 to 99.
-
Added the POPUPBOX option to the Eloquence config file to allow
enabling function keys to interrupt a POPUP BOX statement in the text
based user interface (#3509).
When enabled, a defined function key or HALT interrupts a POPUP BOX
statement and returns -1 as the selected choice.
This function is enabled in the configuration file by specifying
the option POPUPBOX and the asssociated config value. For example:
option popupbox 7
The option value is bit encoded:
- 1 = Function key
- 2 = HALT
- 4 = ESC
Please note that this functionality is not available when using
the DLG driver.
-
Improved DLL interoperability with 32 and 64 bit Eloquence DLLs
(with update B.08.10.01).
The new eloqcore can now use 32 and 64 bit Eloquence DLLs that
are linked against the most recent libeqdll library.
-
Update B.08.10.01 also fixed a limitation in the decompiler ("LIST")
that caused a problem with array member variables passed to a SUB/FN
Eloquence WEBDLG
WEBDLG enables dialog based Eloquence programs to use a web browser as a
user interface (requires Apache web server).
Changes to the Eloquence WEBDLG include
-
The Eloquence WebDLG module for the Apache 1.3 web server is no
longer shipped. The Apache 1.3 web server is considered obsolete and
is no longer supported by the Apache project.
We recommend to use the Apache 2.2 web server for new installations.
Eloquence JDLG
JDLG implements a JAVA (tm) based graphical user interface for dialog based Eloquence programs.
Changes to the Eloquence JDLG include
-
New JDLG 1.5.5 release available
|
|