From:	STAR::EICHE        "Private Instigator"  8-MAY-1995 17:58  8-MAY-1995 17:58:00.00
To:	EVERHART
CC:	EICHE
Subj:	cookbook for installing a kit from the infoserver...

From:	EVMS::WALL "Show me, don't tell me  23-Mar-1994 1204" 23-MAR-1994 12:17:39.30
To:	@DISTLIST:EVMS_ENGINEERING
CC:	
Subj:	Installation cheat sheet revised -- includes note on shadow set members

Due to demand at debug, I am retransmitting the basic instructions for getting
announced baselevels off the InfoServer.

DFW

In the following text, Xnnn refers to an announced baselevel number, e.g.,
X5RL

Here's how to install from the InfoServer:

	The software will be supplied in two forms.  One is a kit installable
	by booting your system off the InfoServer.  Optimum for systems with
	only one disk.  This will be announced as Xnnn_KIT.  The other is an
	image saveset of the media containing Xnnn_KIT.  This is best for
	people who need to work with a machine that won't boot or
	install/upgrade from the Infoserver.  This will be announced as
	Xnnn_IMAGE. 

To boot and install from the InfoServer:

	1) Boot your system with the following command:

	b -flags 0,0 exxx -file apb_Xnnn  (where exxx is your ethernet device)

	This should clank and grind, and eventually present the Network ISL
	banner. This will ask two questions.  The answers are 3 and then 2.
	If your system cannot find this file, you have one of two problems:

		1) You're using the Cobra console and not typing in upper case.
		Hit the caps lock key and try again.

		2) There is no MOP-enabled service on your ethernet segment
		that has the file in hand.  JSB off to Getting APB_Xnnn

	2) Connect to the service supplying the software of interest.  For
	example, if you wanted baselevel XABC, you connect to service XABC_KIT.

	In due course, this should get you into the Standalone User Interface,
	which presents you with the options of installing/upgrading, doing DCL
	things, or shutting down the system.  You want to install/upgrade. 
	From there it should be obvious.

	When the installation finishes, you shut down your system and reboot it
	off your new system disk.  It should boot into AUTOGEN, or run
	cluster_config, depending on the answers you supplied.

	Proceed to Getting Licenses, below.

To get the kit off the InfoServer and install locally:

	1) Boot your system.  You are going to need to be able to mount a DAD
	device, which means you're going to need to have valid values for the
	SYSGEN parameters SCSNODE and SCSSYTEMID.

	2) Execute the following from the SYSTEM account:

		@sys$startup:ess$startup client  (Note the presence of an
						argument, and it's important) 

	3) Get yourself a dad device with the software you want.  To DCL, type:

		mcr ess$ladcp bind/nowrite Xnnn_IMAGE

	3) This will result in a dad device being set up.  You may mount this
	device by the dadnn number supplied or by the logical name
	DAD$Xnnn_IMAGE.  These can be mounted /ov=id or system-wide, but they
	cannot be mounted cluster-wide. 

	4) Mount the device you want to put the kit on as foreign:

		mount/for <device> 

	5) Back down the image of the kit from the InfoServer as follows:

		backup/image <daddevice>:Xnnn.bck/save <device>

	Remember, this is an image mode backup.  You'll lose anything on
	<device>. 

	6) When the backup finishes, boot your system off <device>  It will put
	you into the Standalone interface. Install/upgrade, as you wish, then
	boot your system off the new disk.

	Note also that you can perform most of these steps from a VAX system 
	too, say if you have removable media. Just make sure you use 
	ALPHA_BACKUP, by defining BACKUP:

		define backup evms$images:alpha_backup

	Proceed to Getting Licenses.

A note on Shadowed System Disks:

        The installation procedure is specifically *NOT* mounting the
        targets of of installs/upgrades /over=shadow.  Hence, if you try to
        upgrade a system disk that is a former member of a shadow set you
        may find your target is write-locked.  This is considered a
        feature. Keep it in mind when upgrading shadowed system disks.

Getting Licenses:

A new service has been created on the InfoServer, called EPSILON_LDB.  
The InfoServer can be reached without functioning DECnet.

	1) Once your system has got the software of your choice installed, boot
	it up and make sure you have an SCSNODE and SCSSYSTEMID set.

	2) Log in and run NETCONFIG to configure the network.  You won't be
	able to start it yet.  You can either answer N to NETCONFIG's last
	question or just hit carriage return and watch STARTNET croak -- it's
	up to you. 

	3) Start up LASTDRIVER with @sys$startup:ess$startup client  (don't
	forget that argument, it's important).

	4) Issue a bind/nowrite to service EPSILON_LDB.

	5) Mount the resulting DAD device.

	6) In DAD$EPSILON_LDB:[000000] one will find lmf$license.ldb, the same
	one we've been using for months and months.  Copy it into
	sys$sysdevice:[vms$common.sysexe], load them up, and you're off
	and running.

Getting APB_Xnnn:

The hard part of this is determining what segment you're on and what other
system might have MOP service enabled.  Unfortunately, I don't have any help at
this time.  However, once you have such a system, the rest is easy:

$ copy/contig evms"username password"::xnnn_resd$:[sysexe]apb.exe -
	mom$system:apb_xnnn.sys

Don't forget that contiguous qualifier!