|
Joe Pluta wrote:I understand the pain. But the fact that JDE is OPM is the problem. I don't think it's IBM's fault, either. If you have the source, moving from OPM to ILE isn't that hard. If you don't have the source, your vendor needs to make the move. If you're on an outdated version with no source and no support, that's the situation IBM is really not supporting. They had to make a choice somewhere, and the OPM world is the one getting the wave.
Joe, I totally understand that concept. But what about those of us who
choose to do all of our new development in ILE, but are also stuck
maintaining a vendor-supplied package written in OPM (JDE in our case)?
It's not the individual shop's fault that the vendor refuses to stay
current.
I know you didn't mean anything personal by this, but I'm still ratherYou're going to be penalized if you choose to continue to maintain software that is over 10 years out of date, yes. You find that offensive, I can understand. But it's the reality. The people who pay more are the people who want both worlds.
offended by the idea that IBM is going to charge me once to be able to
maintain my JDE programs, and then charge me twice because I choose to
keep my skills current by developing my custom stuff in ILE.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.