Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!paul.rutgers.edu!sabbath.rutgers.edu!shs From: shs@sabbath.rutgers.edu (S. H. Schwartz) Newsgroups: comp.os.vms Subject: Re: Premature termination of a COM file Message-ID: Date: 12 Apr 88 16:43:15 GMT References: <1179@csun.UUCP> Reply-To: shs@sabbath.rutgers.edu (S. H. Schwartz) Organization: Dept. of Computer Science, Rutgers Univ., New Brunswick NJ Lines: 27 Keywords: Early termination of a COM file In article <1179@csun.UUCP> mst@csun.UUCP writes: Situation: This is the first major(?) script that I have written (we started using VMS this semester). I have a script that does the following BACKUP command: $ BACKUP/REWIND/IMAGE/BUFFER_COUNT=5/VERIFY MA$DUA0: - MA$MUB0:'DATE.BCK/SAVE_SET Problem: My problem is that after either backup is done, the tape does not rewind itself and the statements in the COM file following the backup command are never executed. ------------------------------------- I've noticed the same behavior. If it was worth it to me to debug, I would execute: $ ON ERROR ... $ ON WARNING ... $ ... immediately before the $ BACKUP, then look to see if BACKUP was setting $STATUS to some error-indicating value, without printing a corresponding message. -- ---***--- "Hit me with your best pshat!" --- Lenny Solomon S. H. Schwartz (201) 846-9185 shs@paul.rutgers.edu (201) 932-4714 ...rutgers!paul.rutgers.edu!shs