Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!GRIN1.BITNET!MCGUIRE From: MCGUIRE@GRIN1.BITNET ("The Sysco Kid ", McGuire,Ed) Newsgroups: comp.os.vms Subject: VMS BACKUP hiccups Message-ID: <8806210322.AA22545@ucbvax.Berkeley.EDU> Date: 14 Jun 88 14:43:24 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 15 > Date: Wednesday, June 1 at 12:47 pm pdt > From: Kraig Eno, UW BioStructure> Subj: VMS BACKUP hiccups > > 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. No errors at all? You're using /IGNORE=INTERLOCK for a reason; I imagine you get `file is open by another user' messages: as far as DCL is concerned, those are errors; depending upon the severity code set by BACKUP, they could be signalling DCL to terminate your procedure. If my guess is correct, then a SET NOON statement at the top of your code will cause DCL to bypass all error checking. Hope this helps! Ed