youngdale%v6550c.DECnet@NRL3.ARPA ("V6550C::YOUNGDALE") (06/10/88)
>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. I think that the problem is that during the first backup there is an error of some sort (i.e. file open for write by another user). In order to get this to run, you must turn off error checking. ------------------------------------------------------------------ Eric Youngdale YOUNGDALE%V6550C.DECNET@NRL.ARPA Code 6551 Naval Research Lab "Some user assembly required" Washington, DC 20375 (202) 767-3276 ------------------------------------------------------------------