There was a discussion about the ANS1802E error and the
successful completion code on this list about three weeks ago.
A search of the archives should turn up the response from Andy
Raibeck which explained why ADSM would consider an incremental
backup successful even when a file (or more) fails.

 -- Tom

On Tue, 23 Mar 1999, Peter Griffin wrote:

>Because the backups of our clients are dependant on other tasks and
>resources we do all our scheduling via an external scheduler (ECS).
>
>I run a simple script to backup the client which basically issues the DSMC
>I command and exits with the rc
>
>My concern is that there is an error in the backup (ANS1802E Incremental
>backup of '/opt/adsm' finished with 1 failure ) and yet the script ends
>rc=0.
>
>Is my script too simple? Does anyone do anything similar and has some
>method to track these errors?
>
>
>/usr/adsm/dsmc i
>
>STATUS=$?
>echo $STATUS
>exit $STATUS
>
>Peter Griffin
>Zurich Insurance
>