There are some exciting new developments in the works
Find out what's next for Synergy/DE
We've helped you evolve your applications over the years--in many cases from green
screen to the most modern devices. So what's next? Come to the Synergy DevPartner
Conference and learn...
- What's new in Synergy DBL
- What's on our product roadmap
- What exciting new developments
we have in store.
Join us in Bristol June 18-20 or in Providence June 25-27.
Get more information about the conference at
New Synergy/DE 10.1.1a patch delivers more
Synergex's first patch to Synergy/DE 10.1 is now available to download.
In addition to numerous quality improvements, version 10.1.1a includes new features
that improve code optimization, make Synergy easier to use, and increase Synergy
DBL compatibility with other .NET languages. Features include:
- Case-insensitive SELECT queries
- String class methods for traditional Synergy
- Synergy .NET language enhancements
- Visual Studio enhancements
10.1.1a is supported on Synergy/DE's Windows, OpenVMS, and Unix/Linux platforms.
Learn more about 10.1.1a at the Synergy DevPartner
View the 10.1.1a
release notes (Resource Center password required).
Introducing the power and flexibility of
ISAM REV 6
By John Brunett, Senior Software Engineer
One of the highlights of Synergy/DE version 10 is a new revision of ISAM files.
REV 6 ISAM comes with several new features, as well as plenty of room for growth
before a future revision upgrade is required.
REV 6 includes a new on-disk file structure that's optimized for the new "Advanced
Format" large sector drives being sold today. All index blocks are now aligned to
4K by default. (As a result, to make room for the new 8K header and 4K default PAGE
size, you can expect empty ISAM files to take a slightly larger disk footprint.)
Along with the new file structure, a few other features are well worth mentioning.
One is a new key type called an autokey. An autokey is a key declared in
a file's record that is automatically filled-in by the Synergy DBMS. In Version
10.1, two types of autokeys are supported: a sequence autokey and a timestamp autokey.
The sequence autokey is simply an i8 counter that increments each
time a new record is stored. The timestamp autokey is an i8 datetime
(in microseconds) that is set to the current time when a record is stored and again
when the record is updated. Using the %DATETIME_FROM_I8 routine, you can convert
the i8 datetime value to a string similar to that returned by %DATETIME.
Both of these autokeys are guaranteed to be unique in a file.
Another exciting new feature is Change Tracking, which allows you to transparently
keep track of all changes made to a file. After enabling Change Tracking on a file,
you can replicate to a central database changes made between two points in time
(snapshots), roll back changes made on a failed posting run, or access records exactly
as they were at a single point in time. How you actually use Change Tracking is
up to you, but the possibilities are endless. More details on Change Tracking will
appear in a future article.
If you're using GRFAs (which were released in version 9.3), you might be interested
in the new Stored GRFA feature. GRFAs can be used to implement optimistic locking.
One of the caveats discovered with this technique is that the extra overhead required
to generate the GRFA can have a negative effect on performance. Our new SGRFA file
option, however, moves that overhead to the STORE and WRITE operations, which occur
far less often than the READ/READS operations, thus resulting in better performance.
Also new with REV 6 is the ability to store text to a file's header and then programmatically
retrieve it later. What text you store is entirely up to you. You might store a
name to identify a particular file, your file's version string, a string that identifies
field types and offsets, or an entire XML document describing your file. Then, using
%ISINFOA (FILTXT), you can retrieve that information whenever you need it. Initially,
with Synergy version 10.1.1, you must define your file text upon file creation,
and the text is read-only. In a future release, you will be able to modify the file
text at any time.
To prepare for the future, the maximum TBYTE file size in a REV 6 file has been
increased from 1Tb to 256Tb. Also, there are several new defaults for REV 6 files:
static RFA is now default and is required for all files, the default PAGE size has
been increased from 1024 to 4096, and files configured with Change Tracking also
include the TBYTE (addressing=48) file attribute.
Patching and converting a prior-revision file to REV 6 are slightly different than
in previous releases. The isutl utility is now used in both cases.
Using isutl -p, small files are automatically converted, but larger
files that will take longer to convert are only patched. When patched, a file becomes
an intermediate REV 6 file (designated 4r6 or 5r6 when viewed from ipar).
This intermediate revision is much like the REV 5 revision, which was the result
of patching old revision 2 and 3 files. However, an intermediate REV 6 file is automatically
converted to a full Revision 6 file the next time it is cleared or rebuilt using
isutl. Also, you can choose to override the patch or convert decision
by explicitly specifying the isutl -qfile=[no]convert option.
To facilitate future growth, a Revision 6 file now contains a compatibility level.
As new file features are added that change a file's structure, using one of these
features in a file will appropriately elevate the compatibility level for that file
such that an older Synergy version will not be allowed access (although it will
still have access to files without that feature). This enables us to add new features
that require structure changes without requiring a new file revision to be introduced.
For more information about REV 6 ISAM, see the
Synergy Tools manual and the version 10.1
Quick Migration Guide.
Learn more about REV 6 ISAM at the Synergy
Synergy/DE pros, see if you can answer this question!
Assuming the following:
- myIPAddress resolves to a real host that can accept connections.
- myPort is a valid port on myIPAddress and will accept the connection.
- MYFILE.TXT exists (and in this case is 6088 bytes long).
- The program is linked against WND:tklib.elb.
What will the program below output?
- message box with Success!
- message box with Socket error = n (where n is the error number)
- message box with File error = n (where n is the error number)
- any of the above (a) - (c) could happen
- it won't compile
- it won't run
if (%transmit_file("MYFILE.TXT", myIPAddress, myPort, errFlag)) then
else if (errFlag > 0) then
xcall u_message("Socket error = " + %string(errFlag))
xcall u_message("File error = " + %string(-errFlag))
function transmit_file ,^val
req in argFileToSend ,a
req in argIPAddress ,a
req in argPort ,n
req out argErrorCode ,n
.define M_BADRET(f) if (argErrorCode = f) freturn false
group trxStartPacket ,a
trxStartPacket.soh = %char(1)
trxStartPacket.stx = %char(2)
M_BADRET(%get_actual_file_size(argFileToSend, fileChannel, trxStartPacket.length))
M_BADRET(%ss_connect(socket, argPort, localAddress))
packet_length = ^size(fileBuffer.bufferField)
M_BADRET(%get_buffer_from_file(fileChannel, fileBuffer.bufferField, actualLength))
;; in case we want to keep track of how much has been sent...
totalBytes += actualLength
if (actualLength != packet_length) exitloop
function get_actual_file_size ,^val
req in argFileName ,a
req inout argChannel ,n
req out argTotalLength ,n
xcall u_open(argChannel, "I", argFileName,,, errFlag)
freturn -errFlag ;; return negative value with file issues
xcall filnm(argChannel, actualFileName)
;; there are OS specific ways to do this as well as the ability to read to end of file and
;; determine the length that way.
;; For the purpose of this exercise, assume the "best" approach for the situation has been
;; followed and the result is in actualSize
;; We will leave determining the approaches to this to another exercise...
;; for now, we will hard code a value...
actualSize = 6088
argTotalLength = actualSize
function get_buffer_from_file ,^val
req in argChannel ,n
req out argBuffer ,a
req out argActualLength ,n
retval = 0
argActualLength = ^size(argBuffer)
catch (ex, @Synergex.synergyde.EndOfFileException)
;; we hit end of file, so figure out our actual length
argActualLength = %rsize
;; close the channel - we don't need it anymore
catch (ex, @Synergex.synergyde.SynException)
;; any other type of error should return a bad result
retval = -ex.Errno
;; before we return, we should try to close the file
catch (ex, @Exception)
;; any other type of error should just return a bad result, but we don't know the number
retval = -9999
;; before we return, we should try to close the file
Click here to read
Which libraries do you need when running Synergy/DE on Linux?
Recently, several customers have reported problems with missing libraries on Linux.
Unfortunately, the error returned is more mystifying than illuminating, with text
such as "no such file or directory" and no mention of the missing library name.
We suspect that a recent OS update may have caused this problem.
On all Linux platforms, Synergy/DE requires these libraries:
libstdc++.so.6 (required by the compiler)
libc.so.6 (required by all Synergy components)
libncurses.so.5 (required by the runtime -- dbr and dbs)
If these are not present on your system, download and install them using a package
manager. (Some common package managers are apt-get, dpkg, rpm, and yum.) For example,
you can download libraries for Red Hat from
http://rpmfind.net/linux/RPM/index.html, libraries for Ubuntu from
http://packages.ubuntu.com, and for information on Fedora packages start
There's an easy way to check which libraries are required by any application: Just
run the ldd (that's a lowercase 'L') command followed by the program name. This
command is supported on all Unix platforms. For example, to see which libraries
the Synergy runtime requires, you'd use this command:
For more information on Linux libraries and other Linux installation issues, see
KnowledgeBase article 2094.
Read a selection of recent articles
Microsoft rushes out early-bird release of Visual Studio 2013
Developers clamor for unified dev tools for Microsoft's 3 OSs
Java: Out of the spotlight, but still spry
Oracle reveals plans for Java security improvements
Synergex holiday reminder
Synergex will be closed on Thursday, July 4, in observance of Independence Day.
If you anticipate needing our services on this day, please
let us know.