Re:Cobaul: A COBOL to WebAssembly Compiler
by marktangotango on Monday September 21, 2020 @04:13PM
(#24547906)
Don't forget to include 'EXEC SQL'. For IBM mainframe Cobol, how many progrmams DON'T depend on the mainframe environment specific features/services? Probably zero or close to it. I think the environment for other vendors (Microfocus, Accucobol) is a bit more forgiving, I don't have experience with them so can't say for sure.
Another, maybe more subtle mainframe pecularity is how it maps dataset (ie file names) names to 'dsnames' (Cobol source code construct) at runtime, tied together by JCL.
Re:Cobaul: A COBOL to WebAssembly Compiler
by tyingq on Monday September 21, 2020 @05:39PM
(#24548782)
There's also lots of Adabase, IDMS, IMS, third party schedulers, and maybe some assembler sprinkled around. And lots of smaller problems like printing, EBCDIC centric code, record based files, etc.
I assume Microfocus provides solutions for some of this.
Re:Cobaul: A COBOL to WebAssembly Compiler
by Spearchucker on Monday September 21, 2020 @04:30PM
(#24548101)
Microfocus did a thing where you could port COBOL TO .NET. I haven't worked with it myself but know Barclays used it to migrate a lot of COBOL in the mid 2000s.
As I understand it, many COBOL programs of current practical interest make extensive use of data management and transaction processing facilities that aren’t part of the COBOL language itself.
Can anyone share their experiences? For example, what fraction of the COBOL modules in a typical application would be able to be translated by a compiler that doesn’t handle statements such as “EXEC CICS” or “EXEC DLI”?