RE: Damaged objects after hard fall

By submitting the job, the savefile goes away at the end of the job.


Steven Morrison
Fidelity Express
903-885-1283 ext. 479



"Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/12/2007 02:05 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Damaged objects after hard fall






And clear the save file before each SAVOBJ? I like your idea.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx
[mailto:midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx] On Behalf
Of
smorrison@xxxxxxxxxxxxxxxxxxx
Sent: Friday, October 12, 2007 2:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: Damaged objects after hard fall

One way to check for damaged objects is to save objects to a save file in
qtemp, and monitor for errors. Pseudo code would be:

DSPOBJD *all/*all (or selected types) to an outfile
Read the outfile
For each record in the outfile that you want to check:
submit a job to:
Create savefile in Qtemp
SAVOBJ to the save file
Monitor for error and send message/write to log file if save fails
Loop until end of file



Steven Morrison
Fidelity Express




rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/12/2007 12:11 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Damaged objects after hard fall






That should work. Don't wait so long that some obscure object you only
use on rare occasions has been rotated off of your backup tapes.

Rob Berendt