Legacy Languages Supported
Our approach to modernization supports a very large set of languages — larger, perhaps, than any other modernization vendor. The reason for this is that we create a specification, or model, of the legacy system, and then we create the new version of the system from it. Since our tools also support new development, the model does not have to be reverse engineered from an old system (although parts of it almost always are). Rather, we can simply build the model data using a combination of tools and then we can create the modernized system from the model. What this means is that for some languages we have very extensive reverse engineering tools, while for others we use a lighter approach that does not require element by element parsing of the legacy code itself. This also means that we can modernize systems for which the source code has been lost completely!
Powerbuilder | Unisys MAPPER | Cold Fusion |
Oracle Forms | MUMPS | Perl |
Oracle PL/SQL | Model 204 | FORTRAN |
Adabas and Natural | DEC Forms | RPG |
Visual Basic | Micro Focus Dialog System | REXX |
ASP (Microsoft) | ADR IDEAL, DatacomDB/DC | TCL |
dBase | SilverStream and Forte | COBOL for AS/400 and iSeries |
Clipper | Java (Older Versions) | Visual Objects |
FoxPro | HTML | Frontpage |
ANSI COBOL | COBOL-68 | COBOL-74 |
DEC COBOL | DG COBOL | HP COBOL II, Image |
Unisys COBOL, DPS, DMS | IBM VS COBOL | IBM CICS COBOL |
Realia COBOL | Wang COBOL | Accu-COBOL |
Micro Focus COBOL | CDC COBOL, FTN | Burroughs COBOL |
Pacbase / COOL:Gen CA-Gen | .NET | Browser-Accessible Languages |