× 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 19-Jan-2012 08:42 , rob@xxxxxxxxx wrote:
In the PMR:
Found also CPS DI# 8P4KYJ which explains that the issue with RC6 will
be fixed in a future change.

A CPS DI is a "Continued Programming Support" *internal* "Discussion Item" amongst the level-2 and level-3 support. Any statement inside such a private discussion is not a public statement of support.

That comment is much like a mechanic having made a note in the margin of a work order, that something else needs to be done with the brakes. There is nothing about that notation which assures the customer that the work was ever done or will ever be done to that vehicle; i.e. just some thought written down somewhere for which no followup is required. The vehicle owner might best follow-up and clarify, if they were interested in resolving any brake issues alluded, but for which no work order exists.

If there is something specific [desired] for what will be done about the msgCPI1475 RC6, for either "Recovery" or effect [e.g. not getting that error for a particular invocation], then only an APAR number is a public statement. The APAR represents the discussion between IBM [lvl3\lvl2] and the customer(s). Thus to ensure "fixed in a future change" as a response [for some issue with CPI1475 reason code 6], then only an APAR number should be accepted to suffice as a source for that answer; i.e. the DI number and any text\commitments within that discussion are meaningless to a customer. If the comment in the PMR is accurate, then they also should be able to provide the APAR number which will be used to provide that change.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.