Quote:
Originally Posted by id10t
We still have a large dependency on 25 year old code and db schemes written by former VSAM developers. Data duplicated everywhere since they couldn't grok a join, the languages (VG/EGL) were originally by IBM as a way to move towards Java, you write in EGL/VG and it generates Java+JSP or COBOL code. We can't get the installer any more, we're running it on Win10 vms made from ripping a physical Win7 install out and upgrading the OS on it. We can't even buy licenses, we tried and IBM said "we have no way of charging you for it, just ignore the license warning, here's a nice letter from our legal folk giving permission"
|
That's AS/400 no? Ours are a bit bigger.
If so you'll get a kick out of this - how many times do we need to read "it's the future":
https://www.itjungle.com/2007/09/17/tfh091707-story01/
The "can generate cobol" might give you a path forward.
Especially if you use that to then generate java.
As an aside - since you mentioned VSAM - we ended up writing our own file access code.
I (vaguely) remember than I did a bunch of work optimizing it back in the early 00s. VSAM was too slow and the file owning requirement was too onerous. EOF pointers in a dataspace FTW.