Synergy/DE

Synergy/DE (Synergy DBL, historically “Data Business Language”) is a compiled, business-oriented programming language and application platform from Synergex. Descended from Digital Equipment Corporation’s DIBOL, it began life in the late 1970s as a portable, DIBOL-compatible compiler and has evolved continuously for more than four decades - from PDP-11 minicomputers to Microsoft’s .NET runtime - while remaining a commercially supported product. It is one of the quieter success stories of business computing: rarely discussed in mainstream programming circles, yet still actively developed and running production systems that were first written a generation ago.

History & Origins

A Portable Answer to DIBOL

Synergy DBL traces its lineage to DIBOL (Digital’s Business-Oriented Language), a COBOL-influenced language DEC created for business data processing on its minicomputers. DIBOL was powerful for its niche but had a significant limitation: it ran only on DEC hardware.

Digital Information Systems Corporation (DISC) - the company later renamed Synergex - developed DBL in the late 1970s (around 1978) as a DIBOL alternative. Its pitch was portability: DBL targeted system integrators who combined DEC hardware with third-party peripherals and needed a business language that could run on more than DEC-only platforms. DBL also added the ability to chain to non-DBL programs and interface with subroutines written in other languages.

By mid-1979, DBL was being sold as a DIBOL-compatible compiler for the PDP-11 family running the RT-11 and RSTS/E operating systems.

Becoming a Structured Language

In November 1980, DBL 2.0 arrived as the first structured version of the language, introducing features such as INCLUDE files, global data storage, and fixed-length binary I/O. This marked DBL’s transition from a straightforward DIBOL clone toward a language with its own identity and modern-for-the-era conveniences.

Through the 1980s the language spread across platforms:

• January 1983 - a native-mode version for DEC’s VAX under VMS.
• Summer 1984 - the compiler was rewritten in C for portability, and an MS-DOS release followed.
• December 1984 - a Unix release (AT&T) added chaining and cross-language interfacing.

This C rewrite was strategically important: it decoupled DBL from any single hardware family and let the language follow the industry as computing moved off proprietary minicomputers.

Displacing Its Own Ancestor

In a notable turn, February 1993 saw DBL formally replace DIBOL on DEC’s own VAX, Alpha AXP, DEC OSF/1, and Intel-based SCO Unix systems. The portable descendant had become the standard where the original once ruled.

In 1996, DISC was renamed Synergex, and the surrounding toolset was packaged and marketed as Synergy/DE (the “DE” reflecting its role as a development and deployment environment). The language itself has been officially known as Synergy DBL since 2012.

The Object-Oriented and .NET Era

• April 2007 (Version 9.1) - object-oriented programming was added, and the compiler was rewritten to support objects and provide better error detection.
• November 2010 (Version 9.5) - support for Microsoft’s .NET Framework was introduced, giving developers access to .NET classes alongside native Synergy classes, together with Visual Studio integration.
• December 2014 (Version 10.3) - mobile support for Android and iOS.

These releases repositioned a business language born on the PDP-11 as a viable target for modern Windows, web, and mobile development without abandoning the enormous base of existing code.

Design Philosophy

Synergy DBL was built around a few durable ideas:

1. Business first. Like its DIBOL and COBOL ancestors, the language is optimized for data-heavy business processing - records, files, and reports - rather than systems programming or academic computer science.
2. Portability. From the outset, DBL’s reason for existing was to run business code across many platforms instead of a single vendor’s hardware.
3. Longevity and continuity. Synergex has consistently prioritized backward compatibility, allowing code written decades ago to keep running while the surrounding platform modernizes.
4. Self-documenting readability. The syntax is deliberately English-like and explicit, reflecting the business-computing tradition of code that operations staff and maintainers can read.

Program Structure

A Synergy DBL routine is organized into a data division and a procedure division. The data division declares the records and fields the program uses; the PROC statement marks the end of the data division and the start of the executable procedure division.

