On Fri 05-May-2011 12:24 , Bryce Martin wrote:
I think that it is ridiculous that IBM creates software that is
stomped by a browser upgrade.... even IE 8... which has been out
since when? March 19, 2009. That is right... OVER 2 YEARS AGO!!!!!

It's sloppy at best, but negligent of its customers and products at
worst. How do you not fix something browser based in over 2 years?
My mind boggles when I see this crap from them... they are better
than this, or at least they should be. Thank goodness I don't need
to use an HMC, or might really be mad :D

As described... Seems to me that the browser would be considered to be the problem since their upgraded code is no longer able to process what apparently was being processed previously without any difficulty before the upgrade.? That is to say, when a browser is upgraded and then directed to the same link which is accessing\performing the same un-upgraded code\actions that existed since before the browser was upgraded, then how would the fault be the unchanged versus the changed feature? Why would IBM be expected to ensure that every browser upgrade was still properly rendering their code\output since a level already verified to be supported? Should IBM ensure every release upgrade to a 5250 emulator should remain compatible with their previous version of that non-IBM 5250 emulator?

While I suggested Rob should get a DCR or APAR to track, that is only because the IBM response suggested they had submitted a "request to development to get this repaired". I figured that response implied both that IBM admitted some culpability and that a resolution to the request could be tracked [since code changes would come only from one of those two features, both of which have tracking identifiers].

Regards, Chuck

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].