Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax!uci-icsa.arpa!grich
From: grich@UCI-ICSA.ARPA (John Mangrich)
Newsgroups: fa.info-vax
Subject: Problem with BACKUP in SPAWNed process
Message-ID: <8509071957.AA24820@UCB-VAX.ARPA>
Date: Thu, 5-Sep-85 21:12:25 EDT
Article-I.D.: UCB-VAX.8509071957.AA24820
Posted: Thu Sep  5 21:12:25 1985
Date-Received: Mon, 9-Sep-85 01:10:25 EDT
Sender: daemon@ucbvax.ARPA
Reply-To: info-vax@ucb-vax.berkeley.edu
Organization: The ARPA Internet
Lines: 21


 Every week we run a fullsave command procedure to back up our two disk 
structures onto two tape sets.  This worked fine under 3.7, but under 4.1
we have this strange problem:

  The fullsave procedure does a SPAWN/NOWAIT/INPUT=.../OUTPUT=... and the 
SPAWNed process does a backup of the user files, then dismounts the tape and
does a save of the system files.  Even though it ALLOCATEs the tape drive,
as soon as it starts the user backup a SHOW DEVICE/FULL indicates that the
tape drive is no longer assigned to the spawned job but rather is allocated to
the *parent* process!  Of course when the spawned process goes to backup the
system files it can't use the tape drive.  I can't find any obvious explanation
in the documentation to explain this.  A workaround is to do the save as two
separate events, but I'd like to know what I'm missing that explains what's
going on.  Anyone know?

Thanks,

John "guess who gets VMS since the real manager left?" Mangrich
UC Irvine
grich@uci.arpa