grich@UCI-ICSA.ARPA (John Mangrich) (09/06/85)
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
OC.GARLAND%CU20B@COLUMBIA.EDU (Richard Garland) (09/06/85)
I noticed a similar problem with BACKUPS in SPAWNed subprocesses using the tapedrive. I never had time to analysize the problem and now run as a main process. I thought I was crazy. Looks like I am not. Rg -------