The example below is illustrative of traditional Synergy DBL structure; exact runtime routines vary by platform and version.

main
    record
        message, a13
    proc
        message = "Hello, World!"
        writes(1, message)
        stop
endmain

Fields are declared with a name and a type specification such as a13 (a 13-character alphanumeric field) or i4 (a 4-byte integer), a compact notation inherited from the DIBOL tradition of fixed-width, record-oriented data.

Object-Oriented Synergy

Since version 9.1, Synergy DBL supports classes, inheritance, and the object-oriented constructs that map onto the .NET type system in Synergy .NET builds:

namespace Example

    public class Greeter

        private mName, string

        public method Greeter
            required in name, string
        proc
            this.mName = name
        endmethod

        public method Greet, string
        proc
            mreturn "Hello, " + mName + "!"
        endmethod

    endclass

endnamespace

Key Features

• Integrated ISAM data store. Synergy’s Indexed Sequential Access Method engine, with hierarchical indexing, is a defining feature and the backbone of many production applications.
• Two runtime models. Code can run on the traditional Synergy runtime (using bytecode executed by the Synergy Runtime) or on Synergy .NET, which targets the .NET Framework and modern .NET on Windows and Linux.
• Cross-language interoperability. Longstanding ability to chain to and call routines written in other languages, plus xfNetLink for remote calls.
• Modern connectivity. APIs for XML, JSON, HTTP/HTTPS, and SSL, and RDBMS access to Oracle, MySQL, and Microsoft SQL Server via the SQL Connection product.
• Rich standard library. A substantial set of built-in subroutines, functions, classes, and APIs oriented toward business data processing.
• Tooling. Visual Studio integration with IntelliSense, wizards, and designers, along with debugging and profiling tools.

Evolution

Synergy DBL’s trajectory is unusual for a business language: rather than being frozen as legacy, it has been repeatedly re-platformed. The 1984 rewrite in C freed it from proprietary hardware; the 2007 object-oriented release modernized the language itself; and the 2010 .NET release let it interoperate with an entire contemporary framework. The Synergy/DE 12 generation is the current platform, with 12.3 designated the long-term support (LTS) release in 2024 for production stability and 12.4 feature releases for customers wanting the newest capabilities.

Current Relevance

Synergy/DE remains a commercially supported, actively maintained product. Its user base is concentrated among independent software vendors and enterprises with long-lived business applications - accounting, distribution, manufacturing, and financial systems - where the cost and risk of a full rewrite outweigh the benefits, and where Synergex’s continuity guarantees let teams modernize incrementally. Visual Studio tooling and the .NET runtime path give these organizations a route to web, cloud, and mobile without discarding decades of proven business logic.

Why It Matters

Synergy DBL is a case study in software longevity and pragmatic evolution. It shows how a language can be born in a specific commercial niche - portable DIBOL compatibility for PDP-11 integrators - and survive by continually following the industry’s platform shifts rather than resisting them. Few languages can claim an unbroken commercial lineage from the RT-11 and RSTS/E era to modern .NET. For the businesses that depend on it, that continuity is precisely the point: the code they wrote decades ago still runs, and can still be extended, today.

Key Takeaways

1. Synergy DBL descends from DEC’s DIBOL, created by DISC (now Synergex) in the late 1970s as a portable, DIBOL-compatible alternative.
2. It has been continuously re-platformed - PDP-11, VAX/VMS, MS-DOS, Unix, Windows, and .NET - since first being sold in 1979.
3. An integrated ISAM data store and record-oriented design make it a business-data language at its core.
4. Object orientation (2007) and .NET support (2010) modernized both the language and its ecosystem.
5. Synergy/DE 12 is the current platform, with 12.3 as the 2024 LTS release.
6. Backward compatibility and longevity are the platform’s central promise, sustaining decades-old applications in active production.

Sources: Synergy DBL - Wikipedia, Synergex Language page, Synergex DIBOL page, Announcing Synergy/DE 12.3 LTS Release.