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!decwrl!amdcad!lll-crg!ucdavis!ucbvax!info-vax
From: McGuire_Ed@GRINNELL.MAILNET
Newsgroups: mod.computers.vax
Subject: Merging VAXen
Message-ID: <8601291334.AA19774@ucbvax.berkeley.edu>
Date: Mon, 27-Jan-86 14:40:00 EST
Article-I.D.: ucbvax.8601291334.AA19774
Posted: Mon Jan 27 14:40:00 1986
Date-Received: Thu, 30-Jan-86 02:16:08 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

Follow the procedure in the Guide to VAXclusters, appendix A.  If I remember
right, the same procedure can be used on your VMSMAIL.DAT file.  You will also
need to initialize your queue file (JBCSYSQUE.DAT).  You may want a common
SYSTARTUP.COM and SYLOGIN.COM since the systems are going to be largely the
same.  Differences between systems (such as different hardware) can be coded
in the same file if you look up the system's node name.  My procedures contain
code like this:

        $ AVAX = "!"
        $ BVAX = "!"
        $ CVAX = "!"
        $ 'F$GETSYI("NODENAME")' = ""
            .
            .
            .
        $ 'AVAX' SET PRINTER ...   ! SET PRINTER ONLY IF STARTING NODE AVAX

Merging your SYSUAF and VMSMAIL files is tricky if you have users on both nodes
nodes with the same name.  Only the first record encountered during the merge
is entered in the common file; therefore (for SYSUAF) only one profile is saved
and (for VMSMAIL) the new mail count can be wrong and only one set of users'
personality settings are saved.

Disclaimer:  The above information was written from user memory without ECC.
I guarantee that I have made mistakes and forgotten things.  Call CSC and
review the merge with the cluster support group before you start.  (You ARE on
maintenance, right?)  This is something they're good at.