[Info-vax] how to ignore (some?) errors during backup ?

[Paul Sture]

In article 
<1c4596dd-53c0-48ea-ada9-deed53ee600c at gu8g2000vbb.googlegroups.com>,
 Pierre <pierre.bru at gmail.com> wrote:

> hi,
> 
> I sometime have this error during a backup
> 
> %BACKUP-E-OPENIN, error opening $1$DGA1:[]FILE.EXT;1 as input
> -SYSTEM-W-NOSUCHFILE, no such file
> 
> for what I know, the quoted file is either being moved from a
> directory to another by a detached process or being deleted by the
> same detached process once used, while backup is trying to copy it.
> 
> the problem is that this error seems to stop the backup :(
> is there a way to ignore such errors ?
> 
> the backup command is :
> $ BACKUP $1$DGA1: /IMAGE $1$DGA2:[BACKUP]DGA1.BCK/SAV /IGNORE=(INTER)
> 
> VMS is 8.3
> 

I think this is a side effect of /IMAGE.  BACKUP gets a list of files 
when it starts but they file has gone by the time BACKUP gets around to 
copying it.

If for example your BACKUP command is followed by another BACKUP command 
or commands to remount disks etc, then yes it will stop.

I generally put

$ SET NOON

before BACKUP commands so that the procedure continues in spite of 
errors.  You could also use:

$ ON ERROR THEN CONTINUE

but you need to put this before each command which might produce an 
error.  I prefer the SET NOON method,

I also check the exit status of important commands when I do this. For 
example:

$ BACKUP $1$DGA1: /IMAGE $1$DGA2:[BACKUP]DGA1.BCK/SAV
$ backup_DGA1_status = $STATUS
$ BACKUP $1$DGA3: /IMAGE $1$DGA2:[BACKUP]DGA3.BCK/SAV
$ backup_DGA3_status = $STATUS

and report them at the end of the procedure.

-- 
Paul Sture