RE: DAMAGED OBJECT: How do I delete it???

["Bale, Dan" <D.Bale@xxxxxxxxxxxxx>]

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Thanks to all who responded.  It took the system about an hour to delete
the damaged object.  It's gone, and we've recompiled it.

Our backup scenario is such that nothing, NOTHING, should halt the
backup application.  Without fail, the system MUST be available by 5:00
a.m.  In the case where an error occurs it is either specifically
monitored for (and specific actions taken for it) or it is "caught" by a
global MONMSG (CPF0000 MCH0000), a special "global" message is sent, and
the job log is interrogated the following day, after which I can decide
how to handle it

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com

> -----Original Message-----
> From: rob@dekko.com [SMTP:rob@dekko.com]
> Sent: Monday, September 10, 2001 12:34 PM
> To:   midrange-l@midrange.com
> Subject:      Re: DAMAGED OBJECT: How do I delete it???
>
>
> But be prepared to closely monitor your backup because the discovery
> of a
> damaged object will cause your backup to go to an error message.  You
> have
> three options:
> 1)  Run your reclaims first.  This is what we do.  What the heck, the
> objects are already damaged and won't get saved anyway.
> 2)  Closely monitor your backup and be prepared to answer the message.
> Really popular on a system which takes 5 hours to backup, you leave,
> and
> come back later to find out the message occurred 10 minutes after you
> left
> and you lost all that time.
> 3)  Put the generic MONMSG CPF0000 at the top of your program.  Who
> cares
> if your backups are good?  What is important is that they finish.
> SARCASM
> INTENDED.
>
>
> Rob Berendt