Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!LBL.ARPA!nagy%43198.hepnet
From: nagy%43198.hepnet@LBL.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: RE: Software installation
Message-ID: <8704110639.AA04301@ucbvax.Berkeley.EDU>
Date: Fri, 10-Apr-87 16:21:10 EST
Article-I.D.: ucbvax.8704110639.AA04301
Posted: Fri Apr 10 16:21:10 1987
Date-Received: Sun, 12-Apr-87 01:08:48 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 22
Approved: info-vax@sri-kl.arpa

Being a relatively fearless system manager, I've installed "minor"
items like new compiler versions on live systems on a VAXCluster and
then just logged into the "other" system and used INSTALL to REPLACE
the shared images.

Datatrieve and others were done on semi-live systems due to the lenght
of time required for the install and other factors (more complex products).

Factors in installing on live systems are:

	- updating the shared images on the other nodes (can be easily
	  done with INSTALL REPLACE).

	- a user might interfere with the install by using the HELPLIB
	  at the time the installation attempts to put a new module into
	  the library.

	- new DCLTABLES can be installed on other nodes by the same
	  INSTALL trick as above.  But users must logout and back in
	  to use the new tables.

	- others I've probably forgotten.