Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!BIOSTR.BIOSTR.WASHINGTON.EDU!KRAIG
From: KRAIG@BIOSTR.BIOSTR.WASHINGTON.EDU ("Kraig Eno, UW BioStructure")
Newsgroups: comp.os.vms
Subject: VMS BACKUP hiccups
Message-ID: <8806112307.AA20396@ucbvax.Berkeley.EDU>
Date: 1 Jun 88 19:47:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

Anyone know why BACKUP behaves this way?  I have a command procedure (shown
below) which stops just after the first BACKUP command...no error or anything,
it just doesn't execute the following commands.  If it's run batch, the job
terminates at that point.  This is under 4.7, but it did the same thing under
4.4.  I've tried various things, but it doesn't even seem terribly consistent.

$ set verify
$ set process/name="FULL Backup"
$ allocate MUA0:
$ initialize MUA0: FULL
$ mount/foreign MUA0:
$ backup/image/record/ignore=interlock DUA0: MUA0:SYSTEM.BCK
$ ! This is where it halts.
$ backup/image/record/ignore=interlock DUA1: MUA0:USER1.BCK
$ backup/image/record/ignore=interlock DUA2: MUA0:USER2.BCK
$ dismount MUA0:
$ deallocate MUA0: