Re: COBOL to Java conversion
- From: Alistair <alistair@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 29 Oct 2007 15:03:12 -0700
On 29 Oct, 16:27, b...@xxxxxxxxxxx (Bill Gunshannon) wrote:
In article <1193674751.922948.92...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
HansJ <hji...@xxxxxx> writes:
On 29 Okt., 16:22, "HeyBub" <heybubNOS...@xxxxxxxxx> wrote:
HansJ wrote:
We are in the business of migrating Unisys COBOL mainframe
applications to Unix.
Using the same programming language and keeping the code intact is a
key element, because we think that there are enough issues to deal
with.
Recently we have seen requests to not only move to a different
platform, but also to change the language to be Java.
We don't need to discuss all the issues that come with a language
change, like maintainability, staff competence, etc. as this is a
different topic.
I would be interested in knowing if anyone has seen a successful
project of this type that has a significant size.
A significant size would be more than one million lines of COBOL code.
Thanks HansJ
To paraphrase Samuel Johnson,
"COBOL to Java is like a dog raised up on its hinder legs. It is not
surprising that it does it poorly; what is surprising is that it would want
to do so at all."
HeyBub,
I'm not saying that it is a good idea to even consider this, I'd like
to find out if there is anyone who can name a successfull project like
that.
But, what would a successful project prove? I know someone who successfully
put a Ford V8 engine in a 1979 Triumph Spitfire. It was real impressive.
And basicly impossible to drive safely as it was way overpowered. (Not
to be construed as saying java is more powerful than COBOL, just an
example of a "successful" and yet worthless project.)
I have discussed this with some of the profeessors here as I am a
strong advocate of COBL and they have recently decided to not use
COBOL for any course projects any more. You have already admited
that the concept is bound to cause problems. Now let's look at the
other side of the coin. What would be gained by re-writting all
the COBOL in Java? My guess would be nothing. So, then why do
it? Seems like a very simple Risk Assessment would be enough to
kill this idea.
Tschüß,
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
b...@xxxxxxxxxxxxxxx | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h> - Hide quoted text -
- Show quoted text -
OK. Seeing as I am applying for a job where the organisation is
looking at the option of migrating Cobol (probably to NATURAL but that
is another drum to bang) what experience does this group have of
migrating Cobol to C/C++ or Java (or any other language that might be
relevant)?
.
- Follow-Ups:
- Re: COBOL to Java conversion
- From: Howard Brazee
- Re: COBOL to Java conversion
- References:
- COBOL to Java conversion
- From: HansJ
- Re: COBOL to Java conversion
- From: HeyBub
- Re: COBOL to Java conversion
- From: HansJ
- Re: COBOL to Java conversion
- From: Bill Gunshannon
- COBOL to Java conversion
- Prev by Date: Re: TRUNC(BIN) and COMP-5
- Next by Date: Re: Data validation (NUMERIC checking follow-on)
- Previous by thread: Re: COBOL to Java conversion
- Next by thread: Re: COBOL to Java conversion
- Index(es):
Relevant Pages
|