|
IMHO, this is the problem. IBM shouldn't be breaking backward compatibility in new releases of OS/400 for any products. That's what we should be pushing IBM about, rather than pushing for a release-neutral RPG compiler. > There WAS one twist to the V5R2 upgrade, Scott. V5R2 specifically broke > WAS35SE. That is, if you had an application that worked wonderfully on > WAS35SE and you upgraded to V5R2, your application stopped working > (well, more precisely, WebSphere stopped working). > > The only way around this is to upgrade to WebSphere Express. That's why > I've been giving sessions on migration to WebSphere Express at trade > shows and the like. It's a bit of a pain, actually.
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.