| Pete Dashwood 2006-04-28, 6:55 pm |
|
"Frank Swarbrick" <Frank.Swarbrick@efirstbank.com> wrote in message
news:4bc8avF10basaU1@individual.net...
> Pete Dashwood<dashwood@enternet.co.nz> 04/27/06 3:53 AM >>>
>
>
> I know you were being a bit facetious, but do you honestly think that
> converting, say, a batch transaction posting program to Java is a
> reasonable
> thing to do?
Could be. Depends on the circumstances. If you have no COBOL Programmers in
house and everything else is in Java, your expertise is in Java, why would
you NOT convert it (as a low priority, background type task...)?
What if your COBOL vendor goes broke or withdraws support for it? You'd
need to convert to SOMETHING. (This would be a raised priority as soon as
the existing program crashed or required maintenance.)
So, yes, without being facetious (and I was being :-)) I can see some
scenarios where it would make sense to convert even batch processing to
Java.
> And if not Java and not COBOL, then what?
Again, depends on the circumstances. A package? A 4GL? VB? C#? who knows...
Pete.
|