Re: COBOL to Java conversion
- From: HansJ <hjigel@xxxxxx>
- Date: Tue, 30 Oct 2007 02:06:11 -0700
On 30 Okt., 01:51, LX-i <lxi0...@xxxxxxxxxxxx> wrote:
HansJ wrote:
We are in the business of migrating Unisys COBOL mainframe
applications to Unix.
A-series or ClearPath?
In this business area, all we do is 2200 (Clearpath can be both...)
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 know this goes against what you just said, but from my experience, I
would caution against *any* language "roll" from one to another. When a
system is coded, the low-level design usually draws upon the strengths
and efficiencies of the language in which it is written. These do not
transfer well from one language to another. Forget about the issues you
mentioned - it's simply bad code.
There is nothing wrong (and really not much of an alternative) for
small amounts of code to change the language, for example rewrite
assembler system routines in C language. It is a completely different
story when we are talking about large amounts of the code.
Add to that some of the "bad" COBOL structures one encounters,
especially on code that's old enough to vote, and it's simply a recipe
for disaster.
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.
I have seen a failed project of this type. :) But that's not what you
asked, is it?
Personally, I would tell them something along the lines of this...
"Moving to Java would take significant re-engineering of the existing
system. (The data structures may also need to be converted to a
relational database.) From our research and experience, trying to
convert the system at the code level would be a high-risk endeavor,
while re-engineering would not only increase your chances of being happy
with our results, but may result in a more efficient system that will
cost less to operate in the long run."
Agreed..
Of course, I'm not a marketing guy... I just know that, with my 9 years
coding my previous system, and my 7 months being up to my eyeballs in
Java, I have a pretty good idea of how I'd go about converting my last
system to a Java web application. :) Not to say I could do it quickly,
but I can see how the objects and services would break down.
I can assure you that, first off, hundreds-of-lines-long "edit"
paragraphs would be a thing of the past. Reusable single-responsibility
methods are great. But, you're not going to eliminate that stuff with a
code roll.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ / \/ _ o ~ Live from Albuquerque, NM! ~
~ _ /\ | ~ ~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~ Business E-mail ~ daniel @ "Business Website" below ~
~ Business Website ~http://www.djs-consulting.com ~
~ Tech Blog ~http://www.djs-consulting.com/linux/blog ~
~ Personal E-mail ~ "Personal Blog" as e-mail address ~
~ Personal Blog ~http://daniel.summershome.org ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GEEKCODE 3.12 GCS/IT d s-:+ a C++ L++ E--- W++ N++ o? K- w$ !O M--
V PS+ PE++ Y? !PGP t+ 5? X+ R* tv b+ DI++ D+ G- e h---- r+++ z++++
"Who is more irrational? A man who believes in a God he doesn't see,
or a man who's offended by a God he doesn't believe in?" - Brad Stine
.
- References:
- COBOL to Java conversion
- From: HansJ
- Re: COBOL to Java conversion
- From: LX-i
- COBOL to Java conversion
- Prev by Date: Re: COBOL to Java conversion
- Next by Date: Re: Cornstarch?
- Previous by thread: Re: COBOL to Java conversion
- Next by thread: Re: COBOL to Java conversion
- Index(es):
Relevant Pages
|