Re: Partially damaged DEVD

Working from memory is very bad. Message produced following a GO SAVE.
Test 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?

John McKee

On Tue, Aug 7, 2012 at 1:12 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 07 Aug 2012 10:54, CRPence wrote:

On 07 Aug 2012 10:31, John McKee wrote:

<<SNIP>>

Question: Do the partially damaged objects need to be deleted? I am
wondering if the OS fixes them if it can.

IIRC the "partial damage" condition for a *DEVD may be resolved by
merely a vary-off and vary-on [cycle]; i.e. that the "logical damage"
for which the device is in error is manifest using a "partial
damage" message [81## or 82## range], and any reset is left to user
action. I do recall specifically, that is how a tape device is both
treated and recovered [for some errors; e.g. LIC terminated SAVxxx].
But that type of device [tape] is more conspicuously like a file and
data [e.g. save file being somewhat analogous to a tape device] than
how perhaps a display\workstation device might be perceived; I am
much more familiar in how "damage" conditions are set and diagnosed
for the database... <<SNIP>>

Presumably the following error is available in the log:
DSPLOG MSGID(CPF8105)

FWiW, appearing consistent with my recollection for "device" errors:

DSPMSG CPF8105
"...
Recovery . . . : If full damage occurred, delete the device
description (DLTDEVD command), and do one of the following:
<<SNIPped; per "partially">>
If partial damage occurred, vary off the device and vary the
device on (VRYCFG command) again. ..."

Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.