Re: Partially damaged DEVD -- MIDRANGE-L

Subject: Re: Partially damaged DEVD
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Tue, 07 Aug 2012 15:46:47 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 07 Aug 2012 14:46, John McKee wrote:

Working from memory is very bad. Message produced following a GO
SAVE. Text was "DEVD previously damaged". I don't believe the
correct action is to delete the DEVD and move on - as the SA does -
since a trouble ticket gets produced and it has to be recreated.
Would vary off/vary on still be the appropriate fix?

Full and Partial "damage" conditions are diagnosed either as a prior effect [previously-damaged] or as a current incident [damage-set]. The VLog and the message [identifier with full text and details] for [and the actions and messaging leading up to] the original damage-set condition are best, to answer that question. The CPF8100 or CPF8200 message range searched in the history should identify the job and some details, if the original incident is still logged there.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

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