|
rob@xxxxxxxxx wrote:
If this wasn't fubar'ed http://www-912.ibm.com/s_dir/sline003.nsf/2d3aff1c6b4d6ce086256453000d971e/c1dffebbd2cb7ff2862569c9000eff3d?OpenDocumentthen we could look up MF21772 and find the V5R1 version.Sometimes IBM doesn't find a problem until a system has been out there a good long time, or sometimes even until it's on a new release. Then IBM may ptf it back to previous releases. That's where a bulk of the entries occur on a VxRxMx to VyRyMy cross reference comes in useful. Sometimes, though, there will be no ptf in the newer code because it's included in the base o/s; or new version G/A code.Rob Berendt
RobApart from the faulty document above, is there any other way of finding out? If it was fixed in the base O/S, would the memo to users for V5R1 cover this? If so, where might I find the one for V5R1?
But if they didn't fix it, or I cannot find out whether they did so, is my Client's 170 for the scrap heap? They are a very poor charity and cannot even afford a new PC! They certainly could not afford to replace their 170 with a second user machine, never mind a new one. I imagine that the cost of upgrading to V5R2 would be way beyond them and there is no guarantee that it would fix the problem.
Many thanks Best wishes Rob
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.
midrange.com
