Google
 

Trailing-Edge - PDP-10 Archives - BB-JF18A-BM - documentation/ms-mx.doc
There are 4 other files named ms-mx.doc in the archive. Click here to see a list.
   INSTALLING DECmail/MS SOFTWARE                             Page 1


                        TOPS-20 DECmail/MS V11

                       INSTALLATION PROCEEDURES

                               07 Jul 86




   COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1986. ALL RIGHTS RESERVED

   THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
   ONLY  IN  ACCORDANCE  WITH  THE  TERMS  OF  SUCH LICENSE AND WITH THE
   INCLUSION OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE OR ANY  OTHER
   COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
   OTHER PERSON.  NO TITLE TO AND OWNERSHIP OF THE  SOFTWARE  IS  HEREBY
   TRANSFERRED.

   THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT  NOTICE
   AND  SHOULD  NOT  BE  CONSTRUED  AS A COMMITMENT BY DIGITAL EQUIPMENT
   CORPORATION.

   DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY  OF  ITS
   SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
   INSTALLING DECmail/MS SOFTWARE                             Page 2


   1.0  DECMAIL/MS DISTRIBUTION


   There are four directory areas on this update tape which  contain
   files relating to the DECmail/MS product.  These areas are:

        PS:<DOCUMENTATION>         PS:<SOURCES.MS>        
        PS:<SUBSYS>                PS:<SOURCES.MX>


         o  The PS:<DOCUMENTATION> area  contains  the  installation
            instructions (MS-MX.DOC which is this document), and the
            beware file (MS-MX.BWR).

         o  The PS:<SUBSYS> area contains the DECmail/MS  executable
            files  (MS.EXE  and MX.EXE) and the DECmail/MS help file
            (MS.HLP)

         o  The PS:<SOURCES.MS> and  PS:<SOURCES.MX>  areas  contain
            the source files necessary for rebuilding MS and MX.  MS
            is the user interface.  MX manages message transport and
            delivery.





   2.0  INSTALLATION PROCEDURES


        1.  Use DUMPER to transfer the contents of the documentation
            and   executable   files   to   the  appropriate  system
            directories.

        2.  Define the system-wide logical name UPS:  as a directory
            on  the  public structure.  The MX program puts tracking
            information  in  log  files  in  this   directory.    In
            addition,  incoming  network  mail  is  stored  in  this
            directory  before  MX  distributes  it  to   its   final
            destination.   You also put the optional network-related
            files there, as described below.


            EXAMPLE

            In the 6-1-CONFIG.CMD file:

            DEFINE UPS:  PUBLIC:<MX>
   INSTALLING DECmail/MS SOFTWARE                             Page 3


            The quota for this directory should be large,  at  least
            2000 pages, to accommodate incoming network mail.

        3.  MX should be run under an OPERATOR job, preferably under
            PTYCON, as a part of your 6-1-PTYCON.ATO file.




   3.0  OPTIONAL PROCEDURES


         o  When MX detects a fatal error, it can automatically dump
            and  restart  itself.   It  dumps  itself to DMP:MX.DMP.
            DMP:  is normally defined as a system-wide logical name.
            Then,  the  program  that  the  system-wide logical name
            RUNMX:  points to is run.  If you would  rather  examine
            the dump and not have MX automatically restarted, do not
            define RUNMX:.   To  activate  the  restart  capability,
            define RUNMX:  in the 6-1-CONFIG.CMD file, as follows:

            DEFINE RUNMX:  SYS:MX.EXE

         o  In a TOPS-20 cluster, you can set up central "mailboxes"
            on  a  shared  structure.   Mail sent to any node in the
            cluster will be delivered to this structure,  and  users
            will  be  able  to  read  their  mail from any node.  To
            implement central mailboxes, do the following:


             o  Redefine POBOX:  on  each  system  to  be  the  same
                shared  structure.   (The system-logical name POBOX:
                is defined as the public structure by default.   The
                DECmail/MS  system  expects  all mail files to be on
                POBOX:.)

                EXAMPLE

                In the 6-1-CONFIG.CMD file on each system:


                DEFINE POBOX:  COMMON:


                This command assumes you already  have  a  structure
                called COMMON.


             o  Set up directories on POBOX:  for all users  in  the
                cluster.
   INSTALLING DECmail/MS SOFTWARE                             Page 4


             o  Make sure that users are familiar  with  the  ACCESS
                command so that they can access their POBOX:  areas.

             o  To facilitate mail delivery among  cluster  systems,
                put  the  names of all cluster nodes, including this
                system's, in UPS:LCHOST.TXT,  one  per  line.   Mail
                sent  within  the  cluster will then be delivered as
                local mail, rather than as network mail, saving time
                and system resources.

                EXAMPLE

                SYSA
                SYSB
                SYSC


         o  Create the file UPS:DNHOST.TXT if:

             o  You have a DECnet network with Phase 3 nodes out  of
                the  area.   Put  the  names  and routing strings of
                these nodes in this file.

                EXAMPLE

                SYSA,SYSB::SYSA::

                In this example, SYSA is a Phase 3 system in another
                area,  and SYSB is a Phase 4 system in the same area
                as SYSA.

             o  There are DECnet nodes that  you  do  not  want  the
                DECmail/MS  system  to recognize.  Users will not be
                able to send mail to these nodes.  However, mail can
                be  received  from them.  Add the /INVALID switch to
                the entry in the DNHOST.TXT file.

                EXAMPLE

                SYSA/INVALID
                SYSG/INVALID
   INSTALLING DECmail/MS SOFTWARE                             Page 5


   4.0  BUILDING MS AND MX FROM SOURCES


         o  First define REL:  to point to SYS:  i.e.  "Define  REL:
            SYS:".

         o  In the MS sources area is a  file  called  MS.CTL  which
            will  build  MS.   If  you  specify  /TAG:COMP  when the
            control file is submitted, it will force a recompilation
            of all sources.

         o  In order to rebuild MX completely from the  MX  sources,
            you  must  have the BLISS-36 compiler.  Use the MX20.CTL
            file to rebuild MX.




   5.0  TAILORING MX TO YOUR MAIL TRAFFIC NEEDS

   One reason for rebuilding MX is to set up  a  default  number  of
   listeners  (DECnet connections that accept the incoming message).
   This allows you to tailor MX to handle heavier SMTP or  VMS  mail
   traffic  loads.  The number of SMTP listeners to be started up is
   in location NSMTP.  The number of MAIL-11 listeners to be started
   up  is  in  location  NVM11.   These can be poked with DDT before
   starting MX to change the default values.  The default values are
   2 SMTP listeners, and 3 MAIL-11 listeners.

   Alternatively, you can edit NETTAB.MAC and  change  the  literals
   DNSMTP  and  DNVM11  to  appropriate  values, compile NETTAB, and
   relink MX...

   Please refer to the MS.BWR file for more information about  MS/MX
   options.