Considering HansJ situation..... and with such a magnitude of
requirements. Woh! System language conversion is not my best solution.
Go to the Cobol vendor who provided the solutions and re-engineer.
If business logic is needed to be changed... then start with a "new"
language platform "you think" is best and IT people have "several"
solutions for it.
Best practice: Go to a Cobol provider.... or Java-based vendor for re-
engineering. Definitely you have a budget for it. Get several vendor
solutions for re-engineering and concentrate even more with budgets.
A link above would somehow help... but then again, somehow?!? Most
successful developers knew Cobol, that is why we are here in this
Cobol Google group anyway.
Re: What Smalltalk product/implementation would you use, and why? ... problem - the model you want does not lead to a supportable business.... What it leads to is a vendor that goes under. ... My reason, I am sick and tired of being hosed on COBOL's prohibitive costs - and I'm talking a fully integrated IDE allowing for traditional COBOL, SQL Preprocessors and OO COBOL with general/collection and GUI classes - a superb tool - if you don't mind getting screwed by the compiler vendor on fees. ... I'm searching the Web looking at the multiplicity of options, Smalltalk in its various flavours, Java, C# and of course Visual Studio. ... (comp.lang.smalltalk)
Re: Program templates as Object Classes ... some aspects of OO COBOL have grown and evolved since then. ... Classes from ANY vendor on ANY platform can be "wrapped" (provided the ... 2002 standard implemented. ... I really don't care what J4 or WG4 or SG-1 ... (comp.lang.cobol)
Re: Standard and COBOL file formats ... Nor is it a creature of Cobol,... The 'format' is actually defined, not by the operating system, but by ... the vendor uses headers or other devices to mark records, ... If you mean ORGANIZATION RELATIVE ACCESS RANDOM then you are ... (comp.lang.cobol)
Re: Program templates as Object Classes ... There are users of OO COBOL; they are just far fewer than either the vendors ... whether from the same vendor or not. ... disagreed with you that XML should be supported *first* by the OO features... > being spent by J4 to provide these facilities through a standard that will ... (comp.lang.cobol)
Re: Called Module with File Access - where to Close ... I certainly know of vendors who handle ENTRY statements differently.... > COBOL programming, I've yet to run into anyone who gives a fig. ... Does anyone know of a vendor who does NOT ... > managers COULD exist, but I suspect no one pays them much mind anyway. ... (comp.lang.cobol)
