[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 22-JAN-1991 21:35:05.20  To:	MRGATE::"ARISIA::EVERHART" CC:	) Subj:	Re: Multiple [sysexe] areas?DIR/NEW   * Received:  by crdgw1.ge.com (5.57/GE 1.80)) 	 id AA00786; Tue, 22 Jan 91 21:25:53 EST Y Received: From UCBVAX.BERKELEY.EDU by CRVAX.SRI.COM with TCP; Tue, 22 JAN 91 17:35:58 PST , Received: by ucbvax.Berkeley.EDU (5.63/1.42)* 	id AA17248; Tue, 22 Jan 91 17:22:38 -08009 Received: from USENET by ucbvax.Berkeley.EDU with netnews . 	for info-vax@kl.sri.com (info-vax@kl.sri.com); 	(contact usenet@ucbvax.Berkeley.EDU if you have questions)  Date: 22 Jan 91 13:18:02 GMTZ From: sdd.hp.com!news.cs.indiana.edu!bsu-cs!bsu-ucs!00prneubauer@ucsd.edu  (Paul Neubauer)G Organization: Ball State University, Muncie, In - Univ. Computing Svc's , Subject: Re: Multiple [sysexe] areas?DIR/NEW  Message-Id: <56362@bsu-ucs.uucp>- References: <00943031.246C86C0@SECS.ucsc.edu> # Sender: info-vax-request@kl.sri.com  To: info-vax@kl.sri.com   B In article <00943031.246C86C0@SECS.ucsc.edu>, wipke@SECS.ucsc.edu   (W. Todd Wipke) writes:E > Is it possible to have a satellite vaxstation 3100 boot off its own H > disk (102 meg) and yet obtain some installed application software from+ > the cluster server sys$common:[sysexe]?      Yes, absolutely.   >Perhaps by adding to the < > sys$system logical the other system area in which to look?C > The problem is that the vaxstation disk is too small for all the  F > system software.  By having at least some of the software locally, IF > figure it will increase efficiency and lower load on cluster server.0 > What is the wisdom of the netlanders?  Thanks.  L I agree (for what it's worth) that accessing some software locally SHOULD beN more efficient, though I have not actually run tests (and am not even sure HOWO I would control such tests).  I am not on the right account right now to simply M include examples into this file, so beware that the code I am posting is from O memory, not tested working DCL.  That said, the basic strategy runs as follows:    given L      -	a VAXstation clustered, but booting off its own disk (assume DKA200) F 	(actually, it can alternatively boot off the cluster disks and still D 	use a lot of the more common stuff off its own disk, but that is a  	little trickier);  J      -	a cluster of other VAXen (of whatever sizes), at least one of which- 	boots from a larger disk (call it $1$dua100)    in SYSTARTUP_V5.COM:  H $ define/system/exec local_common dka200:[vms$common.]/trans=(term,conc)K $ define/system/exec clust_common $1$dua100:[vms$common.]/trans=(term,conc) ; $ define/system/exec sys$common   local_common,clust_common   O then, since SYS$SYSTEM is defined as SYS$SYSROOT:[SYSEXE] (unless you have some K other wierd setups, which is all too likely :-() this should get you to the B right place for anything looking for SYS$SYSTEM.  Note that I usedL [VMS$COMMON.], rather than [SYS0.SYSCOMMON.], which _probably_ refers to theM same place.  You may need to make adjustments for your system. I have defined N several local_* and clust_* logicals of this sort to make life simpler, thoughI strictly speaking, you could just do the 3rd line with phycical names and  eliminate the first two.   You should then be able to:   K $ install add/whatever_qualifiers clust_common:[sysexe]fortran !or whatever   O Note also, that it is not strictly necessary to INSTALL the fortran compiler or O most things as long as you have a symbol set up or an entry in your DCL tables. M You really only need to INSTALL them if they need to have privs or some other O attribute (e.g., be shared images).  You can use many images in sys$system with K NO other preparation beyond what I have already listed.  Of course, you can * also get fancier, as the spirit moves you.  
 Good luck.   ========J Paul Neubauer	neubauer@bsu-cs.bsu.edu         00prneubauer@bsu-ucs.bsu.eduI                 neubauer@bsu-cs.UUCP            00prneubauer@bsu-ucs.UUCP K                                                 00PRNEUBAUER@BSUVAX1.BITNET   