Migrating legacy COBOL to the .NET framework


Arctic tern

Pete Dashwood, our CEO, is on record in a statement outlining PRIMA's approach to modernizing COBOL, posted in the Usenet COBOL group (comp.lang.cobol),on 24th October, 2009 (there are some new links added to this, 2013):

Click here to see what he said...

PRIMA has a unique, data driven, solution to the problem of modernizing existing COBOL. For a quick summary of that solution please click here

COBOL has served us well for half a century but it has been overtaken by events.
COBOL compilers, support, and tools are expensive and cannot compete with other languages which are not only more powerful, but are more available, based on modern concepts that fit the modern networked environment, and, best of all, are FREE!...


linefloImp1

Nevertheless, it would be foolish (and in some cases, not even possible...) to write off COBOL code that is functioning perfectly well. PRIMA are committed to salvaging COBOL wherever it makes sense to do so, and we have developed the Migration Toolset over years, leveraging our own and our customers' experience in moving COBOL onto the .Net platform. The goal is to bring this code into the modern arena where it can interact with other languages that use the object paradigm.


To see what is involved in using our approach and WHY we do things the way we do, please click here then tap/click the tile marked "Salvaging COBOL".


The PRIMA Migration solution means COBOL can play on even terms on the same playing field (.Net) as modern, Object Oriented languages; it means your new developments and enhancements can be in any language (including COBOL...), it means your old procedural code will NOT degrade your new Object Oriented .Net environment and it means you are under no pressure to replace your legacy!
...next page

Settings