Re: Damaged objects

Neil,

Run PrtErrLog.  This will show you hardware errors on the system. First run it 
with the defaults. This shows you the errors for the last 24 hours. Then widen 
the time period.

Are the damaged objects the same/similar names each time you run the reclaim?

Theoretically you can dspobjd *all/*all to an outfile and examine the damaged 
object fld in the outfile. If you run that every day, maybe that would help 
determine when the damage is occuring.

hth,

Steve Richter

---------- Original Message ----------------------------------
From: "Carley, Neil" <carleyn1@Midas-Kapiti.com>
Reply-To: midrange-l@midrange.com
Date: Thu, 6 Sep 2001 16:48:35 +0100

>Hi group,
>
>Lately our system, a 720 at V4R3 has been reporting a very high amount of
>damaged objects and it seems as though things are starting to get worse. So
>far this year I have had to run 4 reclaim storage and 1 reclaim DLO. I now
>have to do another rclstg this w/e as there is once again considerable
>damage on the system. A rclstg on our system takes about 37 hours. One thing
>I am now thinking about doing is reinstalling the OS as I think perhaps that
>part of it may have become corrupt ?
>I have completed DR restores, built systems from scratch successfully in the
>past but never just reinstalled the OS on a live system and am somewhat
>hesitant about doing it on a mature system without finding out exactly
>what's going to happen as a result. I'm sure someone has done this in the
>past and would be very grateful if you would offer any advice on the
>process, things to look out for, changes that may occur etc.
>Any advice on any of the above will be very welcome.
>
>thanks again
>Neil
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>
>