eloqcore

• Calling a subroutine with a file argument could result in ERROR 1000 on the HP-UX platform.

• On the HP-UX platform a SORT BY statement could terminate eloqcore with an error message from the dynamic linker (dld.sl) complaining about unresolved symbols.

• On the Linux platform the output of a "beep" could be delayed. In background mode (eg. cron job or output redirected) a "beep" could cause an abort.

• Closing a printer (PRINTER IS 8) could fail with ERROR 133 or 143. When a printer was closed without having printed anything the operation could fail with status 133 or 143.

• MAT A=B could copy excessive elements if the target array had more elements than source array. This could lead to subsequent failure due to garbaged contents if the target array was REDIMmed afterwards.

• DUMP SEGMENTS statement caused a segment violation (Linux platform) or GPF (Windows platform) if the main segment was empty. DUMP SEGMENTS is an unsupported statement, originally created for debugging purposes, which can be used to display subroutines and functions currently present in memory.

  Usage: DUMP SEGMENTS [numeric_arg]
  If numeric_arg is nonzero the file the subprogram was loaded from is displayed in addition.

• ERRMSG$(n) caused a segmentation violation on the Linux platform.

• When used with the Eloquence IDE or eqstart utility eloqcore was unable to redirect its error output into the IDE output window if a character mode program was executed.

• On Windows a DLG SET or DLG LOAD failed with ERROR 654 when empty strings where passed.

• On the Windows platform DLG SET ".driver" uses localhost as requester instead of the hostname when the dlgsrv is executed on the same system. This fixes a failure to startup DLGSRV in a un-docked laptop.

• The IP address is passed instead of the hostname when connecting to dlgsrv. This avoids a failure with an inconsistent or incomplete hosts file.

eloqdb6 server

• eloqdb6 could panic during volume recovery if transaction log meta information is damaged.

• Under rare conditions 16 bit integer key values were incorrectly inserted into an index. This could result in a subsequent database status -96 (bad link to master set).

• The HTTP status display could show garbaged server configuration.

• A deadlock condition could occur during DBPUT and DBUPDATE in rare cases causing the affected tasks to hang infinitely.

• A zero record number in the free record list could result in a eloqdb6 panic during DBPUT.

  The zero record number is placed into the record free list during pre-commit phase of a DBDELETE operation to ensure that the free list does not need to be expanded during the final commit phase. There was a small window of opportunity that a concurrent DBPUT would request a new record number and could get that reserved entry. This situation was not expected and the server paniced.

• Due to a race condition, simultaneous DBOPEN and DBCLOSE operations could cause a server panic in rare situations.

• Transaction isolation in the fixrec subsystem did not work correctly. This could cause a server panic if a commit operation was executed concurrently to a read operation.

• dbctl dbstore could cause a buffer leak when running out of disk space. This caused a subsequent server panic.

• dbctl dbrestore could cause a server panic when using dbutil subsequently to modify the database catalog.

• dbctl backup stop could cause an eloqdb6 panic.

• An eloqdb6 crash during on-line backup could cause a subsequent failure to open the volume files: "Vol_Open() failed with VOLE018"

• Crash recovery could fail with an internal error.

• A corner case with disabling on-line backup mode could cause data corruption if a checkpoint operation was executed concurrently.

• Disabling on-line backup mode could cause a server hang.

• A server crash while in on-line backup mode could cause an internal failure the next time on-line backup mode was enabled.
  Due to a related reason, dbfsck or dbvolextend could refuse to modify a volume, complaining that the volume is still in on-line backup mode.

• eloqdb6 could abort with an internal failure.

• When a client was disconnected (killed) eloqdb6 could cause a high load when the associated internal thread was blocked internally.
  For example, when eloqcore is blocking on a DBLOCK and is killed the eloqdb6 process could busy waiting until the lock becomes available, consuming almost all CPU resources.

• Crash recovery could leave unassigned index and system catalog data pages. In rare situations, this could lead to data corruption.

• Crash recovery could cause fixrec meta data corruption.

• dbctl dbrestore could cause a deadlock.

• DBUPDATE mode 1 on a standalone detail set returned status 41.

• DBFIND/DBGET on index item or QFIND on index item could fail.

• A race condition in cache management could cause an eloqdb6 panic.

• A race condition in Node_Open() could cause an eloqdb6 panic.

• On the HP-UX and Linux platform a server shutdown could cause errorneous messages.

• dbvolcreate utility could output errorneous warnings about a possible "PIN LEAK".

• The eloqdb6 server process could output errorneous warnings about a possible "PIN LEAK".

• The dbstore operation failed to release a node lock which could cause a subsequent eloqdb6 server panic.

• After opening more than 32767 databases in succession in a single session eloqdb6 could provide a possibly wrong or duplicate dbid.

eloqsd service (Windows NT)

• The eloqsd server did not correctly setup user permissions. This could cause subsequent failures e.g. when accessing a network resource from an Eloquence program.

• The eloqsd server sometimes failed to read its configuration files eloqsd.share and eloqsd.user correctly. This could cause the eloqsd server to hang when reading its share or user configuration.

dbimport

• dbimport failed to recognize import files which include structural information (created by dbexport -r).

schema processor

• The schema procesor did not handle 8 bit characters ("Umlaute") correctly on the HP-UX platform. This could result in syntax error messages in schema definitions when 8 bit characters were used in comments.

• A combination of primary path and sort item specification caused an internal failure.

dbfsck

• dbfsck could report an errorneous fixrec meta data inconsistency. When using write mode (-w commandline argument) this could cause bad fixrec meta information written back to the data volume which could cause a subsequent eloqdb6 panic due to inconsistent fixrec meta information.

Eloquence IDE and eloqstart utility (Windows)

• An internal overflow condition caused a GPF in the Eloquence IDE when a directory was displayed in the Explore window which contained a file with an invalid modification date.

• In rare situations a GPF was caused when the Explore window was opened. An assumption was made concerning the network hierarchy which was not always true. This has been fixed by re-implementing the enumeration algorithm more defensively.

• Although eloqcore supports character mode programs with A.06.20, the Eloquence IDE and the eqstart utility did not support this mode correctly (the eloqcore window was always hidden).

Run Server (Windows)

• The Run Server could hang after accepting a network connection.

dlgsrv (Windows)

• The EDITTEXT.ins and EDITTEXT.delln attributes caused the 16bit and 32bit dlgsrv(32) driver to crash if the cursor was positioned at the end of the current content.

Linux libc6 executables could fail

• Executables failed on Linux libc6 with __register_frame_info undefined on Linux distributions other than SuSE Linux.

eloq (HP-UX)

• The eloq program could abort with an internal failure.

    Assertion failed: ptptr->lock == PTY_LOCKED
  

• The eloq program was limited to 256 pty devices.