Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!mcnc!decvax!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Managing cluster(s) of VAXstations.
Message-ID: <880405035756.502@CitHex.Caltech.Edu>
Date: 5 Apr 88 11:11:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32


 > In short, TO REBOOT A VAXSTATION ONE MUST BE PHYSICALLY PRESENT AT THE
 >  VAXSTATION TO TYPE IN THE SHUTDOWN/BOOT COMMANDS! Imagine trying to manage
 >  VAXstations in a large department! ( Only one locked door is sufficient to
 >  make things impossible. )
 > 
 > Perhaps I've overlooked some essential function in DECnet or perhaps someone
 >  has found a solution to this particular cluster management problem? I haven't
 >  considered the RSM ( Remote System Manager ) as that is expensive, I believe.

Try the following:
	Create a file, SYS$MANAGER:DETSHTDWN.COM containing:
		$ @SYS$SYSTEM:SHUTDOWN 0 1 0 1 0 1 R
	or substitute your own favorite shutdown parameters, but make sure
	that parameter 6 is 1.
	Then execute the DCL command:
		$ RUN/UIC=SYSTEM/INPUT=SYS$MANAGER:DETSHTDWN.COM-
			/OUTPUT=SYS$MANAGER:DETSHTDWN.LOG SYS$SYSTEM:LOGINOUT
This creates a detached process that does the system shutdown, specifying an
automatic reboot.  Since the process is detached, it won't be affected by: 
	1)  Shutting down LAT services;
	2)  Shutting down the DECnet; or
	3)  Shutting down batch queues
so it should do what you want.  The technique works for me when I have to
reboot a 780 that I can reach only by DECnet when I'm working from home. 
Please let me know if this solves your problem, and if not, why not.

								-Carl J Lydick

INTERnet:	CARL@CITHEX.CALTECH.EDU (CARL@[192.12.19.5)
BITNET:		CARL@CITHEX
HEPnet/SPAN:	CITHEX::CARL (42044::CARL)