Errors-to: epmdf@YMIR.BITNET
X-Organization: Penn State University / University Libraries
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IPMDF
X-VMS-Cc: JLW
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 27 Jan 93 19:53:30 GMT
From:         "J.Lance Wilkinson, 814-865-1818" <JLW@PSULIAS.BITNET>
Subject:      My most common installation question....
Newsgroups: bit.listserv.pmdf-l

I swear I ask somebody this question every time I install PMDF.  What's the
answer this release (v4.1)?

        I have a completely homogenous cluster, per the definition on page 1-4
        of the v4.1 Installation guide, first paragraph in section 1.3.2.

        Can I simply do *one* VMSINSTAL run, on the primary member of the
        cluster, or must I run VMSINTAL on that primary member (a VAX9420),
        then do the same thing all over again on our VAX6420, our VAXStation
        3100, and all eleven of our VAXStation 4000 VLC's?

        I know I'll still have to stop PMDF and all other network mail
        operations on all cluster members, then reinstall/restart using
        SYS$STARTUP:PMDF_STARTUP.COM on each cluster member, after the
        VMSINTAL and post-installation tasks.  I'm not worried about that;
        I just think it's silly and a significant waste of time to run
        VMSINTAL 14 times with the same results each time -- or *are* they
        really the same results each time (construction of the PMDF_ROOT:[...]
        directory tree)?

        If I sound really dense on this, I'll quote from, again, page 1-4
        of the Installation guide, first paragraph in section 1.3.2:

                "If you have a completely homogenous VAXcluster, ...,
                installing PMDF is essentially the same as on a single
                node.  All individual host names are essentially aliases
                for a single host, and should be rewritten to the local
                host name."

        It *sounds* to me like all I need to do is *one* VMSINTAL, followed
        by taking care to include all my post-installation tasks (running
        CONFIGURE, editing PMDF.CNF, etc.).  But given that JNET needs to
        be VMSINTAL'd on every node, and I clearly remember doing the same
        for PMDF back when we only had the 9420 and 6420 (as well as PMDF
        v3.1), I don't want to make the mistake, while doing this in the middle
        of the night on a weekend when nobody @innosoft is able to answer
        the phones and I have myself screwed....;-{

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services         AT&T:(814) 865-1818 FAX:(814)863-3560  |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU