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.BERKELEY.EDU Path: utzoo!decvax!bellcore!ulysses!cbosgd!ucbvax!YALE.ARPA!LEICHTER-JERRY From: LEICHTER-JERRY@YALE.ARPA Newsgroups: mod.computers.vax Subject: Re: Bugs with Vaxstation II and Vaxcluster Message-ID: <8605131017.AA19896@ucbvax.Berkeley.EDU> Date: Tue, 13-May-86 06:18:29 EDT Article-I.D.: ucbvax.8605131017.AA19896 Posted: Tue May 13 06:18:29 1986 Date-Received: Wed, 14-May-86 00:39:26 EDT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Organization: The ARPA Internet Lines: 20 Approved: info-vax@sri-kl.arpa I have a Vaxstation II runing VMS4.2 and a cluster running VMS4.3. I have several bugs related to this. If anyone has any ideas about them, I would really like to know. [Two problems that start off with:] [S]et host to cluster, set default to Vaxstation, ... SET DEFAULT does not support node names - see the DCL book. As it happens, it MAINLY works - but you can see why it's not supported; it doesn't QUITE work right. [Two problems that involve running a program on the cluster from a Vaxstation] There were bugs in running files across the network; at least one was fixed in V4.3, as I recall. The problems occured at the node the program ran on; try updating your Vaxstation to V4.3 and see if the problem goes away. Jeff Deifik jdeifik@isi.ARPA -- Jerry -------