 


















          Message Exchange Installation Guide



          December 1995



          This manual provides installation and setup
          instructions for Message Exchange, electronic mail
          software for VMS systems.




          Revision/Update Information:  This is a revised manual.
                                        Revision bars indicate
                                        changes made since the
                                        last version.

          Operating System and Version: VMS V5.0 or later

                                        OpenVMS AXP V1.0 or later

          Software Version:             Message Exchange V4.2

          Matt Madison and Hunter Goatley
          MadGoat Software

 








          ________________________
          11 December 1995

          Permission is granted to copy and redistribute this
          document for no commercial gain.

          The information in this document is subject to change
          without notice and should not be construed as a
          commitment by MadGoat Software. The authors and
          MadGoat Software assume no responsibility for any
          errors that may appear in this document.

          DISCLAIMER: The software described in this document is
          provided "as is". No guarantee is made by the authors
          or the authors' employers as to the suitability,
          reliability, security, usefulness, or performance
          of this software.

          MX was originally written by Matthew D. Madison,
          formerly of Rensselaer Polytechnic Institute and
          currently employed by TGV, Inc. The software is
          currently maintained by Hunter Goatley, formerly of
          Western Kentucky University and currently employed by
          The LOKI Group, Inc.

          The following are trademarks of Digital Equipment
          Corporation:

          DEC                DECnet              P.S.I.
          ULTRIX             VAX                 VAXcluster
          VMS                AXP                 VMScluster

          Jnet is a registered trademark of Wingra Technologies,
          Inc.

          MultiNet is a registered trademark of TGV, Inc.

          TCPware is a trademark of Process Software
          Corporation.

          WIN/TCP and Pathway are registered trademarks of The
          Wollongong Group, Inc.

          __________
          Copyright 1995 MadGoat Software. ALL RIGHTS RESERVED.

 









          _______________________________________________________

          Contents

                _________________________________________________
                PREFACE                                       vii

          _______________________________________________________
          CHAPTER 1  PREPARING TO INSTALL MESSAGE
                     EXCHANGE                                 1-1

                _________________________________________________
                1.1   PREREQUISITE SOFTWARE                   1-1

                _________________________________________________
                1.2   VMSCLUSTER SUPPORT AND MX CLUSTERS      1-1

                1.2.1     Answering VMScluster-related
                          Installation Questions  ________    1-2

                1.2.2     Mixed VMSclusters (VAX and AXP
                          systems)  ______________________    1-2

                _________________________________________________
                1.3   DETERMINING YOUR NODE NAME              1-3

                _________________________________________________
                1.4   ACCESSING THE ONLINE RELEASE NOTES      1-4

                _________________________________________________
                1.5   MAILER ACCOUNTS                         1-5

                1.5.1     SMTP-over-DECnet/X.25 Dedicated
                          Account  _______________________    1-6

                _________________________________________________
                1.6   INSTALLATION PROCEDURE REQUIREMENTS     1-6

                _________________________________________________
                1.7   SAVING CURRENT CONFIGURATION           1-10


                                                              iii

 


          Contents





                _________________________________________________
                1.8   JNET LOGICAL NAMES                     1-10


          _______________________________________________________
          CHAPTER 2  INSTALLING MESSAGE EXCHANGE              2-1

                _________________________________________________
                2.1   SHUTTING DOWN MX                        2-1

                _________________________________________________
                2.2   INVOKING VMSINSTAL                      2-1

                _________________________________________________
                2.3   MIXED VAX AND AXP VMSCLUSTER
                      SUPPORT                                 2-2

                _________________________________________________
                2.4   INSTALLATION OPTIONS                    2-4

                _________________________________________________
                2.5   COMPONENT SELECTION                     2-4

                _________________________________________________
                2.6   BASE SOFTWARE CONFIGURATION             2-6

                2.6.1     Placing the MX Directories  ____    2-6

                2.6.2     Selecting the Size of the MX
                          Message Queue  _________________    2-7

                2.6.3     Entering Host Names  ___________    2-8

                _________________________________________________
                2.7   SELECTING NODES AND NUMBERS FOR MX
                      PROCESSING AGENTS                       2-8

                _________________________________________________
                2.8   NETLIB COMPONENT INSTALLATION           2-9

          iv

 


                                                         Contents





                _________________________________________________
                2.9   THE INSTALLATION COMPLETES             2-11


          _______________________________________________________
          CHAPTER 3  POST-INSTALLATION INFORMATION            3-1

                _________________________________________________
                3.1   CONFIGURING MX                          3-1

                _________________________________________________
                3.2   ESTABLISHING A POSTMASTER               3-2

                _________________________________________________
                3.3   ADDING MX STARTUP TO SYSTEM STARTUP     3-2

                3.3.1     MX Jnet Startup  _______________    3-4

                3.3.2     Example  _______________________    3-5

                _________________________________________________
                3.4   ADDING MX SHUTDOWN TO SYSTEM
                      SHUTDOWN                                3-6

                _________________________________________________
                3.5   ESTABLISHING YOUR TIME ZONE             3-6

                3.5.1     The Product-Specific Time Zone
                          Logicals  ______________________    3-6

                3.5.2     The MX Timezone Logicals  ______    3-7

                _________________________________________________
                3.6   INTERFACING WITH TCP/IP                 3-8

                3.6.1     Disabling Vendor SMTP Support  _    3-8
                3.6.1.1     Disabling CMUIP SMTP, 3-8
                3.6.1.2     Disabling MultiNet SMTP, 3-9
                3.6.1.3     Disabling TCPware SMTP, 3-9
                3.6.1.4     Disabling UCX SMTP, 3-9
                3.6.1.5     Disabling Wollongong PathWay
                            SMTP, 3-10

                                                                v

 


          Contents





                3.6.2     Ensuring SMTP Server Restarts  _   3-11

                3.6.3     Enabling SMTP Kanji Support  ___   3-11

                _________________________________________________
                3.7   INTERFACING WITH UUCP                  3-12

                _________________________________________________
                3.8   SMTP SUPPORT FOR DECNET AND X.25       3-13

                3.8.1     Creating a DECnet Object for
                          DECnet-SMTP  ___________________   3-13

                3.8.2     Creating a DECnet Object for
                          X.25-SMTP  _____________________   3-15

                _________________________________________________
                3.9   CUSTOMIZING MAILING LIST AND FILE
                      SERVER FILES                           3-16

                _________________________________________________
                3.10  SETTING UP MXALIAS                     3-17

                _________________________________________________
                3.11  STARTING MX                            3-18

                _________________________________________________
                3.12  REGISTERING YOUR INSTALLATION          3-18

          _______________________________________________________
          APPENDIX A  SAMPLE MX INSTALLATIONS                 A-1

                _________________________________________________
                A.1   NON-CLUSTERED INSTALLATION              A-1

                _________________________________________________
                A.2   CLUSTERED INSTALLATION                  A-6



          vi

 


                                                         Contents





          _______________________________________________________
          APPENDIX B  CONTENTS OF DISTRIBUTION KIT            B-1


          _______________________________________________________
          APPENDIX C  FILES CREATED DURING INSTALLATION       C-1


          _______________________________________________________
          FIGURES

                1-1       Mailer Account attributes  _____    1-7

                1-2       SMTP-over-DECnet server account
                          attributes  ____________________    1-8

          _______________________________________________________
          TABLES

                B-1       MX installation kit save sets  _    B-1

                C-1       Message Exchange files created
                          during installation  ___________    C-2

















                                                              vii

 







          _______________________________________________________

          Preface

          This guide describes how to install Message Exchange
          (MX).

          __________________________________________________________________

          Intended Audience

          This manual is intended for use by the system manager
          or any individual responsible for installing and
          maintaining MX.

          __________________________________________________________________

          Document Structure

          This guide consists of three chapters and three
          appendices.

          Chapter    Contains pre-installation information.
          1

          Chapter    Describes the MX installation procedure.
          2

          Chapter    Contains post-installation information.
          3

          Appendix   Contains a listing of a sample installation.
          A

          Appendix   Describes the contents of the MX
          B          distribution kit.

          Appendix   Contains a list of the files created by an
          C          installation.

          __________________________________________________________________

          Related Documents

          You can find additional information in the following
          documents:

          o  Message Exchange Management Guide describes the
             management of the MX software.

                                                              vii

 


          Preface





          o  Message Exchange User's Guide describes MX features
             available to general users.

          o  Message Exchange Programmer's Guide describes the
             various programming interfaces for customizing MX.

          o  Message Exchange Mailing List/File Server Guide
             describes the MX Mailing List and File Server.

          o  Message Exchange Release Notes contain information
             and updates not included in this manual. The release
             notes are part of the software distribution kit.
             Release notes are also included in the distribution
             kit for NETLIB, the TCP/IP interface library.

          o  VMS Mail Utility Manual, part of the VMS
             documentation set, contains information about the
             VMS Mail utility.






















          viii

 








          _______________________________________________________

   1      Preparing to Install Message Exchange



          This chapter describes the steps that should be taken
          prior to installing the Message Exchange software.

          __________________________________________________________________

   1.1    Prerequisite Software

          MX requires VMS version V5.0 or later or OpenVMS AXP
          V1.0 or later to run. The SMTP support option requires
          a NETLIB-supported TCP/IP package (refer to the NETLIB
          release notes for further information). SMTP-over-
          DECnet requires DECnet, but does not require either
          NETLIB or any TCP/IP package. The Jnet support option
          requires Jnet V3.5 or later. The UUCP support option
          requires DECUS UUCP V1.1 or later.

          __________________________________________________________________

   1.2    VMScluster Support and MX Clusters

          MX fully supports VMScluster systems in both
          homogeneous and heterogeneous configurations.

          An "MX cluster" consists of one or more VMScluster
          nodes that meet the following criteria:

          1  All nodes in the MX cluster share one User
             Authorization File (SYSUAF.DAT) and one VMS Mail
             profile (VMSMAIL_PROFILE.DATA).

          2  All nodes have mounted the disk that contains the MX
             images and directories.

          3  All nodes have mounted the disk that contains the
             message queue.

                                                              1-1

 


          Preparing to Install Message Exchange





          4  If MX is to be used for network mail, at least one
             node in the MX cluster is running the networking
             software required for each type of network link
             desired.

          5  The logical name MAIL$SYSTEM_FLAGS is defined to
             a value of at least 3. (Refer to VMS Mail Utility
             Manual for further information on MAIL$SYSTEM_
             FLAGS.)

          For homogeneous VMScluster systems, the MX cluster
          will usually include all nodes in the VMScluster.

          ___________________________

   1.2.1  Answering VMScluster-related Installation Questions

          The MX installation procedure automatically detects
          that you are in a VMScluster and will ask additional
          questions during installation about where in the
          cluster each installed MX processing agent should
          run. The processing agents are programs which are
          run as detached processes. They can be run on any or
          all nodes in the cluster (following the MX Cluster
          guidelines outlined above), and will automatically
          cooperate in providing their respective services.

          When asked to provide a cluster node name for running
          the processing agents, be sure to specify the SCSNODE
          name (or use an asterisk ("*") to have an agent run on
          all nodes in the cluster).

          ___________________________

   1.2.2  Mixed VMSclusters (VAX and AXP systems)

          Mixed VMSclusters that consist of both VAX and AXP
          systems are fully supported by MX. The MX directory
          tree can be shared by both systems if it resides on
          a common disk. When the VAX and AXP systems share a
          common MX directory, agents may be run on both types
          of systems.

          1-2

 


                            Preparing to Install Message Exchange





          When MX determines that the node is part of a cluster,
          it will ask whether or not the cluster contains both
          VAX and AXP systems. Additional questions relating to
          mixed-VMScluster support will be asked if the cluster
          is mixed.

          Note: MX must be installed twice on a mixed-VMScluster:
          once on a VAX system and once on an AXP system. This
          is necessary because the MX executables are linked
          during the MX installation. Installing MX on a VAX
          produces the VAX executable images and installing it
          on an AXP produces the AXP images.

          If the VAX and AXP systems will be sharing an MX
          directory, it is only necessary to install the full
          MX kit on one of the systems (VAX or AXP). For the
          second installation on the other type of machine, you
          can elect to install only the executables for that
          machine. The installation will prompt for the type of
          installation to be performed. Choosing to install only
          the executables on the second installation eliminates
          the need to specify MX configuration information (host
          name, etc.) again.

          The MX_ROOT: directory tree contains two directories
          for executables: MX_ROOT:[EXE] for VAX executables and
          MX_ROOT:[ALPHA_EXE] for AXP executables. The logical
          MX_EXE:, which is used in all examples below, will
          automatically be defined appropriately on each system
          in the cluster.

          __________________________________________________________________

   1.3    Determining Your Node Name

          MX requires two node names for its operation.
          The first, the MX cluster name, is used by MX to
          coordinate access to the message queue.

          o  For a stand-alone (non-clustered) system, the MX
             cluster name usually corresponds to your DECnet node
             name. If you are not running DECnet, you can use any
             1-to-6 character name.

                                                              1-3

 


          Preparing to Install Message Exchange





          o  For a VMScluster system, the MX cluster name should
             correspond to your DECnet cluster alias node name.
             If do not have a cluster alias, you should use
             the DECnet node name of one of the nodes in the
             MX cluster.

          The second node name is the MX network node name.
          This is the name that is used by the MX software to
          identify mail originating locally. You should decide
          on a node name for your system before installing the
          MX software. If your host has a registered Internet
          domain name, you should use that name. If you are on
          BITNET or a UUCP network and do not have a registered
          Internet domain name, you should use your BITNET or
          UUCP host name. Otherwise, you should use a host name
          that fits with the naming conventions at your site.

          In an MX cluster environment, MX will use a single
          network name to identify the entire cluster. If you
          have several nodes with their own network node names,
          and your networking software does not support the use
          of a cluster-wide alias, you could either pick one
          node to be the "master" for E-mail purposes or use
          the MX_VMSMAIL_FROM_FORMAT logical name (described
          in Message Exchange Management Guide) to have each
          node insert its own host name in return addresses on
          outgoing messages. What you do will depend on your
          network software and setup.

          __________________________________________________________________

   1.4    Accessing the Online Release Notes

          MX provides online release notes, which you can
          display or print by using VMSINSTAL with the
          OPTIONS N parameter. After the installation, you
          can read the release notes by printing the file
          SYS$HELP:MXvvn.RELEASE_NOTES, where "vvn" denotes
          the version number of the software. For example, for
          version V3.0 of MX, the file name would be MX030.

          1-4

 


                            Preparing to Install Message Exchange





          The release notes for NETLIB are provided in the
          file SYS$HELP:NETLIBvvn.RELEASE_NOTES, where "vvn"
          identifies the version of NETLIB shipped with the MX
          distribution kit. This file is created during NETLIB
          installation and is not accessible through VMSINSTAL
          OPTIONS N.

          __________________________________________________________________

   1.5    Mailer Accounts

          You can run the detached processes MX uses under the
          SYSTEM account, or, if you prefer, under a separate
          "mailer" account.

          Note, however, that using a mailer account may
          complicate the process for starting up MX on your
          system; see Section 3.3 for further information on MX
          startup procedures.

          If you intend to use an account other than SYSTEM for
          running the MX detached processes, you should create
          the account before installing MX. The mailer account
          should have the following attributes:

          o  a username of eight characters or less.

          o  full batch access, no interactive access.

          o  network access, only if SMTP-over-DECnet is used and
             you do not wish to create a dedicated account for
             the SMTP-over-DECnet object.

          o  the INTERNET_ACCESS identifier, if needed for CMU-
             Tek TCP/IP access.

          o  the ARPANET_ACCESS identifier, if needed for CMU-Tek
             TCP/IP access.

          o  the following authorized and default privileges:
             CMKRNL, SYSNAM, DETACH, WORLD, PHY_IO, SYSPRV,
             SYSLCK, EXQUOTA, TMPMBX, and NETMBX. (BYPASS may
             also be required if using DECUS UUCP.)

          o  a subprocess limit (PRCLM) of at least 1.

                                                              1-5

 


          Preparing to Install Message Exchange





          o  no detached process limit (MAXDETACH of 0).

          o  a login directory that is owned by the account.

          Figure 1-1 shows the UAF entry for a typical Mailer
          account.

          ___________________________

   1.5.1  SMTP-over-DECnet/X.25 Dedicated Account

          If you intend to use the MX SMTP-over-DECnet or
          SMTP-over-X.25 support, you may want to establish a
          special server account to be used exclusively for
          the DECSMTP and X25_SMTP DECnet objects. If so, you
          should ensure that the accounts have NETWORK access
          and the privileges TMPMBX, NETMBX, SYSPRV, and SYSLCK
          (both authorized and default). Figure 1-2 shows the
          UAF entry for a typical SMTP-over-DECnet or SMTP-
          over-X.25 server account. See Section 3.8 for more
          information on setting up the MX SMTP-over-DECnet and
          SMTP-over-X.25 support.

          __________________________________________________________________

   1.6    Installation Procedure Requirements

          Before installing MX, ensure that the following
          privileges, resources, and requirements are met:

          o  Operating System Version

             MX V4.2 runs on OpenVMS VAX (VAX/VMS) V5.0 and
             higher and on all versions of OpenVMS AXP.

          o  Layered Product Versions




          1-6

 


                            Preparing to Install Message Exchange




          Figure 1-1  Mailer Account attributes
          _______________________________________________________

          Username: MAILER                           Owner:  MX Mailer account
          Account:  NETSTUF                          UIC:    [1076,76] ([MAILER])
          CLI:      DCL                              Tables: DCLTABLES
          Default:  USER_DISK:[MAILER]
          LGICMD:   NL:
          Login Flags:  Disctly Defcli
          Primary days:   Mon Tue Wed Thu Fri
          Secondary days:                     Sat Sun
          Primary   000000000011111111112222  Secondary 000000000011111111112222
          Day Hours 012345678901234567890123  Day Hours 012345678901234567890123
          Network:  -----  No access  ------            -----  No access  ------
          Batch:    ##### Full access ######            ##### Full access ######
          Local:    -----  No access  ------            -----  No access  ------
          Dialup:   -----  No access  ------            -----  No access  ------
          Remote:   -----  No access  ------            -----  No access  ------
          Expiration:            (none)    Pwdminimum:  3   Login Fails:     0
          Pwdlifetime:           (none)    Pwdchange:             (none)
          Last Login:            (none) (interactive), 19-JAN-1990 14:38 (non-interactive)
          Maxjobs:         0  Fillm:        60  Bytlm:        36000
          Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
          Maxdetach:       0  BIOlm:        20  JTquota:       1024
          Prclm:           4  DIOlm:        18  WSdef:          512
          Prio:            4  ASTlm:       325  WSquo:          512
          Queprio:       100  TQElm:        10  WSextent:      2048
          CPU:        (none)  Enqlm:       600  Pgflquo:      25600
          Authorized Privileges:
            CMKRNL SYSNAM DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCK
          Default Privileges:
            CMKRNL SYSNAM DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCK
          Identifier                         Value           Attributes
            ARPANET_ACCESS                   %X80010042      NORESOURCE NODYNAMIC
          __INTERNET_ACCESS__________________%X80010043______NORESOURCE NODYNAMIC

             Refer to the NETLIB release notes for details on
             TCP/IP requirements. For Jnet support, MX V4.2
             requires Jnet V3.5 or later. For UUCP support, MX


                                                              1-7

 


          Preparing to Install Message Exchange




          Figure 1-2  SMTP-over-DECnet server account attributes
          _______________________________________________________

          Username: DNSMTP_SRV                       Owner:  MX DECSMTP object account
          Account:  NETSTUF                          UIC:    [1076,77] ([DNSMTP_SRV])
          CLI:      DCL                              Tables: DCLTABLES
          Default:  USER_DISK:[DNSMTP_SRV]
          LGICMD:   NL:
          Login Flags:  Disctly Defcli
          Primary days:   Mon Tue Wed Thu Fri
          Secondary days:                     Sat Sun
          Primary   000000000011111111112222  Secondary 000000000011111111112222
          Day Hours 012345678901234567890123  Day Hours 012345678901234567890123
          Network:  ##### Full access ######            ##### Full access ######
          Batch:    -----  No access  ------            -----  No access  ------
          Local:    -----  No access  ------            -----  No access  ------
          Dialup:   -----  No access  ------            -----  No access  ------
          Remote:   -----  No access  ------            -----  No access  ------
          Expiration:            (none)    Pwdminimum:  3   Login Fails:     0
          Pwdlifetime:           (none)    Pwdchange:             (none)
          Last Login:            (none) (interactive), 19-JAN-1990 14:38 (non-interactive)
          Maxjobs:         0  Fillm:        60  Bytlm:        36000
          Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
          Maxdetach:       0  BIOlm:        20  JTquota:       1024
          Prclm:           4  DIOlm:        18  WSdef:          512
          Prio:            4  ASTlm:       325  WSquo:          512
          Queprio:       100  TQElm:        10  WSextent:      2048
          CPU:        (none)  Enqlm:       600  Pgflquo:      25600
          Authorized Privileges:
            TMPMBX NETMBX SYSPRV SYSLCK
          Default Privileges:
          __TMPMBX_NETMBX_SYSPRV_SYSLCK__________________________

             V4.2 requires DECUS UUCP V1.1 or later. For SMTP-
             over-X.25, MX V4.2 requires VAX P.S.I. or VAX P.S.I.
             Access V4.2 or later.

          o  all the normal privileges and quotas of the default
             SYSTEM account.


          1-8

 


                            Preparing to Install Message Exchange





          o  approximately 5 minutes to 1 hour, depending on
             your system configuration, distribution medium, and
             options selected.

          o  11 free global sections and 60 free global pages.
             For SMTP support (over TCP/IP), NETLIB also requires
             4 free global sections and 25 free global pages
             (more if multiple transports are installed).

          o  approximately 36,000 free blocks on a disk for use
             during the installation procedure; this can be the
             system disk or a disk specified with the VMSINSTAL
             AWD option.

          o  approximately 5 free blocks on the system disk for
             permanent files.

          o  approximately 3,000 free blocks on any disk for MX
             base software, and the following additional free
             disk blocks:

            o  approximately 500 free blocks for each MX
               optional transport agent.

            o  approximately 800 free blocks for mailing
               list/file server support.

            o  approximately 4,000 free blocks for MX
               documentation.

            o  approximately 110 free blocks for the MX example
               files.

            o  approximately 1,100 free blocks for the MX
               contributed files and programs.

          o  a minimum of 5,000 free blocks on any disk for
             message queue space.

          o  if you are running CMU-Tek TCP/IP, the value of the
             SYSGEN parameter MAXBUF must be at least 2300.

                                                              1-9

 


          Preparing to Install Message Exchange




          __________________________________________________________________

   1.7    Saving Current Configuration

          If MX is already installed on your system, you should
          create an MCP command file from your current MX
          configuration database prior to installing a new
          version of MX. To do this, use the following commands:

              $ MCP :== $MX_EXE:MCP
              $ MCP/FILE=MX_DIR:MX_CONFIG SHOW ALL/OUTPUT=MX_DIR:OLD_CONFIG.MCP/COMMAND

          You can then use this MX command file to re-create
          your MX configuration database once the new version of
          MX is installed.

          __________________________________________________________________

   1.8    Jnet Logical Names

          If you intend to install MX with Jnet interface
          support, you should ensure that the Jnet logical
          names are defined prior to installing MX. The MX
          installation procedure links its Jnet support against
          the JANSHR shareable library, which is part of Jnet.

          If you decide to shut down Jnet on your system prior
          to installing MX, you should do so using the WARM
          option:

              $ @JAN_SYS:JANSTOP WARM

          This will leave the Jnet logical names intact while
          shutting down the Jnet processes.







          1-10

 








          _______________________________________________________

   2      Installing Message Exchange



          MX uses VMSINSTAL for installation. If you do not
          know how to use VMSINSTAL, you should first read
          the chapter on installing software in the VMS System
          Manager's Manual. For the installation, you should be
          logged into the SYSTEM account, or another suitably
          privileged account.

          Note: MX must be installed twice on a mixed-VMScluster:
          once on a VAX system, and once on an AXP system. This
          is necessary because the MX executables are linked
          during the MX installation. Installing MX on a VAX
          produces the VAX executable images and installing it
          on an AXP produces the AXP images.

          __________________________________________________________________

   2.1    Shutting down MX

          If any MX processes are currently running, you should
          stop them before installing a new version of MX,
          including any SMTP servers (which are not shutdown
          with the MCP SHUTDOWN command in versions of MX prior
          to V2.2-2). Unprocessed mail should remain queued
          until you start the new MX processes.

          __________________________________________________________________

   2.2    Invoking VMSINSTAL

          Invoke VMSINSTAL to install MX.

              $ @SYS$UPDATE:VMSINSTAL MXvvn ddcu:


                                                              2-1

 


          Installing Message Exchange





          Substitute the appropriate values for vvn and ddcu.

                       VAX/VMS Software Product Installation Procedure V5.5-2

              It is dd-Mmm-yyyy at hh:mm.
              Enter a question mark (?) at any time for help.

          If there are any users logged into the system, you
          will see the message

              %VMSINSTAL-W-ACTIVE, The following processes are still active:
              ...process names...

          You can install MX while users are logged in, though
          it is safer to perform the installation while no one
          is logged in and while your network links are shut
          down.

              * Do you want to continue anyway [NO]?

          If you wish to continue, answer YES.

              * Are you satisfied with the backup of your system disk [YES]?

          If you feel comfortable with your system disk backup,
          answer YES. Otherwise, answer NO, perform the backup,
          then restart the installation procedure.

          __________________________________________________________________

   2.3    Mixed VAX and AXP VMScluster Support

          If your system is part of a VMScluster that includes
          both VAX and AXP systems, you will need to install
          MX twice: once on a VAX, and once on an AXP. This is
          required because the MX executable images are linked
          during the installation and cross-linking is not
          supported. The MX installation will display a message
          indicating the possible need to install MX twice and
          will ask you if the cluster includes both VAX and AXP
          systems that will share a common MX directory:

          2-2

 


                                      Installing Message Exchange





                  Mixed VAX and AXP VMSclusters
                  -----------------------------

                  This system is part of a VMScluster.  If this VMScluster includes
                  both VAX and AXP systems that will share the MX directories and
                  configuration files, it will be necessary to install MX twice:
                  once on a VAX system and once on an AXP system.  It is only
                  necessary to install the FULL MX kit on one type of system
                  (VAX or AXP).

                  The dual installation is required because the MX images are
                  linked during installation.  However, when installing MX on the
                  second system, you may elect to install only the executables to
                  avoid the need to reconfigure MX.

                  The full MX installation MUST be installed from one of the systems
                  for MX to work.  During that installation, information must be
                  supplied pertaining to which nodes will run which agents, etc.

              *Does this VMScluster include both VAX and AXP systems [NO]?

          If you answer ``NO'' to this question, the
          installation proceeds to the next step (Section 2.4).
          Answering ``YES'' will cause the installation to ask a
          f|w more questions:
           |
           |  *Will the VAX and AXP systems share a common MX directory [YES]?
           |  *Has MX V4.2 already been installed on an AXP system in this cluster [NO]?

          If they will share a common MX directory, you only
          need to configure MX during one of the installations.
          For example, if you install MX on a VAX first as
          in the example above, you will have to provide site
          configuration information (described in the following
          sections). If you've already installed MX on another
          system in the cluster, answering ``Y'' to the second
          question will cause the following prompt to appear:

              *Do you wish to install only the VAX executables [YES]?

                                                              2-3

 


          Installing Message Exchange





          You should answer ``YES'' to this question only
          if you have already installed the current version
          of MX on another system in the cluster. Answering
          ``YES'' causes MX to be paranoid and ask for another
          confirmation:

                 Only the VAX executables will be installed

              *Is this correct [YES]?

          __________________________________________________________________

   2.4    Installation Options

          The next question is

              * Do you want to purge files replaced by this installation [YES]?

          If this is the first time you have installed MX,
          answering NO to this question can save some time when
          the MX files are moved into their directories.

          __________________________________________________________________

   2.5    Component Selection

          A menu of MX components appears next, and you are
          asked to enter your choices from the menu:

                   1. [ ] Base MX software
                   2. [ ] NETLIB network support
                   3. [ ] SMTP interface support
                   4. [ ] Jnet interface support
                   5. [ ] UUCP interface support
                   6. [ ] SMTP-over-DECnet support
                   7. [ ] SMTP-over-X.25 support
                   8. [ ] Site-provided interface support
                   9. [ ] Mailing List/File Server support
                  10. [ ] Documentation
                  11. [ ] Example files and programs
                  12. [ ] User-contributed files and programs

                  13.     Exit

          2-4

 


                                      Installing Message Exchange





              *       Your choice [13]:

          Note: When installing MX on an AXP system, the menu
          items for those agents whose third-party transports
          have not been ported to AXP (DECUS UUCP, X.25) will
          not be displayed.

          Enter the number corresponding to the component you
          wish to install; multiple components may be selected
          by entering the numbers as a comma-separated list.
          The menu is displayed again after each selection,
          with asterisks appearing next to the items you have
          selected; selecting a component twice removes it from
          the selection list.

          When you are upgrading to a new version of MX, the
          installation procedure will look at your current
          configuration to automatically determine the
          components that should be installed. If you wish
          to omit any of those components that were selected,
          simply select them again to remove it from the list.

          When you have selected the components you want to
          install, enter 13 to exit the menu. Your selections
          are displayed again and you are asked to confirm your
          selections:

                  You have selected the following optional components:

                  (selected components listed here)

              * Is this correct [YES]?

          Press RETURN to continue the installation, or enter NO
          to return to the components menu.

          Component Notes

          You must install the Base software component if this
          is your first installation of MX, or if you are
          upgrading from a previous version of MX. The other
          components are optional and may be installed at any
          time after the Base component is installed. If you re-
          install the Base component, you must also re-install

                                                              2-5

 


          Installing Message Exchange





          all desired optional components as well, except for
          documentation, examples and contributed files.

          If you elect to install SMTP support, NETLIB support
          will automatically be installed as well. If you have
          already installed the NETLIB support component, you
          can disable the NETLIB re-installation by re-selecting
          it on the menu.

          __________________________________________________________________

   2.6    Base Software Configuration

          If you are installing the Base software component,
          the saveset containing the Base support files will be
          loaded and you will be asked some questions regarding
          the configuration of the Base software.

          ___________________________

   2.6.1  Placing the MX Directories

          A brief description of the directory structure used by
          MX is displayed, and you are asked:

              * Where should the MX top directory be located [SYS$SYSDEVICE:[MX]]:

          You may place the MX directories on any disk you
          like. If MX is already installed on the system and
          its logical names are defined, the default answer will
          be the definition of your existing MX root directory.

          Note: If you are installing MX on a mixed VMScluster
          where VAX and AXP systems will share a common
          directory, be sure you specify a disk that is common
          to both types of systems. SYS$SYSDEVICE: is not an
          appropriate response, since VAX and AXP systems cannot
          share system disks.

          The file queueing used by MX is described next, and
          you are asked:

              * Where would you like the MX file queue [SYS$SYSDEVICE:[MX.QUEUE]]:

          2-6

 


                                      Installing Message Exchange





          You can keep the queue with the MX directories, or
          you can place it on another device, depending on how
          busy your disks are. If MX is already installed on
          the system, and you keep the same queue directory, any
          files already in the queue will be retained.

          Note: See the note above!

          MX actually uses 10 subdirectories under the MX queue
          directory. Those directories are automatically created
          by the installation procedure.

          ___________________________

   2.6.2  Selecting the Size of the MX Message Queue

          The MX queueing subsystem uses a fixed-size sequential
          file for the MX queue. The size of the file determines
          the number of messages that can be in the queue at any
          one time. The size of the file can be extended at a
          later date using the MCP command QUEUE EXTEND.

          For each message, one block is required. To allow up
          to 5,000 messages to be in the queue at any one time,
          the queue file must be slightly larger than 5,000
          blocks. The required file size depends heavily on your
          site's e-mail traffic. For a workstation that normally
          receives a couple of hundred messages a day, a queue
          file of 100 blocks or less is probably sufficient.

          For sites with a lot of mail traffic, a size of 5,000-
          10,000 blocks is recommended. If disk space is not
          a problem, you can specify as many as 131,072 (128K)
          messages, which is the maximum number MX is designed
          to handle.

          The installation prompts you for the size of the file:

              * Maximum number of entries to allow in the queue [5000]:

                                                              2-7

 


          Installing Message Exchange




          ___________________________

   2.6.3  Entering Host Names

          If you are installing only the MX executables for a
          system (described in Section 2.3), the installation
          will skip this section.

          The host names MX uses are described as they are in
          Section 1.3. You should have selected the host names
          you want to use prior to installation, so just enter
          the names you selected.

              * Enter the MX cluster name [MYNODE]:
              * Enter the MX network node name:

          The names are displayed again and you are asked to
          confirm their correctness.

          __________________________________________________________________

   2.7    Selecting Nodes and Numbers for MX Processing Agents

          If you are installing only the MX executables for a
          system (described in Section 2.3), the installation
          will skip this section.

          If your system is part of a VMScluster, you will be
          requested to supply the SCS node names of the nodes
          in the cluster where the MX processing agents will
          execute.

          For example, you are asked:

              * Enter the node(s) that will run the Router:
              * Enter the node(s) that will run the Local delivery agent:

          when you install the base software.

          Specify the SCS node names of the nodes in the cluster
          on which the MX processes should run, or enter an
          asterisk ("*") to indicate that they should run on all
          nodes in the cluster.

          You can elect to run multiple processes for some of
          the MX agents. Running more than one process will
          generally increase MX throughput. Whether or not
          you are in a cluster, you will be prompted to enter

          2-8

 


                                      Installing Message Exchange





          the number of processes for each multi-process agent
          for each node. The default value is 1; the maximum
          value is 10. These values can be changed after the
          installation by editing the file MX_DIR:MX_STARTUP_
          INFO.DAT.

              Number of ROUTER agent processes to run on node ABC [1]:
              Number of LOCAL agent processes to run on node ABC [1]:

          __________________________________________________________________

   2.8    NETLIB Component Installation

          If you are installing the NETLIB component (required
          for SMTP support using TCP/IP), the saveset containing
          the NETLIB support files will be loaded and you will
          be asked some questions regarding the configuration of
          NETLIB.

          The NETLIB installation procedure displays a menu of
          supported TCP/IP packages and asks for the packages
          for which you wish to install NETLIB support:

                   1. [ ] CMU-Tek TCP/IP V6.4
                   2. [ ] CMU-Tek TCP/IP V6.5 or later
                   3. [ ] DEC VMS/ULTRIX Connection (UCX) V1.2
                   4. [ ] DEC UCX V1.3 or TCP/IP Services for VMS V2.0 or later
                   5. [ ] TGV MultiNet V2.2 or later
                   6. [ ] PSC TCPware
                   7. [ ] TWG WIN/TCP or PathWay Access for VMS

                   8.     Exit

              *       Your choice [8]:

          The installation procedure attempts to pre-select
          those packages which appear to be installed on the
          system. Selections are made just as from the MX
          optional components menu. When you exit this menu,
          your selections are displayed and you are asked to
          confirm them:

                                                              2-9

 


          Installing Message Exchange





                  You have selected the following TCP/IP support:

                    (packages listed here)

              * Is this correct [YES]?

          Press RETURN to continue or enter NO to return to the
          menu.

          If you elected to install support for more than one
          TCP/IP package, you are then asked to select the one
          that will be used by default when the NETLIB startup
          procedure executes:

                  You have selected support for more than one TCP/IP package.
                  You must now select which is to be used by default on the
                  current system.

                    (packages listed here)

              *       Your choice:

          Select the package you wish to use by default. If
          you need to have different packages used on different
          systems in a VMScluster, you will need to edit the
          NETLIB_STARTUP command procedure as described in
          Section 3.6.

          The final NETLIB installation question asks where the
          NETLIB shareable libraries should be placed:

              * Where should the NETLIB libraries be placed [SYS$COMMON:[SYSLIB]]:

          If you do not wish to install the libraries in
          SYS$LIBRARY, you may specify any other device and
          directory on the system.

          If you are installing MX on a VMScluster containing
          both VAX and Alpha AXP systems, it is recommended that
          you install the NETLIB libraries in the appropriate
          MX executable directory (MX_ROOT:[EXE] for VAX and MX_
          ROOT:[ALPHA_EXE] for AXP). If you do not place them
          in there, you may have to modify the NETLIB startup
          procedure to locate the proper files for each system
          type.

          2-10

 


                                      Installing Message Exchange




          __________________________________________________________________

   2.9    The Installation Completes

          After the configuration questions and NETLIB component
          installations, which always require input from the
          installer, all selected components are installed.
          Files are copied from the each save set of the
          installation kit and the appropriate images are
          linked, then all installed files are copied to their
          destination directories. Informational messages about
          the individual components are displayed as needed.





























                                                             2-11

 








          _______________________________________________________

   3      Post-Installation Information



          This chapter contains important information about
          setting up MX configuration and startup options.

          __________________________________________________________________

   3.1    Configuring MX

          Once the MX files have been installed, you should
          next create an MX configuration database. If you
          were already running MX before the installation and
          saved your configuration commands as described in
          Section 1.7, you can re-create your old configuration
          with the commands:

              $ @SYS$STARTUP:MX_STARTUP LOGICALS
              $ MCP :== $MX_EXE:MCP
              $ MCP
              MCP> @MX_DIR:OLD_CONFIG
              MCP> SAVE MX_DIR:MX_CONFIG.MXCFG
              MCP> EXIT

          If this was a first-time installation, or if you want
          to create a new MX configuration from scratch, you
          should use the MXCONFIG command procedure to create an
          MX configuration database:

              $ @SYS$STARTUP:MX_STARTUP LOGICALS
              $ @MX_DIR:MXCONFIG

          MXCONFIG prompts you for some basic information
          and creates an MCP command file to create an MX
          configuration database. You can use MXCONFIG to define
          all routing information and Postmaster aliases for a
          typical Internet- or BITNET-connected system. Once the
          basic configuration is created with MXCONFIG, you can
          tailor it as you wish using the MCP commands described
          in Message Exchange Management Guide.

                                                              3-1

 


          Post-Installation Information





          Note: If you are upgrading to MX V4.2 from a release
          prior to V3.0, it is recommended that you use the
          MXCONFIG command procedure shipped with this release
          to generate a new MCP configuration file, in order
          to take advantage of the improved rewrite rules for
          gateways included in the new version of MXCONFIG.

          __________________________________________________________________

   3.2    Establishing a Postmaster

          All Internet and BITNET sites that use electronic
          mail must be able to accept mail to the username
          Postmaster. BITNET sites must also accept mail to
          the username POSTMAST (Postmaster truncated to eight
          characters). If you do not have a real username called
          POSTMASTER on your system, you should either establish
          aliases with the MCP DEFINE ALIAS command:

              MCP> DEFINE ALIAS Postmaster "user@host"
              MCP> DEFINE ALIAS POSTMAST   "user@host"

          (substituting appropriate values for user and host),
          or use the SET FORWARD command in VMS Mail to forward
          mail from Postmaster to a real user:

              MAIL> SET FORWARD/USER=POSTMASTER user
              MAIL> SET FORWARD/USER=POSTMAST   user

          Even if you are not connected to the Internet or
          BITNET, it is still a good idea to create a Postmaster
          username or forwarding address.

          __________________________________________________________________

   3.3    Adding MX Startup to System Startup

          The startup procedure for MX may vary depending on:

          o  you are running in a cluster environment

          o  you are running MX processes under a separate mailer
             account

          3-2

 


                                    Post-Installation Information





          In either case, remember that if you are running the
          MX SMTP-over-TCP/IP support, you should start MX after
          you start your TCP/IP software, and if you are running
          the MX Jnet support, you should start MX before you
          start Jnet (although the Jnet interface is started
          during or after the Jnet startup).

          If you are running L-Soft International's LISTSERV,
          you must define the LISTSERV logicals, but not the
          process, before starting MX. For example:

              $ @SYS$STARTUP:LISTSERV_STARTUP.COM LOGICALS
              $ @SYS$STARTUP:MX_STARTUP.COM
              $ @SYS$STARTUP:LISTSERV_STARTUP.COM

          Standalone Systems

          If you intend to run MX under the SYSTEM account, all
          you need to add to your system startup procedure is
          the command:

              $ @SYS$STARTUP:MX_STARTUP

          If you are using a separate mailer account, you would
          use the following commands instead:

              $ @SYS$STARTUP:MX_STARTUP LOGICALS
              $ SUBMIT/NOPRINT/USER=mailer SYS$STARTUP:MX_STARTUP

          For mailer substitute the username you assigned to
          your mailer account.

          Clustered Systems

          In a cluster environment, as long as you are running
          MX under the SYSTEM account, the startup command is as
          easy as for standalone systems:

              $ @SYS$STARTUP:MX_STARTUP

          However, if you are running MX under a separate
          mailer account, how each node in the cluster starts MX
          depends on whether or not it will run one or more of
          the MX processes (as selected during MX installation).

                                                              3-3

 


          Post-Installation Information





          If the node will not run one or more of the MX
          processing agents, such as a satellite node in a
          Local-Area or Mixed-Interconnect VMScluster, all it
          needs to start up MX is the command:

              $ @SYS$STARTUP:MX_STARTUP

          which just defines the necessary logical names and
          install the necessary images for interfacing VMS Mail
          with MX.

          If the node will run one or more MX processes, those
          processes need to be started up under the mailer
          account's username, so you would use the commands:

              $ @SYS$STARTUP:MX_STARTUP LOGICALS
              $ SUBMIT/NOPRINT/USER=mailer/QUEUE=nodeque SYS$STARTUP:MX_STARTUP

          substituting the mailer account name for mailer and
          the name of a batch queue that runs on the local
          system for nodeque.

          ___________________________

   3.3.1  MX Jnet Startup

          If you installed MX Jnet support, you should edit
          the JAN_SYS:JANSITE.COM or JAN_SYS:JANSITECOMMON.COM
          command procedure for your system to include the
          following commands:

              $ DEFINE/SYSTEM/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISP   ! under cold_start
              $ SUBMIT/NOPRINT/QUEUE=batchque/USER=mailer/PARAM=JNET-
                            SYS$STARTUP:MX_STARTUP   ! under warm_start

          In a cluster environment, the queue name you specify
          for batchque must be a batch queue that executes on
          the same node that the Jnet startup is executing on.

          You should also add the following to JAN_
          SYS:JANSITESTOP.COM to ensure a proper shutdown of
          MX Jnet when Jnet is shut down:

              $ MCP :== $MX_EXE:MCP.EXE
              $ MCP SHUTDOWN JNET

          3-4

 


                                    Post-Installation Information





          If you have a mail/file dispatcher you were using with
          Jnet prior to MX installation that you would like to
          continue to use, add the following line before the
          invocation of MX_STARTUP in JANSITECOMMON:

              $ DEFINE/SYSTEM/EXEC MX_LOCAL_MFSDISP file-spec

          MX_MFSDISP will automatically invoke your local
          mail/file dispatcher for all incoming Jnet files that
          it does not transfer into MX.

          ___________________________

   3.3.2  Example

          As an example, take a homogeneous VMScluster with two
          nodes, NODE1 and NODE2, each with a TCP/IP connection
          and a BITNET connection, and several satellite nodes
          that will just be used for sending and receiving mail
          by users (i.e., no MX processes will run on them).

          Both NODE1 and NODE2 have batch queues, called NODE1_
          BATCH and NODE2_BATCH, respectively. The mailer
          account username is MAILER.

          The commands to be added to SYS$MANAGER:SYSTARTUP_
          V5.COM, after TCP/IP startup and before Jnet startup,
          would be:

              $ NODE = F$GETSYI ("NODENAME")
              $ IF NODE .NES. "NODE1" .AND. NODE .NES. "NODE2"
              $ THEN
              $    @SYS$STARTUP:MX_STARTUP
              $ ELSE
              $    SUBMIT/NOPRINT/USER=MAILER/QUEUE='NODE'_BATCH SYS$STARTUP:MX_STARTUP
              $ ENDIF

          The commands to be added to the specific JAN_
          SYS:JANSITE.COM for NODE1 and NODE2 would be:

              $ NODE = F$GETSYI ("NODENAME")
              $ DEFINE/SYSTEM/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISP
              $ SUBMIT/NOPRINT/USER=MAILER/QUEUE='NODE'_BATCH/PARAM=JNET -
                               SYS$STARTUP:MX_STARTUP

                                                              3-5

 


          Post-Installation Information




          __________________________________________________________________

   3.4    Adding MX Shutdown to System Shutdown

          To ensure that MX agent processes are shut down
          cleanly when the system is shut down, add the
          following lines to SYS$MANAGER:SYSHUTDWN.COM:

              $ MCP := $MX_EXE:MCP
              $ MCP SHUTDOWN

          This will notify any agent processes on the system
          that they should shut down without affecting the agent
          processes on other nodes in the cluster.

          __________________________________________________________________

   3.5    Establishing Your Time Zone

          If you are not in the US Eastern time zone, or you are
          not following US standard daylight savings time, or
          you do not like "EST" and "EDT" as time zone names,
          you must make sure that at least one of several time
          zone logicals is defined in SYSTARTUP_V5.COM.

          ___________________________

   3.5.1  The Product-Specific Time Zone Logicals

          MX checks for the existence of one of several time
          zone logicals that specify the timezone string to
          be used when generated RFC822 mail message headers.
          Because most of the delivery transports (Jnet, DECUS
          UUCP, the TCP/IP implementations, etc.) already define
          time zone logicals compatible with MX, it is not
          necessary to define MX-specific logicals.

          The value of the first logical defined in the
          following ordered list is used with no time-zone
          calculations.

          MX_TIMEZONE             MX
          MDM_TIMEZONE            MDMLIB
          SYS$TIMEZONE_NAME       DECdts

          3-6

 


                                    Post-Installation Information






          SYS$TIME_ZONE           DEC TCP/IP Services for VMS
                                  (formerly UCX)
          MULTINET_TIMEZONE       TGV's MultiNet
          JAN_TIME_ZONE           Wingra's Jnet
          UUCP_TIME_ZONE          DECUS UUCP
          WIN$TIME_ZONE           Wollongong's WIN/TCP and
                                  PathWay

          ___________________________

   3.5.2  The MX Timezone Logicals

          If you are in the United States and you are following
          standard US daylight savings time, define the
          following logical name:

              $ DEFINE/SYS/EXEC MX_TZ_PREFIX x

          where x is the letter E, C, M, or P, depending on
          whether you are in the Eastern, Central, Mountain, or
          Pacific time zone.

          If you are not in the United States, or you do not
          wish to use the xST/xDT time zone designation, you
          should define the following logical:

              $ DEFINE/SYS/EXEC MX_TIMEZONE "tzstr"

          where tzstr is a valid (RFC822-compliant) time zone
          designation, such as "-0500". No validity checking
          is performed on this string. Note that the string you
          specify with MX_TIMEZONE is used verbatim. If you use
          MX_TIMEZONE and you observe daylight savings time in
          your area, it is your responsibility for modifying the
          definition of MX_TIMEZONE as needed. You do not need
          to shut down MX to do this.

          If you do not define MX_TZ_PREFIX or MX_TIMEZONE, the
          default (EST/EDT) time zone will be used.

                                                              3-7

 


          Post-Installation Information




          __________________________________________________________________

   3.6    Interfacing with TCP/IP

          The SMTP interface uses the NETLIB transport-
          independent library to interface with the TCP/IP
          package or packages you have installed on the system.
          If you installed NETLIB support for multiple packages,
          you may wish to alter the definition of the logical
          name NETLIB_SHR in SYS$STARTUP:NETLIB_STARTUP.COM to
          use a different TCP/IP package on different systems in
          your cluster.

          If you are using CMU-Tek TCP/IP V6.4: it is strongly
          recommended that you edit SYS$STARTUP:NETLIB_
          STARTUP.COM to change the definition of the NETLIB_
          NAMESERVERS logical name to reflect the actual name
          servers that should be used. This information can be
          found in the file SYS$MANAGER:NAMSRV.CONFIG.

          ___________________________

   3.6.1  Disabling Vendor SMTP Support

          If your TCP/IP vendor provides SMTP support as part
          of its package, you should disable that support before
          starting MX.

          Note: The instructions provided below were valid for
          various versions of each vendor's software. Please
          consult your TCP/IP documentation for more accurate
          instructions.
                 _____________________
                 3.6.1.1  Disabling CMUIP SMTP
          For CMU-OpenVMS/IP (aka CMU-Tek TCP/IP), edit your
          INTERNET.CONFIG file and comment out the line
          that begins with "WKS:25", then restart TCP/IP. In
          addition, you may wish to deassign the system logical
          name TCP$SMTPSV.


          3-8

 


                                    Post-Installation Information




                 _____________________
                 3.6.1.2  Disabling MultiNet SMTP
          For MultiNet, use the Server Configuration Utility to
          disable MultiNet's SMTP service:

              $ MULTINET CONFIGURE/SERVER
              MultiNet Server Configuration Utility 2.2(25)
              [Reading in symbols from SERVER image MULTINET:SERVER.EXE]
              [Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
              SERVER-CONFIG>DISABLE SMTP
              SERVER-CONFIG>RESTART
              SERVER-CONFIG>EXIT

          If the SMTP was previously enabled, you will also need
          to stop the MultiNet SMTP batch queue. For example:

              $ stop/queue smtp_alpha
                 _____________________
                 3.6.1.3  Disabling TCPware SMTP
          For TCPware, use the TCPware configuration utility
          to disable TCPware's SMTP server, if you installed
          TCPware-SMTP. For TCPware v3.0, type:

              $ @TCPWARE:CNFNET FULL SMTP

          For versions of TCPware prior to v3.0, type:

              $ @TCPIP_ROOT:CNFNET FULL SMTP

          When asked

              Enter the number of listening SMTP-VMS servers [1]:

          enter 0. When asked whether to restart SMTP, answer
          YES.
                 _____________________
                 3.6.1.4  Disabling UCX SMTP
          VMS/ULTRIX Connection (in versions 1.0 through 1.3B)
          does not include any native SMTP support.

          DEC TCP/IP Services for VMS v2.0 (formerly UCX) does
          include native SMTP support. To disable the UCX SMTP
          server under V2.0, perform the following:

          o  Disable the currently running SMTP service:

                                                              3-9

 


          Post-Installation Information





                  $ UCX DISABLE SERVICE SMTP

          o  Stop the UCX SMTP queues. For example:

                  $ STOP/QUEUE UCX_node_00
                  $ STOP/QUEUE UCX_node_01

          o  Modify the system startup (SYSTARTUP*.COM in
             SYS$MANAGER:) procedure to not invoke UCX$SMTP_
             STARTUP.COM.

          For DEC TCP/IP Services for VMS V3.0 and higher,
          perform the following:

          o  Run the UCX configuration procedure:

                  $ @SYS$MANAGER:UCX$CONFIG.COM

          o  Select ``Client components''.

          o  Select ``SMTP''.

          o  Answer ``Y'' to reconfigure SMTP.

          o  Answer ``N'' to disable SMTP.
                 _____________________
                 3.6.1.5  Disabling Wollongong PathWay SMTP
          To disable the SMTP server for Wollongong's PathWay,
          follow these steps:

          o  Edit the file TWG$TCP:[NETDIST.ETC]SERVERS.DAT.

          o  Find the server description for the SMTP service
             and place pound signs (#)  in front of each line,
             including the blank lines preceding and following
             the SMTP server description. This marks those lines
             as comments and they will be ignored by INET_SERVERS
             during its startup.

          o  If the INET_SERVERS process is running, kill it.

          o  Restart INET_SERVER by executing the following
             command:

                  $ @TWG$TCP:[NETDIST.MISC]INETSERV.COM

          3-10

 


                                    Post-Installation Information





          o  List the registered TCP/UDP services to make sure
             the SMTP service is not listed:

                  $ netstat -a

          o  You can now start the MX SMTP_SERVER process.

          To prevent the PathWay SMTP server from restarting
          on the next system boot, comment out the
          SMTP_INIT line in the PathWay startup file,
          TWG$TCP:[NETDIST.MISC]STARTINET.COM.

          This procedure should permanently disable the PathWay
          SMTP server. To reenable the PathWay SMTP server, undo
          all the edit changes, kill the MX SMTP_SERVER, kill
          the INET_SERVER, and restart the INET_SERVER.

          ___________________________

   3.6.2  Ensuring SMTP Server Restarts

          The MX SMTP Server process automatically exits when
          it detects the shutdown of the TCP/IP software. If
          you want to ensure that it starts back up again after
          restarting your TCP/IP software, you should create a
          command procedure for starting up TCP/IP:

              $ @vendor-supplied-startup
              $ IF F$TRNLNM ("MX_EXE") .NES. "" THEN @SYS$STARTUP:MX_STARTUP SMTP_SERVER

          Substitute the name of the vendor-supplied startup
          procedure for your TCP/IP package in the first line.

          ___________________________

   3.6.3  Enabling SMTP Kanji Support

          The SMTP interface contains code that will
          automatically convert JIS Kanji character encoding,
          used on the Japanese Internet, to DEC Kanji encoding
          (and vice-versa). The conversion is performed on
          the body of any message passing into or out of MX
          via SMTP. To enable this conversion, ensure that the
          following logical name definition is included in your

                                                             3-11

 


          Post-Installation Information





          SYSTARTUP_V5.COM prior to the startup of the MX SMTP
          support:

              $ DEFINE/SYSTEM MX_SMTP_KANJI_SUPPORT TRUE

          __________________________________________________________________

   3.7    Interfacing with UUCP

          If you have installed the support for DECUS UUCP, you
          must ensure that DECUS UUCP calls MX to deliver mail.

          If you are running DECUS UUCP v2.0 or higher, you must
          modify the UUCP configuration to define the logical
          UUCP_UUXQT_DCL_RMAIL_MX. The logical should be added
          to UUCP_CFG:CONTROL. as follows:

              !+
              !
              !       -- Make DECUS UUCP UUXQT_DCL procedure use MX to deliver mail.
              !
              !-
              UUCP_UUXQT_DCL_RMAIL_MX                 TRUE

          For versions of DECUS UUCP prior to v2.0, you must
          modify the UUCP command procedure UUCP_BIN:UUXQT_
          DCL.COM to accommodate the hook into MX. The section
          of the command file after the label DO_RMAIL should be
          modified as follows:

          The line that reads

              $        SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS)

          should be modified to include the privilege SYSLCK:

              $        SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS, SYSLCK)

          The corresponding line that turns off these privileges
          a few lines below should be similarly modified.

          The line that runs the mail message through the UUCP
          mailer:

              $        MAIL/PROTOCOL=UUCP_MAILSHR 'infile' "''addr'"

          3-12

 


                                    Post-Installation Information





          should be replaced by the following two lines:

              $        RMAIL := $MX_EXE:MX_RMAIL
              $        RMAIL 'infile' "''addr'"

          You may want to move the definition of the RMAIL
          symbol to the top of the command procedure.

          Note: UUCP must be started before MX in the system
          startup sequence.

          __________________________________________________________________

   3.8    SMTP Support for DECnet and X.25

          If you elected to install support for SMTP-over-DECnet
          or SMTP-over-X.25, you must take some additional steps
          to configure DECnet and MX.

          ___________________________

   3.8.1  Creating a DECnet Object for DECnet-SMTP

          You must create a DECnet object called DECSMTP for
          establishing SMTP-over-DECnet connections, both
          incoming and outgoing.

          If you intend to accept incoming SMTP-over-DECnet
          connections, you should establish an account (either
          your mailer account or a dedicated server account)
          for use with each DECnet object. See Section 1.5.1 for
          more information on the requirements for the DECnet
          object account.

          A DECnet object needs to be created to handle the
          incoming SMTP-over-DECnet connections and to map the
          DECSMTP object name to a DECnet object number. Choose
          an unused DECnet object number. To see what object
          numbers are currently in use, use the command:

              $ MCR NCP SHOW KNOWN OBJECT

                                                             3-13

 


          Post-Installation Information





          Assign the object name DECSMTP to an unused object
          number; the number used must be identical on all
          nodes on your network that use SMTP-over-DECnet (this
          example uses 254). In NCP, use these commands:

              NCP> PURGE OBJECT DECSMTP ALL
              NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY NONE FILE -
              _NCP>    MX_EXE:DNSMTP_SERVER.EXE USER server-acct PASSWORD some-password
              NCP> SET OBJECT DECSMTP ALL

          You do not need to specify the FILE, USER, or PASSWORD
          parameters if you do not intend to accept incoming
          SMTP connections over DECnet. Be sure that the
          password in the DECnet database matches the password
          you set for the server account in AUTHORIZE.

          Using Proxies

          Instead of storing the username and password for the
          server account in the DECnet database, you could
          grant access using DECnet proxies. Proxies give you
          more control over who on the network has access to
          the object, and eliminate the need for storing the
          password to the server account in the DECnet object
          database.

          Note: Using proxies allows the remote system access
          to all files the server account can access (by using
          regular DECnet file transfers with FAL). If you do not
          manage the remote system, it is recommended that you
          use DECnet objects instead of proxies.

          To enable proxy access to the DECSMTP object, use the
          following commands in NCP:

              NCP> PURGE OBJECT DECSMTP ALL
              NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY INCOMING FILE -
              _NCP>    MX_EXE:DNSMTP_SERVER.EXE
              NCP> SET OBJECT DECSMTP ALL

          3-14

 


                                    Post-Installation Information





          Then in AUTHORIZE, create proxy entries for the mailer
          accounts on the other systems on the network that will
          be sending you mail via SMTP-over-DECnet:

              UAF> ADD/PROXY remote::mailer server-acct/DEFAULT

          For remote::mailer substitute the DECnet node of the
          remote system and the username of the mailer account
          on that system. For server-acct substitute the name
          of the server account you set up for use with the
          DECnet-SMTP object.

          ___________________________

   3.8.2  Creating a DECnet Object for X.25-SMTP

          You must create a DECnet object called X25_SMTP for
          establishing SMTP-over-X.25 connections, both incoming
          and outgoing.

          If you intend to accept incoming SMTP-over-X.25
          connections, you should establish an account (either
          your mailer account or a dedicated server account)
          for use with each DECnet object. See Section 1.5.1 for
          more information on the requirements for the DECnet
          object account.

          A DECnet object needs to be created to handle the
          incoming SMTP-over-X.25 connections and to map the
          X25_SMTP object name to a DECnet object number. Choose
          an unused DECnet object number. To see what object
          numbers are currently in use, use the command:

              $ MCR NCP SHOW KNOWN OBJECT

          Assign the object name X25_SMTP to an unused object
          number; the number used must be identical on all
          nodes on your network that use SMTP-over-DECnet (this
          example uses 253). In NCP, use these commands:

              NCP> PURGE OBJECT X25_SMTP ALL
              NCP> DEFINE OBJECT X25_SMTP NUMBER 253 PROXY NONE FILE -
              _NCP>    MX_EXE:XSMTP_SERVER.EXE USER server-acct PASSWORD some-password
              NCP> SET OBJECT X25_SMTP ALL

                                                             3-15

 


          Post-Installation Information





          You do not need to specify the FILE, USER, or PASSWORD
          parameters if you do not intend to accept incoming
          SMTP connections over X.25. Be sure that the password
          in the DECnet database matches the password you set
          for the server account in AUTHORIZE.

          You must also add an X.25 "destination" to the P.S.I.
          database that maps to the DECnet object:

              NCP> DEFINE MODULE X25-SERVER DESTINATION X25_SMTP -
              _NCP>   OBJECT X25_SMTP PRIORITY 0 -
              _NCP>   CALL MASK  FFFFFFFFFFFFFFFFFFFFFFFF -
              _NCP>   CALL VALUE FF0000005832355F534D5450

              NCP> SET MODULE X25-SERVER DESTINATION X25_SMTP ALL

          __________________________________________________________________

   3.9    Customizing Mailing List and File Server Files

          The MX installation procedure provides three files,
          MLIST_ADD_MESSAGE.TXT, MLIST_REMOVE_MESSAGE.TXT, and
          MLIST_FORWARD_MESSAGE.TXT, for use with the mailing
          list processor, and a help file called FILESERV_
          HELP.TXT for use with a file server. If you intend
          to use the mailing list or file server features of
          MX, you should modify the contents of these files
          to reflect site dependencies. If you already had
          customized versions of these files, they are not
          purged; you should delete the new versions created
          by the installation procedure.

          Refer to Message Exchange Mailing List/File Server
          Guide for more information on setting up mailing
          lists.





          3-16

 


                                    Post-Installation Information




          __________________________________________________________________

   3.10   Setting Up MXALIAS

          MX includes a utility called MXALIAS which users
          can execute to define personal MX aliases for e-mail
          addresses. MXALIAS is fully documented in the Message
          Exchange User's Guide.

          In order to make MXALIAS accessible to users on the
          system, you should add a symbol like the following to
          your system login procedure (SYS$SYLOGIN) or to the
          user's LOGIN.COM:

              $ mxalias :== $mx_exe:mxalias.exe

          Alternatively, you can add a command to the DCLTABLES
          on your system that will invoke MXALIAS. In order to
          do so, create a file called MXALIAS.CLD containing the
          following lines:

              !
              !  CLD file for defining MXALIAS command as DCL command
              !
              !  To install for all users, modify the dev:[dir] strings below and
              !  execute the following commands:
              !
              !       $ SET COMMAND MXALIAS.CLD/TABLE=SYS$LIBRARY:DCLTABLES.EXE-
              !               /OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE
              !       $ INSTALL :== $INSTALL/COMMAND
              !       $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE
              !
              DEFINE VERB MXALIAS
                      IMAGE   MX_EXE:MXALIAS.EXE
                      CLIFLAGS(FOREIGN)

          The instructions in the file show you would enter
          the command in the system-wide DCLTABLES. This
          undocumented technique can be used for any program
          that must be run with a foreign symbol.

                                                             3-17

 


          Post-Installation Information





          MXALIAS includes its own on-line help. A brief
          description of MXALIAS that can be placed in the
          system help library can be found in MX_DIR: as
          MXALIAS_MAIN.HLP. To install it in the system-wide
          help library, execute the following command:

              $ LIBRARY/HELP/REPLACE SYS$HELP:HELPLIB.HLB MX_DIR:MXALIAS_MAIN

          Of course, any local help library may be specified
          instead of SYS$HELP:HELPLIB.HLB.

          __________________________________________________________________

   3.11   Starting MX

          Once you have created an MX configuration database and
          added the appropriate startup commands to your system
          startup, you are ready to start up the MX software.
          From the SYSTEM account, or other suitably privileged
          account, enter the command:

              $ @SYS$STARTUP:MX_STARTUP

          If you are using a separate mailer account, you
          instead use the command:

              $ SUBMIT/NOPRINT/USER=mailer/QUEUE=batchque SYS$STARTUP:MX_STARTUP

          If you are running MX Jnet support, you should also
          start (or stop and restart) Jnet.

          In a VMScluster environment, you should execute MX_
          STARTUP on each node in the cluster.

          __________________________________________________________________

   3.12   Registering Your Installation

          Message Exchange is freely distributable software, and
          no license is required to use it. Registration of your
          installation is at your discretion, and is used by the
          author only to determine the size of the MX user base
          and the future directions for the package.

          To register, simply send a note to the author with the
          following information:

             Installer's name

          3-18

 


                                    Post-Installation Information





             Company name and address
             System(s) on which MX is running
             Which network transports you're using
             Any comments and/or suggestions you might have

          You can send it electronically to:
          goathunter@MadGoat.COM

































                                                             3-19

 








          _______________________________________________________

   A      Sample MX Installations



          This appendix includes two samples of MX
          installations: one for a simple non-clustered system
          using SMTP-over-DECnet, and one for a clustered system
          using several different transports.

          __________________________________________________________________

   A.1    Non-Clustered Installation

          $|@SYS$UPDATE:VMSINSTAL MX042 MUA0:

           VAX/VMS Software Product Installation Procedure V5.5-2

          It is dd-MMM-yyyy at hh:mm.

          Enter a question mark (?) at any time for help.

          * Are you satisfied with the backup of your system disk [YES]? <RET>

          The following products will be processed:

           |MX V4.2
           |
           |              Beginning installation of MX V4.2 at hh:mm

          %VMSINSTAL-I-RESTORE, Restoring product save set A ...
          %VMSINSTAL-I-
          RELMOVED, Product's release notes have been moved to SYS$HELP.

           |               Message Exchange V4.2 Installation Procedure

                  Copyright  1993,1994,1995, MadGoat Software.  All Rights Reserved.

                       Redistribution for no commercial gain is permitted.

                                                              A-1

 


          Sample MX Installations





                       DEC, VMS, OpenVMS, VAX, AXP, DECnet, and VMScluster
                        are trademarks of Digital Equipment Corporation.
                         MultiNet is a registered trademark of TGV, Inc.
                        LISTSERV is a trademark of L-Soft International.
                     TCPware is a trademark of Process Software Corporation.
                   Jnet is a registered trademark of Wingra Technologies, Inc.
             WIN/TCP and Pathway are registered trademarks of The Wollongong Group, Inc.

          * Do you want to purge files replaced by this installation [YES]? <RET>

                                    Component Selection

              Select the MX components you wish to install from the menu below.
              An asterisk appears next to the packages that have already been
              selected.  You can remove a package from the list by selecting it
              again.  You may enter more than one selection by separating your
              choices with commas.

               1. [*] Base MX software (REQUIRED)
               2. [ ] NETLIB network support
               3. [ ] SMTP interface support
               4. [ ] Jnet interface support
               5. [ ] UUCP interface support
               6. [ ] SMTP-over-DECnet support
               7. [ ] SMTP-over-X.25 support
               8. [ ] Site-provided interface support
               9. [ ] Mailing List/File Server support
              10. [ ] LISTSERV interface support
              11. [ ] Documentation
              12. [ ] Example files and programs
              13. [ ] User-contributed files and programs

              14.     Exit

          *       Your choice [14]: 6,14 <RET>

              You have selected the following components:

                  Base MX software
                  SMTP-over-DECnet support

          * Is this correct [YES]? <RET>

              Now loading the Message Exchange base software.

          A-2

 


                                          Sample MX Installations





          %VMSINSTAL-I-RESTORE, Restoring product save set C ...

              Configuring Base MX Directories and Logicals
              --------------------------------------------

              MX places most of its files in a private directory structure.  This
              directory structure can be located on any disk, but the disk must either
              have disk quotas disabled or sufficient diskquota to hold all of the MX
              images, temporary files, and log files.

          * Where should the MX top directory be located? [SYS$SYSDEVICE:[MX]]: <RET>

              MX uses a file queue directory for storing mail messages.  This queue
              directory may be placed with the other MX directories, or may be placed
              on a different disk.  The disk on which the queue directory resides must
              also have quotas disabled or must have sufficient system quota to provide
              for a backlog of undelivered messages.

          * Where would you like the MX message queue? [SYS$SYSDEVICE:[MX.QUEUE]]: <RET>

              MX uses 10 subdirectories under the MX message queue directory for
              the actual storage of files.  Those directories will be created
              now, if necessary.

                              H O S T   N A M E   S E L E C T I O N

              There are two host names you must designate for the "local" host or
              cluster.

              MX Cluster Name
              ---------------

              This is a 1-to-6 character name that uniquely identifies the
              system (when standalone) or MX Cluster (when in a VMScluster).

              This name should generally be the DECnet node name (when
              standalone) or DECnet cluster alias (when in a VMScluster).

          * Enter the MX Cluster Name [MGRSTA]: <RET>

              MX Network Host Name
              --------------------

              This is a 1-to-
          255 character name that is your "official" host
              name for E-mail purposes.

                                                              A-3

 


          Sample MX Installations





              For Internet hosts, this should be your Internet domain name.
              (Example: myhost.mycompany.com)

              For BITNET hosts that are not Internet hosts, this should be
              your BITNET host name with ".BITNET" added to the end.
              (Example: MYORG.BITNET)

              For UUCP hosts that are not Internet hosts, this should either
              be your registered domain name (if you have one) or your UUCP
              node name with ".UUCP" added to the end.
              (Example: myhost.mycompany.com  -or-  myhost.UUCP)

          * Enter the MX network node name: mgrsta.mycompany.com <RET>

              MX Cluster Name:      MGRSTA
              Network Host Name:    mgrsta.mycompany.com

          * Is this correct [YES]? <RET>

              Auto-purging of FINished entries
              --------------------------------

              When an MX queue entry has been fully processed,  it is marked as
              being "finished" and  is  left in the queue for a period of time.
              The MX Router or MX FLQ Manager scans the file every  15 minutes,
              by default, and purges "FIN" entries.

              Many sites,  especially  high-
          volume  sites,  don't need  to keep
              finished entries in the queue for any length of time,  so MX V4.1
              now includes optional automatic purging of entries in the  queue.
              Enabling this  feature  causes  queue  entries and the associated
              files to be automatically deleted when they are marked "finished."

          *Do you wish to enable auto-
          purging of FINished entries [NO]: <RET>

              MX Queue Manager Process
              ------------------------

              The purging of processed entries from the MX message queue can be
              handled by the MX Router.  You can also choose to run a separate
              queue manager whose sole job is managing the message queue.  The
              advantage of running the MX FLQ Manager is that it frees the
              MX Router for routing messages.

          A-4

 


                                          Sample MX Installations





          *Do you wish to run the MX FLQ Manager as a separate process [YES]: <RET>

              Now linking MX base images.

          %MX-I-LINKING, Linking image MX_FLQ_SHR...
          %MX-I-LINKING, Linking image MX_MSG...
          %MX-I-LINKING, Linking image MX_SHR...
          %MX-I-LINKING, Linking image MX_MAILSHRP...
          %MX-I-LINKING, Linking image MX_MAILSHR...
          %MX-I-LINKING, Linking image MX_MAILSHRP (secure)...
          %MX-I-LINKING, Linking image MCP...
          %MX-I-LINKING, Linking image MX_ROUTER...
          %MX-I-LINKING, Linking image MX_LOCAL...
          %MX-I-LINKING, Linking image MAILQUEUE...
          %MX-I-LINKING, Linking image MLFAKE...
          %MX-I-LINKING, Linking image MXALIAS...
          %MX-I-LINKING, Linking image MX_DECODE...
          %MX-I-LINKING, Linking image MX_FLQ_MGR...

              Now providing the DECnet-SMTP support files and images.

          %VMSINSTAL-I-RESTORE, Restoring product save set G ...
          %MX-I-LINKING, Linking image MX_DNSMTP...
          %MX-I-LINKING, Linking image DNSMTP_SERVER...

              Please refer to the Installation Guide for information on setting
              up a DECnet object for SMTP-over-DECnet.

              MX installation procedure complete.

              Be sure to follow the post-
          installation instructions described in
              the MX Installation Guide.  This will minimally include editing
              SYSTARTUP_V5.COM to include the following command:

                         $ @SYS$STARTUP:MX_STARTUP

              If this is a new installation of MX, or you need to reconfigure
              MX before starting it up, you should ensure that all MX logical
              names are defined and shareable images are installed by executing

                         $ @SYS$STARTUP:MX_STARTUP LOGICALS

              immediately after VMSINSTAL completes.  If this is a new installation
              of MX, use the MXCONFIG procedure to build a base configuration:

                                                              A-5

 


          Sample MX Installations





                         $ @MX_DIR:MXCONFIG

          %VMSINSTAL-I-
          MOVEFILES, Files will now be moved to their target directories...

           |              Installation of MX V4.2 completed at hh:mm

                              VMSINSTAL procedure done at hh:mm

          __________________________________________________________________

   A.2    Clustered Installation

          $|@SYS$UPDATE:VMSINSTAL MX042 MUA0:

                      VAX/VMS Software Product Installation Procedure V5.5-
          2

          It is dd-MMM-yyyy at hh:mm.

          Enter a question mark (?) at any time for help.

          * Are you satisfied with the backup of your system disk [YES]? <RET>

          The following products will be processed:

           |MX V4.2
           |
           |                Beginning installation of MX V4.2 at hh:mm

          %VMSINSTAL-I-RESTORE, Restoring product save set A ...
          %VMSINSTAL-I-
          RELMOVED, Product's release notes have been moved to SYS$HELP.

           |               Message Exchange V4.2 Installation Procedure

                  Copyright  1993,1994,1995, MadGoat Software.  All Rights Reserved.

                       Redistribution for no commercial gain is permitted.

                       DEC, VMS, OpenVMS, VAX, AXP, DECnet, and VMScluster
                        are trademarks of Digital Equipment Corporation.
                         MultiNet is a registered trademark of TGV, Inc.
                        LISTSERV is a trademark of L-Soft International.
                     TCPware is a trademark of Process Software Corporation.
                   Jnet is a registered trademark of Wingra Technologies, Inc.
             WIN/TCP and Pathway are registered trademarks of The Wollongong Group, Inc.

          A-6

 


                                          Sample MX Installations





          * Do you want to purge files replaced by this installation [YES]? <RET>

              Mixed VAX and AXP VMSclusters
              -----------------------------

              This system is part of a VMScluster.  If this VMScluster includes
              both VAX and AXP systems that will share the MX directories and
              configuration files, it will be necessary to install MX twice:
              once on a VAX system and once on an AXP system.  It is only
              necessary to install the FULL MX kit on one type of system
              (VAX or AXP).

              The dual installation is required because the MX images are
              linked during installation.  However, when installing MX on the
              second system, you may elect to install only the executables to
              avoid the need to reconfigure MX.

              The full MX installation MUST be installed from one of the systems
              for MX to work.  During that installation, information must be
              supplied pertaining to which nodes will run which agents, etc.

          *Does this VMScluster include both VAX and AXP systems [NO]? YES<RET>
          *Will the VAX and AXP systems share a common MX directory [YES]? <RET>
          *|as MX V4.2 already been installed on an AXP system in this cluster [NO]? <RET>

                                    Component Selection

              Select the MX components you wish to install from the menu below.
              An asterisk appears next to the packages that have already been
              selected.  You can remove a package from the list by selecting it
              again.  You may enter more than one selection by separating your
              choices with commas.








                                                              A-7

 


          Sample MX Installations





               1. [*] Base MX software (REQUIRED)
               2. [ ] NETLIB network support
               3. [ ] SMTP interface support
               4. [ ] Jnet interface support
               5. [ ] UUCP interface support
               6. [ ] SMTP-over-DECnet support
               7. [ ] SMTP-over-X.25 support
               8. [ ] Site-provided interface support
               9. [ ] Mailing List/File Server support
              10. [ ] LISTSERV interface support
              11. [ ] Documentation
              12. [ ] Example files and programs
              13. [ ] User-contributed files and programs

              14.     Exit

          *       Your choice [14]: 2,3,4,6,9,11 <RET>
                                    Component Selection

              Select the MX components you wish to install from the menu below.
              An asterisk appears next to the packages that have already been
              selected.  You can remove a package from the list by selecting it
              again.  You may enter more than one selection by separating your
              choices with commas.

               1. [*] Base MX software (REQUIRED)
               2. [*] NETLIB network support
               3. [*] SMTP interface support
               4. [*] Jnet interface support
               5. [ ] UUCP interface support
               6. [*] SMTP-over-DECnet support
               7. [ ] SMTP-over-X.25 support
               8. [ ] Site-provided interface support
               9. [*] Mailing List/File Server support
              10. [ ] LISTSERV interface support
              11. [*] Documentation
              12. [ ] Example files and programs
              13. [ ] User-contributed files and programs

              14.     Exit

          *       Your choice [14]: <RET>

          A-8

 


                                          Sample MX Installations





              You have selected the following components:

                  Base MX software
                  NETLIB network support
                  SMTP interface support
                  Jnet interface support
                  SMTP-over-DECnet support
                  Mailing List/File Server support
                  Documentation

          * Is this correct [YES]? <RET>

              Configuring Base MX Directories and Logicals
              --------------------------------------------

              MX places most of its files in a private directory structure.  This
              directory structure can be located on any disk, but the disk must either
              have disk quotas disabled or sufficient diskquota to hold all of the MX
              images, temporary files, and log files.

          * Where should the MX top directory be located? [SYS$SYSDEVICE:[MX]]: <RET>

              MX uses a file queue directory for storing mail messages.  This queue
              directory may be placed with the other MX directories, or may be placed
              on a different disk.  The disk on which the queue directory resides must
              also have quotas disabled or must have sufficient system quota to provide
              for a backlog of undelivered messages.

          * Where would you like the MX message queue? [SYS$SYSDEVICE:[MX.QUEUE]]: <RET>

              MX uses 10 subdirectories under the MX message queue directory for
              the actual storage of files.  Those directories will be created
              now, if necessary.

                              H O S T   N A M E   S E L E C T I O N

              There are two host names you must designate for the "local" host or
              cluster.

              MX Cluster Name
              ---------------

              This is a 1-to-6 character name that uniquely identifies the
              system (when standalone) or MX Cluster (when in a VMScluster).

                                                              A-9

 


          Sample MX Installations





              This name should generally be the DECnet node name (when
              standalone) or DECnet cluster alias (when in a VMScluster).

          * Enter the MX Cluster Name [MYCLUS]: <RET>

              MX Network Host Name
              --------------------

              This is a 1-to-
          255 character name that is your "official" host
              name for E-mail purposes.

              For Internet hosts, this should be your Internet domain name.
              (Example: myhost.mycompany.com)

              For BITNET hosts that are not Internet hosts, this should be
              your BITNET host name with ".BITNET" added to the end.
              (Example: MYORG.BITNET)

              For UUCP hosts that are not Internet hosts, this should either
              be your registered domain name (if you have one) or your UUCP
              node name with ".UUCP" added to the end.
              (Example: myhost.mycompany.com  -or-  myhost.UUCP)

          * Enter the MX network node name: myhost.mycompany.com <RET>

              MX Cluster Name:      MYCLUS
              Network Host Name:    myhost.mycompany.com

          * Is this correct [YES]? <RET>

              Auto-purging of FINished entries
              --------------------------------

              When an MX queue entry has been fully processed,  it is marked as
              being "finished" and  is  left in the queue for a period of time.
              The MX Router or MX FLQ Manager scans the file every  15 minutes,
              by default, and purges "FIN" entries.

              Many sites,  especially  high-
          volume  sites,  don't need  to keep
              finished entries in the queue for any length of time,  so MX V4.1
              now includes optional automatic purging of entries in the  queue.
              Enabling this  feature  causes  queue  entries and the associated
              files to be automatically deleted when they are marked "finished."

          A-10

 


                                          Sample MX Installations





          *Do you wish to enable auto-
          purging of FINished entries [NO]: <RET>

              MX Queue Manager Process
              ------------------------

              The purging of processed entries from the MX message queue can be
              handled by the MX Router.  You can also choose to run a separate
              queue manager whose sole job is managing the message queue.  The
              advantage of running the MX FLQ Manager is that it frees the
              MX Router for routing messages.

          *Do you wish to run the MX FLQ Manager as a separate process [YES]: <RET>

              Specifying VMScluster Node Names
              --------------------------------

              This system is part of a VMScluster.  For each component you have
              selected that includes a process to be run, you will be asked to
              select which nodes in the cluster should run the component's
              process.  You may run each process on any or all of the nodes
              in the cluster, under the MX Cluster guidelines outlined in the
              Installation Guide.

              When specifying node names, use a system's cluster (SCS) node name.
              You may specify more than one node name by separating them with
              commas.

              You may specify an asterisk ("*") as the node name if you want to
              execute the process on all nodes in the cluster

          * Enter the node(s) that will run the MX FLQ Manager: NODE1 <RET>

          * Enter the node(s) that will run the Router: NODE1,NODE2 <RET>

              Specifying the Number of MX Agent Processes
              -------------------------------------------

              For some components, you will be asked to enter the number of
              processes to be run on each specified node.  Multiple processes
              can increase the total throughput of messages processed by MX.

                                                             A-11

 


          Sample MX Installations





              Valid numbers range from 1 to 10.  These values can be changed
              at any time after the installation by modifying the file
              MX_DIR:MX_STARTUP_INFO.DAT.

          * Number of ROUTER processes to run on node NODE1 [1]: <RET>
          * Number of ROUTER processes to run on node NODE2 [1]: <RET>

          * Enter the node(s) that will run the Local delivery agent [NODE1,NODE2]: <RET>
          * Number of LOCAL processes to run on node NODE1 [1]: <RET>
          * Number of LOCAL processes to run on node NODE2 [1]: <RET>

          * Enter the node(s) that will run the SMTP delivery agent: NODE1 <RET>
          * Number of SMTP processes to run on node NODE1 [1]: 8<RET>

          * Enter the node(s) that will run the SMTP server: NODE1 <RET>

          * Enter the node(s) that will run the Jnet interface: NODE2 <RET>
          * Number of JNET processes to run on node NODE2 [1]: <RET>

          * Enter the node(s) that will run the DECnet-
          SMTP delivery agent: NODE1,NODE2 <RET>
          * Number of DNSMTP processes to run on node NODE1 [1]: 2<RET>
          * Number of DNSMTP processes to run on node NODE2 [1]: 2<RET>

          * Enter the node(s) that will run the Mailing List/File Server: NODE1,NODE2 <RET>
          * Number of MLF processes to run on node NODE1 [1]: <RET>
          * Number of MLF processes to run on node NODE2 [1]: <RET>

              Now installing NETLIB library for TCP/IP support.

          %VMSINSTAL-I-RESTORE, Restoring product save set B ...
          %MX-I-NETLRNOT, Release notes for NETLIB V1.5 have been copied to SYS$HELP.

                                 TCP/IP Support Selection

              Select the NETLIB TCP/IP support you wish to install from the
              menu below.  An asterisk appears next to the packages that have
              already been selected.  You can remove a package from the list
              by selecting it again.  You may enter more than one selection
              by separating your choices with commas.

          A-12

 


                                          Sample MX Installations





               1. [*] CMU-Tek TCP/IP V6.4
               2. [ ] CMU-Tek TCP/IP V6.5 or later
               3. [ ] DEC VMS/ULTRIX Connection (UCX) V1.2
               4. [*] DEC UCX V1.3 or TCP/IP Services for VMS V2.0 or later
               5. [ ] TGV MultiNet V2.2 or later
               6. [ ] PSC TCPware

               7. [ ] TWG WIN/TCP or PathWay Access for VMS

               8.     Exit

          *       Your choice [8]: <RET>

              You have selected the following TCP/IP support:

                  CMU-Tek TCP/IP V6.4
                  DEC UCX V1.3 or TCP/IP Services for VMS V2.0 or later

          * Is this correct [YES]? <RET>

              You have selected support for more than one TCP/IP package.
              You must now select which is to be used by default on the
              current system.

               1. CMU-Tek TCP/IP V6.4
               4. DEC UCX V1.3 or TCP/IP Services for VMS V2.0 or later

          *       Your choice: 4 <RET>

              Default TCP/IP transport will be: DEC UCX V1.3 or TCP/IP Services for VMS V2.0 or later

              Choosing the NETLIB Directory

              The NETLIB libraries may go in either SYS$COMMON:[SYSLIB]
              or some other directory you specify.

          * Where should the NETLIB libraries be placed [MX_
          ROOT:[EXE]]: <RET>
          %VMSINSTAL-
          I-SYSDIR, This product creates system disk directory  MX_

                                                             A-13

 


          Sample MX Installations





          ROOT:[EXE].
          %CREATE-I-EXISTS, MX_ROOT:[EXE] already exists
          %NETLIB-I-LINKING, Linking image NETLIB_SHRXFR...
          %NETLIB-I-LINKING, Linking image NETLIB_CMU064_SHR...
          %NETLIB-I-LINKING, Linking image NETLIB_UCX_SHR...

              The installation will continue for another 5 to 45 minutes,
              depending on your CPU type, distribution media, etc.  No
              further input is required.

              Now loading the Message Exchange base software.

          %VMSINSTAL-I-RESTORE, Restoring product save set C ...
          %MX-I-LINKING, Linking image MX_FLQ_SHR...
          %MX-I-LINKING, Linking image MX_MSG...
          %MX-I-LINKING, Linking image MX_SHR...
          %MX-I-LINKING, Linking image MX_MAILSHRP...
          %MX-I-LINKING, Linking image MX_MAILSHR...
          %MX-I-LINKING, Linking image MX_MAILSHRP (secure)...
          %MX-I-LINKING, Linking image MCP...
          %MX-I-LINKING, Linking image MX_ROUTER...
          %MX-I-LINKING, Linking image MX_LOCAL...
          %MX-I-LINKING, Linking image MAILQUEUE...
          %MX-I-LINKING, Linking image MLFAKE...
          %MX-I-LINKING, Linking image MXALIAS...
          %MX-I-LINKING, Linking image MX_DECODE...
          %MX-I-LINKING, Linking image MX_FLQ_MGR...

              Now providing the SMTP support files and images.

          %VMSINSTAL-I-RESTORE, Restoring product save set D ...
          %MX-I-LINKING, Linking image MX_SMTP...
          %MX-I-LINKING, Linking image SMTP_SERVER...
          %MX-I-LINKING, Linking image DOMAIN_EXPANSION...

              Now providing the Jnet support files and images.

          %VMSINSTAL-I-RESTORE, Restoring product save set E ...
          %MX-I-LINKING, Linking image MX_JNET...
          %MX-I-LINKING, Linking image MX_MFSDISP...

          A-14

 


                                          Sample MX Installations





              Remember that Jnet must be started AFTER MX is started.  To start the
              MX/Jnet Interface, include the following commands in the JANSITE or
              JANSITECOMMON procedures for your node:

                  $ DEFINE/SYS/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISP
               $ SUBMIT/NOPRINT/QUEUE=node_queue/USER=maileracct -
                           SYS$STARTUP:MX_STARTUP/PARAM=JNET

              where "node_
          queue" is the name of a batch queue that executes on the
              node where you are running Jnet and "maileracct" is the username of
              your mailer account.  For more information, see the Installation Guide.

              Now providing the DECnet-SMTP support files and images.

          %VMSINSTAL-I-RESTORE, Restoring product save set G ...
          %MX-I-LINKING, Linking image MX_DNSMTP...
          %MX-I-LINKING, Linking image DNSMTP_SERVER...

              Please refer to the Installation Guide for information on setting
              up a DECnet object for SMTP-over-DECnet.

              Now installing the Mailing List/File Server support files and images.

          %VMSINSTAL-I-RESTORE, Restoring product save set J ...
          %MX-I-LINKING, Linking image MX_MLF...

              Now providing MX documentation to directory MX_ROOT:[DOC].

          %VMSINSTAL-I-RESTORE, Restoring product save set K ...

              MX installation procedure complete.

              Be sure to follow the post-
          installation instructions described in
              the MX Installation Guide.  This will minimally include editing
              SYSTARTUP_V5.COM to include the following command:

                         $ @SYS$STARTUP:MX_STARTUP

              If this is a new installation of MX, or you need to reconfigure
              MX before starting it up, you should ensure that all MX logical
              names are defined and shareable images are installed by executing

                         $ @SYS$STARTUP:MX_STARTUP LOGICALS

                                                             A-15

 


          Sample MX Installations





              immediately after VMSINSTAL completes.  If this is a new installation
              of MX, use the MXCONFIG procedure to build a base configuration:

                         $ @MX_DIR:MXCONFIG

          %VMSINSTAL-I-
          MOVEFILES, Files will now be moved to their target directories...

           |                Installation of MX V4.2 completed at hh:mm

                                VMSINSTAL procedure done at hh:mm





























          A-16

 








          _______________________________________________________

   B      Contents of Distribution Kit



          MX is provided in a VMSINSTALlable distribution kit
          consisting of twelve save sets. Each save set is
          briefly described in Table B-1.

          Table_B-1__MX_installation_kit_save_sets_______________

          Save_Set___Contents____________________________________

          MX042.A    The KITINSTAL command procedure and its
                     supporting files, object code common to all
                     MX components.
           |
          M|042.B    NETLIB VAX installation kit.
           |
          M|042.C    NETLIB Alpha installation kit.
           |
          M|042.D    MX base software.
           |
          M|042.E    SMTP interface support.
           |
          M|042.F    Jnet interface support.
           |
          M|042.G    UUCP interface support.
           |
          M|042.H    SMTP-over-DECnet support.
           |
          M|042.I    SMTP-over-X.25 support.
           |
          M|042.J    SITE interface support.
           |
          M|042.K    Mailing List/File Server support.
           |
          M|042.L    LISTSERV interface support.
           |
          M|042.M    Documentation files, in PostScript,
           |         Bookreader, and plain ASCII formats.
           |
          M|042.N    Examples.
           |
          M|042.O____Contributed_software_and_files._____________

                                                              B-1

 








          _______________________________________________________

   C      Files Created During Installation



          The files in Table C-1 are created during the
          installation of the MX software. For an inventory
          of the MX user-contributed files and software, see
          the file 00README.TXT in save set MX042.M, or in
          directory MX_ROOT:[CONTRIB], if the contributed files
          are installed.

          The following notes are referenced in Table C-1:

          1  Only if ML/FS support is installed.

          2  Only if Documentation is installed.

          3  Only if Examples are installed.

          4  Only if SMTP-over-DECnet is installed.

          5  Only if SMTP support is installed.

          6  Only if Jnet support is installed.

          7  Only if UUCP support is installed.

          8  Only if SITE support is installed.

          9  Only if NETLIB support is installed.

         10  Only if SMTP-over-X.25 is installed.

         11  Only if LISTSERV support is installed.




                                                              C-1

 


          Files Created During Installation





          Table C-1  Message Exchange files created during
          ___________installation________________________________

          File_name___________________Description________________

          __________________Files_in_MX_FLQ_DIR:_________________

          MX_SYSTEM_QUEUE.FLQ_CTL     System queue sequential
                                      file

          _______________________________________________________
          _______________Files_in_MX_ROOT:[000000]_______________

          MXALIAS_MAIN.HLP            Top-level MXALIAS help file
                                      for HELPLIB.HLB

          MX_ALIAS_HELPLIB.HLB        Help library for MXALIAS

          MX_MCP_HELPLIB.HLB          Help library for MCP

          MLF_CONFIG.COM              ML/FS configuration
                                      procedure (Note 1)

          MXCONFIG.COM                MX configuration creation
                                      procedure

          MX_LOGICALS.DAT             Logical name definitions
                                      used by MX___STARTUP.COM

          MX_STARTUP_INFO.DAT         Describes which MX
                                      processes get started









          C-2

 


                                Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          _______________________________________________________

          ____________Files_in_MX_ROOT:[DOC]_(Note_2)____________

          MX_INSTALL_                 Installation guide
          GUIDE.DECW$BOOK             (Bookreader)

          MX_INSTALL_GUIDE.PS         Installation guide
                                      (PostScript)

          MX_INSTALL_GUIDE.TXT        Installation guide (ASCII)

          MX_LIBRARY.DECW$BOOKSHELF   Library file for MX
                                      Bookreader documents

          MX_MGMT_GUIDE.DECW$BOOK     Management guide
                                      (Bookreader)

          MX_MGMT_GUIDE.PS            Management guide
                                      (PostScript)

          MX_MGMT_GUIDE.TXT           Management guide (ASCII)

          MX_MLF_GUIDE.DECW$BOOK      Mailing List/File Server
                                      guide (Bookreader)

          MX_MLF_GUIDE.PS             Mailing List/File Server
                                      guide (PostScript)

          MX_MLF_GUIDE.TXT            Mailing List/File Server
                                      guide (ASCII)

          MX.DECW$BOOKSHELF           Bookshelf file for MX
                                      Bookreader documents

          MX_PROG_GUIDE.DECW$BOOK     Programmer's guide
                                      (Bookreader)

          MX_PROG_GUIDE.PS            Programmer's guide
                                      (PostScript)

          MX_PROG_GUIDE.TXT           Programmer's guide (ASCII)

          MX_USER_GUIDE.DECW$BOOK     User guide (Bookreader)

          MX_USER_GUIDE.PS            User guide (PostScript)

          MX_USER_GUIDE.TXT           User guide (ASCII)

                                                              C-3

 


          Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          File_name___________________Description________________

          __________Files_in_MX_ROOT:[EXAMPLES]_(Note_3)_________

          ADDRESS_REWRITER.C          Header and envelope
                                      rewriter routine template

          DOM_EXPANSION_CMU.B32       Domain name expansion
                                      routine template

          DOM_EXPANSION_UCX.B32       Domain name expansion
                                      routine template

          MX_HDR.H                    Include file for ADDRESS_
                                      REWRITER.C

          NAME_CONVERSION.B32         Alias conversion routine
                                      template

          NAME_CONVERSION.C           Alias conversion routine
                                      template
















          C-4

 


                                Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          _______________________________________________________

          ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___

          DNSMTP_SERVER.EXE           SMTP-over-DECnet receiver
                                      module (Note 4)

          DOMAIN_EXPANSION.EXE        Domain name expander (Note
                                      5)

          MAILQUEUE.EXE               Program for listing delayed
                                      messages in queue

          MCP.EXE                     MX Control Program

          MLFAKE.EXE                  Utility for faking messages
                                      to mailing list servers

          MXALIAS.EXE                 Utility for defining MX
                                      aliases

          MX_DECODE.EXE               Utility to decode BASE64
                                      mail messages














                                                              C-5

 


          Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          File_name___________________Description________________

          ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___

          MX_DNSMTP.EXE               SMTP-over-DECnet delivery
                                      module (Note 4)

          MX_FLQ_MGR.EXE              MX FLQ Manager

          MX_FLQ_SHR.EXE              Shareable image
                                      implementing file queues

          MX_JNET.EXE                 MX Jnet interface module
                                      (Note 6)

          MX_JNET.COM                 Command procedure used by
                                      Jnet interface (Note 6)

          MX_LOCAL.EXE                MX Local delivery module

          MX_LSV.EXE                  MX LISTSERV interface
                                      module (Note 11)

          MX_MAILSHR.EXE              VMS MAIL foreign protocol
                                      interface












          C-6

 


                                Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          File_name___________________Description________________

          ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___

          MX_MAILSHRP.EXE             Service routines for
                                      foreign protocol interface

          MX_MFSDISP.EXE              Jnet Mail/File Dispatcher
                                      for MX (Note 6)

          MX_MLF.EXE                  Mailing list/file server
                                      module (Note 1)

          MX_MSG.EXE                  Messages file

          MX_RMAIL.EXE                UUCP mail entry interface
                                      (Note 7)

          MX_ROUTER.EXE               MX Router module

          MX_SHR.EXE                  MX common routines
                                      shareable library















                                                              C-7

 


          Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          File_name___________________Description________________

          ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___

          MX_SITE.COM                 Command procedure used by
                                      site-spec interface (Note
                                      8)

          MX_SITE.EXE                 Site-spec delivery agent
                                      (Note 8)

          MX_SITE_IN.COM              Site-spec message entry
                                      program (Note 8)

          MX_SMTP.EXE                 SMTP outbound delivery
                                      module (Note 5)

          MX_START.COM                Command procedure for
                                      starting MX components

          MX_UUCP.COM                 Used by UUCP delivery agent
                                      (Note 7)

          MX_UUCP.EXE                 UUCP delivery agent (Note
                                      7)

          MX_XSMTP.EXE                SMTP-over-X.25 delivery
                                      agent (Note 10)

          MX___STARTUP.COM            Master startup procedure
                                      for MX.

          SMTP_SERVER.EXE             SMTP inbound receiver
                                      module (Note 5)

          XSMTP_SERVER.EXE            SMTP-over-X.25 inbound
                                      receiver module (Note 10)

          _______________________________________________________
          ____________Files_in_MX_ROOT:[MLF]_(Note_1)____________

          FILESERV_HELP.TXT           Help text for use with file
                                      server

          C-8

 


                                Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          File_name___________________Description________________

          _____Files_in_MX_ROOT:[MLF.MAILING_LISTS]_(Note_1)_____

          MLIST_ADD_                  Template for mailing list
          MESSAGE.TEMPLATE            add message

          MLIST_ADD_MESSAGE.TXT       Template for mailing list
                                      add message

          MLIST_FORWARD_              Template for forwarded-to-
          MESSAGE.TEMPLATE            list-owner message

          MLIST_FORWARD_MESSAGE.TXT   Template for forwarded-to-
                                      list-owner message

          MLIST_HELP.TXT              Help file for mailing list
                                      processor

          MLIST_REMOVE_               Template for mailing list
          MESSAGE.TEMPLATE            removal message

          MLIST_REMOVE_MESSAGE.TXT    Template for mailing list
                                      removal message

          _______________________________________________________
          _____________Files_in_NETLIB_DIR:_(Note_9)_____________

          NETLIBDEF.L32               BLISS library file for
                                      NETLIB programming

          NETLIBDEF.R32               BLISS REQUIRE file for
                                      NETLIB programming

          NETLIB_SHRXFR.EXE           NETLIB transport-
                                      independent library

          NETLIB_xxx_SHR.EXE          NETLIB transport-specific
                                      library (one per transport)

          _______________________________________________________
          ______________Files_in_SYS$COMMON:[SYSHLP]_____________

          MXvvn.RELEASE_NOTES         Release notes for MX

          NETLIBvvn.RELEASE_NOTES     Release notes for NETLIB

                                                              C-9

 


          Files Created During Installation





          Table C-1 (Cont.)  Message Exchange files created
          ___________________during_installation_________________

          File_name___________________Description________________

          ___________Files_in_SYS$COMMON:[SYS$STARTUP]___________

          MX_STARTUP.COM              Startup procedure for MX

          NETLIB_STARTUP.COM          Startup procedure for
          ____________________________NETLIB_(Note_2)____________





























          C-10
