×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Neil Palmer wrote:
I was told it affected only V5R3M0.
I figured the affected releases [listing all of them] was a side
effect of the long-standing problems with the internal tools which
shadow information to the web. :-( With a new APAR the developer
/answers/ the APAR internally with a /fixed in release/ value. That
value either gets ignored by the tools _or_ the defaulted value does
not [yet] reflect the correct release where the problem no longer
exists in a base release [i.e. in which release where no PTF is
required to prevent the problem].
I must be thinking back many years when I could
swear a close of PER was PERmanent Restriction
(& they didn't intend to fix it).
Never was, though. Not a surprise however, since I recall many
within IBM who had done the same thing; repeatedly. Not sure why,
because PER and PRS were long established in the RETAIN problem
tracking from the mainframe APAR process. Perhaps those first three
letters PER matching the prefix of the word PERmanent, just has a
too powerful override to recollection of the mnemonic PRS. :-)
Regards, Chuck
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
