Converting from COBOL?

Question

Our hourly/union payroll is currently programmed (using union rules) in COBOL. Our COBOL Programmer plans to retire in a couple of years, and I plan to hire someone to program in something like C++, C#, .Net, Java, etc.

If we go this route, will a Programmer be able to convert from COBOL to one of the programs above, or will he/she need to start from scratch? How easy would it be to start from scratch?

Thank you!

Answer 1

Frank's way is one way that will work. The other way is to hire a C++, C#, etc., programmer and have him work alongside your COBOL programmer, converting each function, basically writing it from scratch, which is how porting is done, whether it's one person or two people. You can't convert COBOL to a C-ish language line by line (It's like converting German to English - English doesn't work when the verb is at the end of the sentence), and you can't really do it automatically.



You should "go this route", if only so you have a programmer who can maintain the code in an efficient manner. Any good programmer could maintain a COBOL program, but very slowly (having to refer to the book for almost every move).



To start from scratch, using union rules, would depend on the union rules. Payroll is fairly simple - integrating it with a huge book of rules could make it very complex. If the current program works, I'd convert it.



(BTW, .Net is a technology, not a language - C# is a .Net language, and I wouldn't use Java for payroll. Or even C++ You don't really need an object oriented [the ++ in C++] language for payroll, even with union rules.)

Answer 2

You don't have to convert the whole thing in one go - as modifications become necessary, remove the blocks of code from the existing Cobol program and make them called subroutines in whatever language you decide upon. Alternatively, upgrade the existing programs to a newer version of Cobol that incorporates object-oriented concepts while your Cobol programmer is around. Once you have OOD versions of the programs, just about any programmer worth their salt should be able to maintain them - Cobol syntax isn't all that difficult to learn.

Answer 3

Yes, it is entirely possible to migrate from COBOL to a modern object-oriented language like Java or C++. There is probably no need to start from scratch. Using an automated or semi-automated process to modernize your software can allow you to retain your investment in your mission critical legacy systems, although it can also be quite a challenge that will require the mitigation of some risk.



I have been migrating and re-engineering COBOL applications to more modern platforms for the past 15 years.

Answer 4

I agree with the assessment that you should have someone work side by side to convert.

I find C#.NET or Java are so much more productive that a mock up might be created in the time it takes to just make a simple COBOL change.



You might be surprised at how fast someone could rewrite the entire program. Keep in mind that line by line conversion could be written and later re-factored.

Answer 5

Absolutely, just make sure the new programmer is familiar with both Cobol and whatever the new programming language your system will be using. I used to do this stuff for years and now I'm strictly into real estate and I love It.

Answer 6

Converting from COBOL? Many businesses have lost their "shirt" doing that, only to experience the most disappointing results at the highest cost.



Many have converted from COBOL to Pascal (RIP), Delphi (RIP), PowerBuilder (RIP),Visual basic (RIP) only to discover that VB even with the ++ added to it, could not match the performance and power of COBOL. Then they rewrote the application using C with ++ or other silly character (#) attached to it. There is nothing Sharp, Business-Smart or Cost-Effectiveness about this. The ++ has always meant only one thing: More Money (mm for short).



Experience is a wonderful thing. It allows us to recognize a mistake when we make it AGAIN! (unknown author).



Some would be “conversion counselor” here even proposed to hire TWO programmers to do the job: one to "Read" COBOL, the other to "Write" Cwhatever! Talk about double-budget in the current harsh economic times!



Other “15-years COBOL applications migrating and re-engineering expert” advise here to “migrate from COBOL to a "modern" object-oriented language like Java or C++”, completely uninformed of the fact that OO-COBOL - based on the authentic Object-Oriented methodology found in SMALLTALK that even C++ did not realize completely - has been implemented on Mainframes since 1994, followed shortly by UNIX and even Windows and the INTERNET platforms in COBOL-97.



Refer to http://www.ils-international.com/documents/COBOL%20on%20the%20Internet.pdf

and http://www.ils-international.com/documents/COBOL%20Rejuvenation.pdf .



The COBOL-2002 standard which support full scale Object oriented methodology ALSO supports Unicode, generation and parsing XML, and calling conventions to and from non-COBOL languages such as Cwhatever and other modern programming languages, and provide support for execution within framework environments such as the latest craze: Microsoft's .NET and Java. That was implemented SIX years ago!



Next stop? Look forward to COBOL-2008! The Mother of ALL COBOL standards.



Discover, Learn, Experience, Save more at http://www.COBOLonWeb.com where you can see COBOL in action on the Internet like you have never seen it before!



Comment or inquiries please email to [e-mail].

Answer 7

By converting you would be compiling the source, the .cpp file. Thus find a command in the menus that says compile. BTW, if you would like to use a small C++ compiler try Dev C++; Its fairly small(smaller than Visual C++) and is a very good compiler if you're a begginer to C++. :)

Answer 8

If it ain't broke don't fix it.



Leave it alone and start another system if you want.