Anything other than a simple answer is too complicated so I'll stick
with that for the most part.
The simple answer is money.
The slightly less simple version is that at the time that we convinced
management to produce an ILE version of COBOL there were very severe
budget restrictions on the team. COBOL only bought in about 20% of the
revenue that RPG did, and they had to build a new compiler from
scratch - RPG could use the SAA compiler base which in theory made it
look cheaper. Within that budget they could either live without OPM
compatibility, or not build it. According to development it was very
difficult to do in part because the original OPM COBOL run unit stuff
was a bit ... well "weird" would be the best word. I was one of those
who decided that it was better to live without than wait another
release cycle and perhaps lose the funding and staff completely.
The hope was that once the new compiler was in place we could add the
compatibility features. For many reasons that I was not really party
to, that didn't happen. The requirement to perhaps retrofit it had
not featured as strongly in the design as it should have and it turned
out to be even more difficult (and therefore expensive) to do.
Sigh ... and the money was never forthcoming - in part because not
enough customers cared enough to complain.
On 4-Nov-09, at 2:23 PM, Jeff Buening wrote:
- - - - -This is what I don't understand, why couldn't it of been made
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.