From:	CSBVAX::MRGATE!RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP 19-SEP-1988 19:49
To:	ARISIA::EVERHART
Subj:	Re: LAVC question


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 19 SEP 88 16:12:59 PDT
Received: from CitHex.Caltech.Edu by KL.SRI.COM with TCP; Mon, 19 Sep 88 16:04:20 PDT
Date:     Mon, 19 Sep 88 16:04:03 PDT
From:     carl@CitHex.Caltech.Edu (Carl J Lydick)
Message-Id: <880919153658.939@CitHex.Caltech.Edu>
Subject:  Re: LAVC question
In-Reply-To: Your message <545@dms.UUCP> dated 16-Sep-1988
To:       amdcad!weitek!dms!shepperd@ucbvax.Berkeley.EDU,
         MARK%UMNMOR.BITNET@CitHex.Caltech.Edu, info-vax@CitHex.Caltech.Edu

 > On shutdown, how can I get the disks on the system being shut  down  to  be
 > dismounted  from the other system without physically logging into the other
 > system(s) and dismounting the disks from the system going down?

You can do this by using a DECnet task.  A simple task to do this that allows
the calling process to specify which disk to dismount and to wait until the
dismount's been done is:

	$	OPEN/READ/WRITE FILE SYS$NET:
	$ LOOP:	READ/END=DONE FILE REC
	$	MSG = F$FAO("DISMOUNTED !AS", REC)
	$	ON WARNING THEN -
	$	MSG = F$FAO("COULDN'T DISMOUNT !AS; STATUS = !AS", REC, $STATUS)
	$	DISMOUNT/ABORT/CLUSTER 'REC'
	$	WRITE FILE MSG
	$	GOTO LOOP
	$ DONE:	STOP/ID=0

Create a file like the above in the login directory of a privileged account
on the remote node that's proxied to the account from which you'll do the
shutdown.  Then invoke it as follows, where:
	remote_node	is the node where the DISMOUNT/CLUSTER is to be done;
	remote_file	is the name you gave the above procedure
	remote_disk	is the name, on remote_node, of the disk to dismount

	$	OPEN/READ/WRITE FILE remote_node::"0=remote_file"
	$	WRITE FILE "remote_disk"
	$	READ FILE STATUS
	$	CLOSE FILE