×
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.
On 03-Feb-2012 11:18 , Kurt Anderson wrote:
Was recently semi-frustrated by the lack of dates on this apar for
the qteRetrieveDebugAttribute api. Says the bug was reported in v5r4
but is scheduled for fix in 7.2 (how many years apart are those
releases?) Maybe it the bug was found recently on a v5r4 system. I
don't know - can't tell from the link.
http://www-912.ibm.com/n_dir/nas4apar.NSF/b6c9b771e38b5ea2862564c00079d110/1a676fc8e6c2ba2486257871003c76b3?OpenDocument
I have also been very frustrated by the lack of tracking dates [open
and "close" most notably] on the APAR and PTF documents that are
published. However the above APAR SE47693 found via the "support
portal" search gives "Modified date: 2011-04-13" as part of the
information. The 7.2 as proposed fixed-in release is consistent for a
"fixed in a future release [UR1]" closure; i.e. primary aim being the
next release after the currently GA or a very nearly GA release. See
this alternative link to that same APAR, showing that modification date:
http://www.ibm.com/support/docview.wss?uid=nas21a676fc8e6c2ba2486257871003c76b3
Even so, that date is not very meaningful because the modification
may not necessarily reflect the "close" date, i.e. when the status
changed to "Status.... CLOSED UR1", and may instead reflect any
potential update to the APAR [text, release(s), etc.] since closure.
Regards, Chuck
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.