














                    Message Router VMSmail Gateway


                          Installation Guide







                             Version 3.1


















                    digital equipment corporation,
                        maynard, massachusetts




AA-KR24B-TE
First Printing, September 1988

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation.  Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.

The software described in this document is furnished under a license
and may be used and copied only in accordance with the terms of such
license.

Digital Equipment Corporation assumes no responsibility for the use or
reliability of its software on equipment that is not supplied by
DIGITAL or its affiliated companies.



Copyright (c) 1988 Digital Equipment Corporation.  All rights
reserved.



Please fill in and send us the prepaid reader's comments at the end of
this book.  It will help us to keep improving our documentation.





The following are trademarks of Digital Equipment Corporation:


--------------- TM
|d|i|g|i|t|a|l|
_______________         DNA                     Rainbow
ALL-IN-1                LQP                     RSTS
DEC                     MAILbus                 RSX
DECmate                 MASSBUS                 ULTRIX
DECnet                  Message Router          UNIBUS
DECset                  MicroPDP                VAX
DECstart                MicroVAX                VAXmate
DECUS                   MicroVMS                VMS
DECSYSTEM-10            OSAK                    VOTS
DECSYSTEM-20            PDP                     WPS-PLUS
DIBOL                   Q-BUS                   WPS-8





                                  ii







                                   CONTENTS



                Preface


CHAPTER 1       Introduction

        1.1     Introduction to the Gateway  . . . . . . . . . . . 1-1
        1.2     Introduction to Installation and Configuration . . 1-1
        1.2.1     The Installation Procedure . . . . . . . . . . . 1-2
        1.2.2     The Configuration Procedure  . . . . . . . . . . 1-2
        1.3     Error Handling   . . . . . . . . . . . . . . . . . 1-3


CHAPTER 2       Preparing to Install the Gateway

        2.1     Preparation Checklist  . . . . . . . . . . . . . . 2-1
        2.2     Prerequisite Software and Hardware . . . . . . . . 2-2
        2.3     Preparing Your System for Installation . . . . . . 2-3
        2.4     Preparing for an Upgrade Installation from Version 
                2.0 or 2.1 . . . . . . . . . . . . . . . . . . . . 2-6
        2.5     Preparing for an Upgrade Installation from Version 
                3.0  . . . . . . . . . . . . . . . . . . . . . . . 2-8
        2.6     Preparing to Re-install Version 3.1  . . . . . . . 2-9
        2.7     Preparing to Install the Gateway on a VAXcluster 
                or Local Area VAXcluster . . . . . . . . . . . .  2-10
        2.7.1     Installing the Gateway on a Homogeneous Cluster 2-11
        2.7.2     Installing the Gateway on a Heterogeneous 
                  Cluster  . . . . . . . . . . . . . . . . . . .  2-11
        2.8     Preparing MicroVMS for a Gateway Installation 
                Procedure  . . . . . . . . . . . . . . . . . . .  2-12
        2.9     Preparing VMS Version 5.0 for a Gateway 
                Installation Procedure . . . . . . . . . . . . .  2-14
        2.9.1     Preparing to Use the VMS Tailoring Utility . .  2-15
        2.9.2     Using the VMS Tailoring Utility  . . . . . . .  2-16


CHAPTER 3       Installing the Gateway

        3.1     Overview of VMSINSTAL  . . . . . . . . . . . . . . 3-1
        3.2     Installation Procedure . . . . . . . . . . . . . . 3-1
        3.3     Running the IVP  . . . . . . . . . . . . . . . . . 3-9
        3.4     Completing the Installation  . . . . . . . . . .  3-11
        3.5     Location of the Gateway Software . . . . . . . .  .3-13
        3.6     After a MicroVAX Installation on MicroVMS  . . .  3-15


                                 iii




        3.7     After a MicroVAX Installation on VMS Version 5.0  3-16


APPENDIX A      Distribution Media


APPENDIX B      Sample Installation Procedure on VMS Version 4.6, 4.7,
                or MicroVMS


APPENDIX C      Sample Installation Procedure on VMS Version 5.0


INDEX


FIGURES

        3-1     Directory Structure of the MRGATE Account  . . .  3-13


TABLES

        3-1     Location of Gateway Files  . . . . . . . . . . .  3-14




























                                  iv














                               Preface



Purpose of This Book

This book describes how to install the VAX Message Router VMSmail
Gateway Version 3.1.  It also describes how to upgrade from Version
2.0, 2.1, or 3.0 of the Gateway.



Intended Audience

This book is for the person responsible for installing and maintaining
the Message Router VMSmail Gateway.  That person should be familiar
with operating system management and DECnet, and have access to the
SYSTEM account on the VMS or MicroVMS system.



How This Book Is Organized

This book contains three chapters and three appendixes:

      o  Chapter 1 explains briefly what the Gateway does and
         introduces the installation and configuration procedures.

      o  Chapter 2 describes the preparation required before
         installing the Gateway.

      o  Chapter 3 describes the installation procedure step by step.
         It also describes the installation verification procedure
         (IVP).

      o  Appendix A contains a list of the files in the Message Router
         VMSmail Gateway distribution kit.





                                  v

Preface


      o  Appendix B contains a log of a typical Gateway installation
         on VMS Version 4.6 or 4.7, or on MicroVMS.

      o  Appendix C contains a log of a typical Gateway installation
         on VMS Version 5.0.




How to Use this Book

Read Chapters 1 and 2 to understand the preparations required before
installation.

Read Chapter 3 for a step-by-step description of the interactive
installation procedure.

Refer to Appendix A for a list of the files supplied as part of the
Message Router VMSmail Gateway distribution kit.

Refer to Appendix B for an example of a successful Gateway
installation on VMS 4.6 or 4.7, or on MicroVMS.

Refer to Appendix C for an example of a successful Gateway
installation on VMS Version 5.0.



Related Documents

Before installing the Gateway, as described in Chapter 4, you must
install Message Router Version 3.1 as described in the Message Router
Installation Guide.

You may also need to refer to:

VAX/VMS Command Language

Guide to VAX/VMS Software Installation

MicroVMS User's Manual

Message Router VMSmail Gateway Management Guide

Message Router VMSmail Gateway User's Guide

Introduction to Message Router





                                  vi

                                                               Preface


Message Router Configuration Guide

Message Router Management Reference Manual

VAX/VMS License Management Utility Manual

Figure 1 shows how to use the books supplied with this kit.













































                                 vii

Preface


Figure 1:  Message Router VMSmail Gateway Documentation Map





              ------------------------------------------
              |Read the Introduction to Message Router.|
              ------------------------------------------
                                   |
                                   |
                                   V
        -----------------------------------------------------
        | Read the release notes for Message Router and      |
        | the Message Router VMSmail Gateway.                |
        | See the Message Router Installation Guide and      |
        | the Message Router VMSmail Gateway Installation    | 
        | Guide for details of how to print them.            |
        ------------------------------------------------------
                                   |
                                   |
                                   V
           ------------------------------------------------
           |Read the Message Router Installation Guide for|
           |  details of how to install Message Router.   |
           ------------------------------------------------
                                   |
                                   |
                                   V
                          Do you want to install    No
                          Message Router VMSmail -------------
                                Gateway?                      |
                                   |                          |
                                   V Yes                      |
           ------------------------------------------------   |
           | Read the Message Router VMSmail Gateway      |   |
           | Installation Guide for details of how to     |   |
           | to install Message Router VMSmail Gateway.   |   |
           ------------------------------------------------   |
                                   |                          |
                                   |                          |
                                   |<-------------------------- 
                                   |  
                                   V
           ------------------------------------------------- 
           |Read the Message Router Configuration Guide for|
           |  details of how to configure Message Router.  |
           -------------------------------------------------
                                   |
                                   V


                                 viii

                                                               Preface



                               |
                               V
                      Have you installed    No
                      the Gateway?  ----------- 
                               |              |
                               |Yes           |
                               |              |                No
                               |       Do you want to install------ 
                               |           the Gateway?            |
             <-----------------               |                    |
            |                                 | Yes                |
            |                                 |                    |
            |                                 V                    |
            |   ------------------------------------------------   |  
            |   | Read the Message Router VMSmail Gateway      |   |
            |   | Installation Guide for details of how to     |   |
            |   | to install Message Router VMSmail Gateway.   |   |
            |   ------------------------------------------------   |
            |                                 |                    | 
            |<--------------------------------                     |
            |                                                      |
            V                                                      |
  -------------------------------------------                      |
  | Read the Message Router VMSmail Gateway  |                     |
  | Management Guide for details of how to   |                     |
  | configure MRGATE.                        |                     |
  --------------------------------------------                     |
            |                                                      |
            |                                                      |
            V                                                      |
   -----------------------------------------------------           |
   | Read the Message Router VMSmail Gateway Management |          | 
   | Guide for details of how to manage MRGATE          |          |
   -----------------------------------------------------           |
            |                                                      |
            |<-----------------------------------------------------
            V                              
   ------------------------------------------------------
   |    Read the Message Router Management Guide for    |
   |      details of how to manage Message Router.      |
   |   Refer to the Message Router Management Action    |
   |    Procedures and the Message Router Management    |
   |Reference Manual for further management information.|
   ------------------------------------------------------
                                                         






                                 ix

Preface


Conventions

The following conventions are used in this book:





Red print       Indicates entries you make at the terminal.

This typeface   Indicates prompts and messages from the terminal.

lowercase       Lowercase text in a function call, or in 
                a DCL command or command procedure, indicates that 
                you substitute a valid expression in that place.

[]              Brackets are used after installation questions
                to enclose the default answer. Press RETURN
                to accept the default value.

                Brackets in a function or in a DCL command
                indicate an optional entry.


1               Marks the order of the steps you must follow 
2               to complete a procedure.
3

a               Marks steps within a major step in a procedure.
b
c


Type            Indicates characters you type from the keyboard.  


















                                  x













                              Chapter 1

                             Introduction



1.1  Introduction to the Gateway

The Message Router VMSmail Gateway is part of MAILbus.  MAILbus
comprises Message Router and its Gateways, of which the VMSmail
Gateway is one.  The Message Router VMSmail Gateway Kit contains the
Message Router VMSmail Gateway and Message Router.  The Gateway allows
you to exchange mail between VMSmail and a Message Router system.
Using the Gateway, a VMSmail user and a user of a Message Router based
mail system can send mail to each other.

VMSmail users can also use the Gateway when exchanging mail with each
other.  This enables them to take advantage of Message Router's
store-and-forward capability, which is useful if a node is not
operating.



1.2  Introduction to Installation and Configuration

You cannot use the Gateway until you have first installed and then
configured it.  You do not have to configure the Gateway immediately
after installing it.  If you have other MAILbus components that you
want to install, such as other gateways, you can install these first
and configure all the components together.

If you are installing the Gateway on VMS Version 5.0, you must use the
VMS License Management Utility to register the Gateway before starting
the installation procedure.  An attempt to install an unlicensed
Gateway on VMS Version 5.0 will fail.  Refer to the VMS License
Management Utility Manual for details of how to use the VMS License
Management Utility.

This book deals with the installation of the Message Router VMSmail
Gateway on VMS Version 4.6, 4.7, and 5.0, and on MicroVMS Version 4.6
and 4.7.


                                 1-1

Introduction


                                 NOTE

        If you install the Gateway on VMS Version 4.6 or 4.7,
        or on MicroVMS, and then upgrade to VMS Version 5.0,
        you must then register the Gateway's Product
        Authorization Key and re-install the Gateway.




1.2.1  The Installation Procedure

Use the VMSINSTAL procedure to install the Gateway.  This procedure is
interactive and takes you through the installation step by step.  Each
step is described fully in Chapter 3.

The installation verification procedure (IVP), if requested, runs
immediately after the installation, and is fully described in Chapter
3.  If the IVP runs successfully, the Gateway software has been
installed but cannot be used until it is configured.  See Section
1.2.2 for information about the configuration procedure.

Installing the Gateway and running the IVP should take about 30 or 40
minutes, depending on the system configuration and type of
distribution medium used.  The installation procedure is the same,
whatever your distribution medium.

The installation procedure varies slightly, according to whether you
are performing a new or an upgrade installation.  The differences are
fully described in Chapter 2.

Prepare your system for installation by following the instructions in
Chapter 2.



1.2.2  The Configuration Procedure

After installing the Gateway, configure it as described in the Message
Router VMSmail Gateway Management Guide.  You will not be able to use
the Gateway until it has been configured.

The configuration procedure allows you to customize the Gateway to
meet the requirements of your system.








                                 1-2

                                                          Introduction


1.3  Error Handling

If you receive an unexpected error message during installation, check
that you have responded to the prompts correctly.  If you make a
mistake and are re-prompted, re-enter the correct information.  If
that fails, check the installation conditions, for instance, the
preceding warning messages or space available on the device you are
installing on.  Restart the installation, and if the installation
fails again at the same point, stop the installation and contact:

      o  Your Customer Support Center, if you have a service contract

      o  Your local DIGITAL office to arrange for a service contract,
         if you do not have one






































                                 1-3















                              Chapter 2

                   Preparing to Install the Gateway



2.1  Preparation Checklist

Complete the following checklist to prepare your VAX/VMS system for
the new or upgrade installation:

      1  Check that your Gateway distribution kit contains everything
         listed on the bill of materials, which is included with the
         kit.

         The distribution medium may be a magnetic tape or disk(s)
         containing all the files listed in Appendix A.  The type of
         medium depends on the hardware of your system.

      2  Check that you have a Software Product Description (SPD).

      3  Ensure that your system has the prerequisite software and
         hardware.  See Section 2.2.

      4  If you are installing the Gateway on VMS Version 5.0, check
         that the Gateway Product Authorization Key is registered and
         loaded.  The VMS License Management Utility Manual describes
         how to use the licensing utility.

      5  Prepare the system for installation.  See Section 2.3.

      6  Make sure that your VAX/VMS system contains a Message Router
         Version 3.1 that has been successfully installed.  You can do
         this by running the IVP during the Message Router
         installation.  You do not have to configure Message Router
         Version 3.1 before installing the Gateway.

         If you run the IVP during the Gateway installation, both
         Message Router and DECnet are set running on this node.
         These, and the Gateway, are shut down after the IVP has been
         run.  (If, despite DIGITAL's recommendation, you install the


                                 2-1

Preparing to Install the Gateway


         Gateway while DECnet is still running, the IVP does not shut
         it down.)

Version 3.1 of the Message Router VMSmail Gateway kit contains Version
3.1 of Message Router and Version 3.1 of the Message Router VMSmail
Gateway.  Message Router Version 3.1 should be installed first as
described in the Message Router Installation Guide.

Version 2.* and 3.0 of the Gateway are compatible with Version 3.1 of
Message Router.  Version 3.1 of the Gateway cannot operate with
Version 2.0 of Message Router.



2.2  Prerequisite Software and Hardware

To install the Message Router VMSmail Gateway Version 3.1, you must
have:

      o  A valid VAX or MicroVAX system configuration.

      o  Message Router Version 3.1 installed.

      o  DECnet installed.

      o  A minimum of 10000 blocks of free space available for
         installation, and 2000 blocks available permanently for the
         Gateway on the disk where SYS$UPDATE resides.  SYS$UPDATE is
         the working directory that the installation procedure uses.

      o  VAX/VMS Version 4.6 or later installed on the node or
         cluster.

The following software must be installed on a MicroVAX running
MicroVMS:

      o  MicroVMS base system Version 4.6 or later

      o  System Symbol Table File (SYS$SYSTEM:SYS.STB) from diskette
         SYSP

      o  Object and Shareable Image Libraries (SYS$SHARE:IMAGELIB.OLB)
         from diskette PROG

      o  Print and Batch Queue Utilities (SYS$BATCH) from diskette
         USER

      o  DECnet from diskette DECNET

Section 2.8 gives details of how to install any software missing on a


                                 2-2

                                      Preparing to Install the Gateway


MicroVAX running MicroVMS.

The following software must be installed on a VMS Version 5.0 system:

      o  VAX/VMS Version 5.0

      o  System Symbol Table File (SYS$SYSTEM:SYS.STB)

      o  Object and Shareable Image Libraries (SYS$SHARE:IMAGELIB.OLB)

      o  File Access Control List utilities

      o  Print and Batch Queue utilities (SYS$BATCH)

      o  The VMS MAIL utility

Section 2.9 gives details of how to use the VMS Tailoring utility,
VMSTAILOR, to install any software missing on a VMS Version 5.0
system.



2.3  Preparing Your System for Installation

Follow these steps before invoking VMSINSTAL:

      1  Log in to the SYSTEM account at the operator's console.

      2  Ensure that there are no active users on the system:

          a  Enter the following command to determine how many users
             can log in to the system:

             $ SET LOGINS/INTERACTIVE

             This command displays the maximum number of interactive
             logins allowed on your system.  You must make a note of
             this number in order to reset it at the end of the
             installation.

          b  Ask these users to log out by typing:


             $ SET LOGINS/INTERACTIVE=0
             $ REPLY/BELL/ALL "PLEASE LOG OUT"







                                 2-3

Preparing to Install the Gateway


      3  Backup your system disk.

         If a system failure occurs at a critical point during the
         installation, some files can be corrupted.  Also, you are
         given the choice of purging old files during the
         installation.

         Use the backup copy of the system disk for installation.  In
         this way you can verify that the backup copy contains a
         working system image.  Also, the backup copy will have more
         adjoining free space.

      4  Ensure that there are at least 10000 blocks available on the
         system disk for the installation of the Gateway.  After
         installation, the Gateway needs at least 2000 blocks on the
         system disk.  Use the SHOW DEVICE command to find out how
         many blocks are available on the system disk.

         To display the number of blocks available on the system disk,
         type:

         $ SHOW DEVICE SYS$SYSDEVICE

      5  You must ensure that the account that VMSmail uses is set up
         with sufficient quota.  By default, VMSmail uses the DECNET
         account.  If you are not sure what account VMSmail uses on
         your system, use the NCP command SHOW OBJECT CHARACTERISTICS
         to check the characteristics of the VMSmail object.  If the
         characteristics do not include a user id, then VMSmail is
         using the default account.

         Set FILLM for the account that VMSmail uses to at least 9.

         Set BYTLM for the account to 512 multiplied by FILLM.

         To set the quota for these parameters, use the Authorize
         utility as follows:

          a  Invoke the Authorize utility:

             $ RUN AUTHORIZE

          b  Modify the FILLM quota:

             UAF> MODIFY accountname/FILLM=quota1

             where:





                                 2-4

                                      Preparing to Install the Gateway


              -  accountname is the name of the account that VMSmail
                 uses

              -  quota1 is the quota you want to specify for FILLM,
                 and should be at least 9


          c  Modify the BYTLM quota:

             UAF> MODIFY accountname/BYTLM=quota2

             where:

              -  accountname is the name of the account that VMSmail
                 uses

              -  quota2 is 512 multiplied by the quota you specified
                 for FILLM.


          d  Exit from the Authorize utility:

             UAF> EXIT


         If these quotas for the account that VMSmail uses are not set
         sufficiently high, a message sent to many recipients on many
         nodes might not be delivered efficiently.

                                     NOTE

                 During the configuration procedure, you have
                 the opportunity to specify the number of
                 nodes that the Gateway can connect to at one
                 time.  The default is 5 nodes.  You must set
                 the FILLM quota for the account that VMSmail
                 uses to the number of nodes that can be
                 connected to at once, plus 4.  If you choose
                 to change the number of nodes during the
                 configuration, you will need to modify the
                 FILLM and BYTLM quotas accordingly.


      6  Check that VMSmail is working by sending a mail message to
         0::SYSTEM.  If the message arrives at the SYSTEM account,
         VMSmail is working.

      7  If Message Router Version 3.1 is running on your system, you
         must stop it and all MAILbus components as follows:



                                 2-5

Preparing to Install the Gateway


         $ @SYS$MANAGER:MB$CONTROL STOP=(ER,...,TS,DDS,MS)

         You must stop the all MAILbus components on every node in a
         VAXcluster.

      8  Shut down DECnet by typing the following commands:

         $ RUN SYS$SYSTEM:NCP
         NCP> SET EXECUTOR STATE OFF
         NCP> EXIT


You must shut down DECnet on every node in a cluster.

Read Section 2.4 if you are upgrading the Gateway from Version 2.*.
Read Section 2.5 if you are upgrading the Gateway from Version 3.0.
Read Section 2.6 if you are re-installing Version 3.1 of the Gateway.



2.4  Preparing for an Upgrade Installation from Version 2.0 or 2.1

The following is a list of preparations that you should make if you
are upgrading the Gateway.  Make sure that you have also followed the
instructions in Section 2.3.

      1  If you have Version 1.0 or 1.1 of the Gateway, upgrade to
         Version 2.0 or 2.1 before installing Version 3.1 of the
         Gateway.

      2  If you want to retain data or messages from an existing
         Version 2.* Gateway installation, find out the directory
         specification for the Gateway directory.

         The directory specification should be in the form:

         ddcu:[directoryname]

         where ddcu is the name of the device where the miscellaneous
         directory is located, and directoryname is the name of the
         Gateway directory.

         Note the directory specification in the space provided.

         ________________________________

      3  The installation procedure replaces the file VMSERROR.DAT.
         VMSERROR.DAT contains the list of errors which, when they
         occur, cause the Gateway to stop trying to send the message.
         If you have customized VMSERROR.DAT, you must edit the new


                                 2-6

                                      Preparing to Install the Gateway


         file to recustomize it each time you install the Gateway.

      4  Version 3.1 of the Gateway needs at least 10000 blocks.  If
         you are upgrading from Version 2.* of the Gateway, find out
         the MRGATE account block quota.  Add at least this amount to
         the MBMANAGER account quota of the Version 3.1 Message Router
         system, or add 10000 if this is greater.

      5  If you are upgrading from Version 2.0 or 2.1 of the Gateway,
         stop the Gateway and remove MRTOVMS from the batch queue as
         follows:

          a  Log in to the SYSTEM account

          b  Stop the Gateway by typing:

             $ DEASSIGN/SYSTEM MRG$DIR

             You must stop the Gateway on every node in a VAXcluster.

          c  Remove MRTOVMS from the batch queue by typing the
             following command:

             $ SHOW QUEUE queuename/ALL

             where queuename is the name of the batch queue MRTOVMS is
             running on.  The default queue name is SYS$BATCH.

             This command displays the list of jobs queued to run on
             the batch queue specified.

             Examine the queue for the MRTOVMS entry and make a note
             of the entry number.  You can delete this entry from the
             queue by typing:

             $ DELETE/ENTRY=entrynumber queuename

             where entrynumber is the entry number you noted, and
             queuename is the name of the queue.



To install Version 3.1 of the Gateway on a VAXcluster or Local Area
VAXcluster, follow the instructions in Section 2.7 of this book after
you have completed the installation preparations.

If you are installing the Gateway on a MicroVAX running MicroVMS,
follow the instructions in Section 2.8.




                                 2-7

Preparing to Install the Gateway


If you are installing the Gateway on a VMS Version 5.0 system, follow
the instructions in Section 2.9.

For all other cases you do not need to read the rest of this chapter.
Turn to Chapter 3, which describes the installation procedure.



2.5  Preparing for an Upgrade Installation from Version 3.0

Prepare your system for installation as follows:

      1  If the Gateway is already configured and running on your
         system, you must stop it by typing:

         $ @SYS$MANAGER:MB$CONTROL STOP=MRG

         You must stop the Gateway on every node in a VAXcluster.

      2  Log in to the SYSTEM account

          a  Remove MRTOVMS from the batch queue by typing the
             following command:

             $ SHOW QUEUE queuename/ALL

             where queuename is the name of the batch queue MRTOVMS is
             running on.  The default queue name is MB$BATCH.

             This command shows the list of jobs queued to run on the
             batch queue specified.

             Examine the queue for the MRTOVMS entry and make a note
             of the entry number.  You can delete this entry from the
             queue by typing:

             $ DELETE/ENTRY=entrynumber queuename

             where entrynumber is the entry number noted above, and
             queuename is the name of the queue.


      3  If you configured the Gateway to run with exception
         reporting, you must also delete MB$MRG from the batch queue.
         Do this in the same way as you deleted MRTOVMS from the batch
         queue.

         If either of these two entries are in the batch queue, the
         old batch jobs will fail if you select the purge option
         during the installation procedure.


                                 2-8

                                      Preparing to Install the Gateway


If you are installing the Gateway on a VAXcluster or Local Area
VAXcluster, complete the further preparations described in Section
2.7.

If you are installing the Gateway on a MicroVAX running MicroVMS,
follow the instructions in Section 2.8.

If you are installing the Gateway on a VMS Version 5.0 system, follow
the instructions in Section 2.9.

For all other cases you do not need to read the rest of this chapter.
Turn to Chapter 3, which describes the installation procedure.



2.6  Preparing to Re-install Version 3.1

Prepare your system for installation as follows:

      1  If the Gateway is already configured and running on your
         system, you must stop it by typing:

         $ @SYS$MANAGER:MB$CONTROL STOP=MRG

         You must stop the Gateway on every node in a VAXcluster.

      2  During the installation procedure, you are asked if you want
         to purge files replaced by this installation.  If you are
         re-installing Version 3.1 of the Gateway and purge your
         files, as recommended, you must also remove MRTOVMS from the
         batch queue as follows:

          a  Log in to the SYSTEM account

          b  Remove MRTOVMS from the batch queue by typing the
             following command:

             $ SHOW QUEUE queuename/ALL

             where queuename is the name of the batch queue MRTOVMS is
             running on.  The default queue name is MB$BATCH.

             This command shows the list of jobs queued to run on the
             batch queue specified.

             Examine the queue for the MRTOVMS entry and make a note
             of the entry number.  You can delete this entry from the
             queue by typing:




                                 2-9

Preparing to Install the Gateway


             $ DELETE/ENTRY=entrynumber queuename

             where entrynumber is the entry number noted above, and
             queuename is the name of the queue.


         If you configured the Gateway to run with exception
         reporting, you must also delete MB$MRG from the batch queue.
         This is done in the same way as MRTOVMS is deleted from the
         batch queue.

         If either of these two entries are in the batch queue, the
         old batch jobs will fail if you select the purge option
         during the installation procedure.


If you are installing the Gateway on a VAXcluster or Local Area
VAXcluster, follow the instructions in Section 2.7.

If you are installing the Gateway on a MicroVAX running MicroVMS,
follow the instructions in Section 2.8.

If you are installing the Gateway on a VMS Version 5.0 system, follow
the instructions in Section 2.9.

For all other cases you do not need to read the rest of this chapter.
Turn to Chapter 3, which describes the installation procedure.



2.7  Preparing to Install the Gateway on a VAXcluster or Local Area
     VAXcluster

You can run the Gateway on any VMS Version 4.6 or later VAXcluster or
Local Area VAXcluster configuration.  If you are running VMS Version
5.0, you must use the VMS License Management Facility on every node in
a cluster.  (Refer to the VMS License Management Utility Manual for
details of VMSLICENSE.)

If you group several nodes into a VAXcluster, you must make sure that
they are running the same version of the Gateway.

There are two types of cluster:  homogeneous clusters and
heterogeneous clusters.

In a homogeneous VAXcluster all the machines share the same user
community and access the same devices.  Each node provides access for
the other nodes to the devices that it owns.




                                 2-10

                                      Preparing to Install the Gateway


In a heterogeneous VAXcluster the nodes do not share the same user
community.  Individual nodes may have different user communities and
different devices available at each node.  The nodes in the same
heterogeneous cluster can be booted from different devices, although
there are some shared disk areas.



2.7.1  Installing the Gateway on a Homogeneous Cluster

If you are installing the Gateway on a homogeneous cluster, you need
only install it once to modify the user authorization file
(SYSUAF.DAT).

If you have identical copies of the SYSUAF.DAT file on the cluster,
you must install the Gateway so that it modifies each copy of the
file.

If you are installing the Gateway on a MicroVAX running MicroVMS, read
Section 2.8 for a description of further preparations.

If you are installing the Gateway on a VMS Version 5.0 system, read
Section 2.9 for a description of further preparations.

For all other cases, you do not need to read the rest of this chapter.
Turn to Chapter 3 for a description of the installation procedure.



2.7.2  Installing the Gateway on a Heterogeneous Cluster

In a heterogeneous cluster you have to install the Gateway on more
than one node.  The installation procedure must modify the user
authorization file (SYSUAF.DAT).  If the SYSUAF.DAT is shared between
a set of nodes, however, you need only install the Gateway on one node
in the set.  List the smallest number of nodes from which all the
copies of SYSUAF.DAT database can be modified, and install the Gateway
on all nodes in the list.

If you are not going to install the Gateway on every node in a
heterogeneous cluster, you must set the logical name MAIL$SYSTEM_FLAGS
to ensure that messages can reach one of the nodes that does have a
Gateway, and that the From field includes the name of the node from
which a message was sent, rather than the cluster name.

Use the SHOW LOGICAL command to check the translation of the logical
name MAIL$SYSTEM_FLAGS.  If there is no MAIL$SYSTEM_FLAGS logical
there is no problem.  If there is a logical, it will translate to a
number between 1 and 7 inclusive.  If the logical translates to an odd
integer, you must set it to an even integer.


                                 2-11

Preparing to Install the Gateway


To redefine the MAIL$SYSTEM_FLAGS logical name, use the following
command:

$ DEFINE /SYSTEM /EXECUTIVE_MODE MAIL$SYSTEM_FLAGS n

where n is an even integer.  Refer to the VAX/VMS MAIL Utility Manual
for details of the meaning of the flag.

You cannot specify an odd integer, because that would mean that
VMSmail would bypass DECnet and try to connect to a Gateway on the
local node, even if the local node does not have a Gateway.  Also, an
odd integer would mean that the From field would contain the cluster
name rather than the name of the node from which the message was sent.
In this case, the message would arrive at its destination, but a reply
to that message would be addressed to the cluster name.  The message
might then be sent to a node within the cluster that does not have a
Gateway, in which case the reply would fail.

If you are installing the Gateway on a MicroVAX running MicroVMS,
follow the instructions in Section 2.8.

If you are installing the Gateway on a VMS Version 5.0 system, follow
the instructions in Section 2.9.

For all other cases you do not need to read the rest of this chapter.
Turn to Chapter 3 for a description of the installation procedure.



2.8  Preparing MicroVMS for a Gateway Installation Procedure

Complete the following checklist, in addition to the other relevant
pre-installation checks, to prepare your MicroVMS system for the new
or update installation:

      1  The Object and Shareable Image libraries
         (SYS$SHARE:IMAGELIB.OLB) must be installed.  If the libraries
         are installed, the file IMAGELIB.OLB is in SYS$SHARE.

         If the libraries are missing, install them from the diskettes
         labeled PROG, as described in the installation section of the
         MicroVMS User's Manual.

         VMSINSTAL displays:

              Do you want to install the entire kit?

         Type NO.




                                 2-12

                                      Preparing to Install the Gateway


         Answer NO to all sub-options except:

              Do you want to install the Object and Shareable Image
              Libraries?

         Type YES.

      2  Check that you have the Print and Batch Queue utilities on
         your system, and that the batch queue, SYS$BATCH, is running.
         Check that the file SMBSRVSHR.EXE is in SYS$LIBRARY.  If you
         find the file, use the following command to see whether the
         batch queue is running:

         $ SHOW QUEUE /BATCH /ALL

         If these utilities are missing, then install them from the
         diskettes labeled USER, as described in the installation
         section of the MicroVMS User's Manual.

         VMSINSTAL displays:

         Do you want to install the entire kit?
         Type NO

         For each suboption, you are asked if it is required.  Answer
         NO to all questions except:

         Do you want to install the Print and Batch queue utilities?
         Type YES

         If you do not have a batch queue SYS$BATCH, use the following
         command to create it:

         $ START /QUEUE /MANAGER /BUFFER_COUNT=10 /EXTEND_QUANTITY=25

         To ensure that the batch queue starts at all system startups,
         edit the system startup file (SYS$MANAGER:SYSTARTUP.COM) to
         include that command line.

      3  Check that you have the VMSmail utility on your system, and
         that the image is installed.  To do this, type:

         $ MAIL

         If the MAIL> prompt appears, the utility is installed.

         If the utility is missing, install it from the diskettes
         labeled UTIL, as described in the installation section of the
         MicroVMS User's Manual.



                                 2-13

Preparing to Install the Gateway


         VMSINSTAL displays:

              Do you want to install the entire kit?

         Type NO.

         Answer NO to all sub-options except:

              Do you want to install the Mail utility?

         Type YES.

         Edit the system startup file (SYS$MANAGER:SYSTARTUP.COM) to
         install the mail image when the system reboots.  Shutdown and
         reboot the system to execute the commands in SYSTARTUP.


Once you have completed these preparations, turn to Chapter 3.



2.9  Preparing VMS Version 5.0 for a Gateway Installation Procedure

This section describes how to prepare a VMS Version 5.0 system for the
installation of the Gateway.

If you are running VMS Version 5.0, you need to check that the Gateway
Product Authorization Key is registered and loaded.  To check this,
type the following command:

$ LICENSE LIST

If the list does not include an entry for the Message Router VMSmail
Gateway, refer to the VMS License Management Utility Manual for
details of the licensing utility.

Also, you might need to use the VMS tailoring utility to prepare your
system for the Gateway installation procedure.  The tailoring utility
enables you to add and remove software from a VMS Version 5.0 system.
You must ensure that your VMS Version 5.0 system includes all the
software required for the installation.  (You can use the VMS
tailoring utility on any VAX system, but you are most likely to need
it on a MicroVAX.)









                                 2-14

                                      Preparing to Install the Gateway


2.9.1  Preparing to Use the VMS Tailoring Utility

Message Router VMSmail Gateway Version 3.1 requires the following
software:

      o  Object and Shareable Image libraries

      o  File Access Control List utility

      o  Print and Batch Queue utilities

      o  The VMS MAIL utility

Complete the following checklist to see whether these files and
utilities are already installed on your system.

     1   Check that the Object and Shareable Image libraries are
         installed (SYS$SHARE:IMAGELIB.OLB).  If the libraries are
         installed the file IMAGELIB.OLB is in SYS$SHARE.

     2   Check that the File Access Control List utilities
         (SYS$SYSTEM:ACLEDT.EXE) are installed.  If the File Access
         Control List utilities are installed, the file ACLEDT.EXE is
         in SYS$SYSTEM.

     3   Check that the Print and Batch Queue utilities are installed,
         and have a running batch queue, SYS$BATCH.  Check that the
         file SMBSRVSHR.EXE is in SYS$LIBRARY.  If you find the file,
         use the following command to see whether the batch queue is
         running:

         $ SHOW QUEUE /BATCH /ALL

         If the utilities are installed but there is no running batch
         queue, edit SYS$MANAGER:SYSTARTUP_V5.COM to ensure that it
         includes the following command line:

         $ START /QUEUE /MANAGER /BUFFER_COUNT=10 /EXTEND_QUANTITY=25

     4   Check that the VMSmail utility is installed.  To do this,
         type:

         $ MAIL

         If the MAIL> prompt appears, the VMSmail utility is
         installed.






                                 2-15

Preparing to Install the Gateway


If any of these libraries and utilities are missing, use the VMS
Tailoring Utility, VMSTAILOR, to install them, as described in Section
2.9.2.

If these VMS libraries and utilities are all installed on your system,
you are ready to install Message Router Version 3.1, and do not need
to read the rest of this chapter.  Turn to Chapter 3 for a description
of the installation procedure.



2.9.2  Using the VMS Tailoring Utility

If you need to install any of the VMS libraries and utilities
mentioned in Section 2.9.1, perform the following steps:

     1   Invoke VMSTAILOR in the following way:

         a   Log in to the SYSTEM account.

         b   Type the following command:

             $ RUN SYS$UPDATE:VMSTAILOR

         c   The procedure starts and displays:

             This is the VMS tailoring utility. It lets you customize VMS 
             for your particular system. You do this by identifying 
             classes and subclasses of VMS files that you want to add or 
             delete.

             VMSTAILOR has three phases:

                    - First, VMSTAILOR asks if you want to tailor your 
             system by adding files ("tailor on") or by deleting files 
             ("tailor off").

                    - Second, if you choose the "tailor on" procedure, 
             VMSTAILOR lists each class of VMS files and asks if you 
             want to include them on the system disk. If you choose 
             the "tailor off" procedure, VMSTAILOR lists each class of 
             VMS files and asks if you want to delete them from the 
             system disk.

                    - Third, VMSTAILOR carries out your instructions.

             NOTE: To cancel VMSTAILOR during the first and second phases, 
             press Control-C, Control-Y, or Control-Z. If you cancel 
             VMSTAILOR during the third phase, you may end up with a 
             partially tailored disk.


                                 2-16

                                      Preparing to Install the Gateway


             Do you want to tailor files "ON" or "OFF"? 


             Type ON and press RETURN.


     2   The procedure displays:

         TAILOR-ON
         ----------
         You will now be prompted with a list of the classes and 
         subclasses of VMS files that are optional. The size of each 
         class and subclass is included in the list. This will help 
         you decide whether or not you want to add a class or subclass 
         to your system.

         Under some classes, there is a set of common files that is 
         required in order for any subclasses to work. These files are 
         added when you ask for either the entire class or any of its 
         subclasses.

         Total size of the system disk is nnnnnnn blocks.
         Total space used on the system disk is nnnnnnn blocks.
         Total space left on the system disk is nnnnnnn blocks.

         CLASS - Network support
                   Size of entire class (with subclasses): 1442
                   Size of common files required for any subclass: 1221
                   Do you wish to select the entire class (default = NO)?

         where nnnnnnn are numbers.

         Press RETURN to accept the default answer, because the
         Gateway does not require the entire class.

     3   The procedure displays:

         Do you wish to select any of its subclasses (default NO)?

         Press RETURN to accept the default answer, because the
         Gateway does not require any of the subclasses.

     4   The procedure displays:

         CLASS - Programming Support
                   Size of entire class (with subclasses): 9749
                   Size of common files required for any subclass: 0
                   Do you wish to select the entire class (default = NO)?




                                 2-17

Preparing to Install the Gateway


         Press RETURN to accept the default answer, as the Gateway
         does not require the entire class.

         The procedure displays:

         Do you wish to select any of its subclasses (default = NO)?

         If the Object and Shareable Image libraries are already
         installed on your system, type NO and go to Step 6.
         Otherwise, type YES and press RETURN.

     5   The procedure displays:

         Select the subclasses that you wish to use:

         For each subclass, press RETURN except for the following
         subclass:

         SUBCLASS - Object and Shareable Image Libraries (3480 
         blocks) [NO]:

         Type YES and press RETURN.

     6   The procedure displays:

         CLASS - RMS journaling files
                   Size of entire class (with subclasses): 72
                   No subclasses in this tailor class.
                   Do you wish to select the entire class (default = NO)?

         Press RETURN to accept the default answer, because the
         Gateway does not require the class.

     7   The procedure displays:

         CLASS - System programming Support
                   Size of entire class (with subclasses): 1290
                   Size of common files required for any subclass: 87
                   Do you wish to select the entire class (default = NO)?

         Press RETURN to accept the default answer, because the
         Gateway does not require the entire class.

     8   The procedure displays:

         Do you wish to select any of its subclasses (default = NO)?

         Press return to accept the default answer, because the
         Gateway does not require any of the subclasses.



                                 2-18

                                      Preparing to Install the Gateway


     9   The procedure displays:

         CLASS - Secure User's Environment
                   Size of entire class (with subclasses): 613
                   Size of common files required for any subclass: 0
                   Do you wish to select the entire class (default = NO)?

         Press RETURN to accept the default answer, because the
         Gateway does not require the entire class.

    10   The procedure displays:

         Do you wish to select any of its subclasses (default = NO)?

         If the File Access Control List utilities and the Print and
         Batch Queue utilities are already installed on your system,
         press RETURN and go to Step 12.

         If you need to install either the File Access Control
         utilities, or the Print and Batch queue utilities, type YES
         and press RETURN.

    11   The procedure displays:

         Select the subclasses that you wish to use:

         For each subclass, press RETURN except for the following
         subclasses:

         SUBCLASS - File Access Control List utilities (386 blocks) [NO]:

         SUBCLASS - Print and Batch Queue utilities (106 blocks) [NO]:

         If you need to install these utilities, type YES and press
         RETURN.  Otherwise, press RETURN.

    12   The procedure displays:

         CLASS - Utilities
                   Size of entire class (with subclasses): 8692
                   Size of common files required for any subclass: 0
                   Do you wish to select the entire class (default = NO)?

         Press RETURN to accept the default answer, because the
         Gateway does not require the entire class.

    13   The procedure displays:

         Do you wish to select any of its subclasses (default = NO)?



                                 2-19

Preparing to Install the Gateway


         If the VMSmail utility is already installed on your system,
         press RETURN and go to Step 15.

         If you need to install the VMSmail utility, type YES and
         press RETURN.

    14   The procedure displays:

         Select the subclasses that you wish to use:

         For each subclass, press RETURN, except for the following
         subclass:

         SUBCLASS - MAIL utility (394 blocks) [NO]:


         If you need to install this utility, type YES and press
         RETURN.  Otherwise, press RETURN.

    15   For all the remaining classes and subclasses offered by the
         procedure, press RETURN because the Gateway does not require
         them.

    16   The procedure displays:

         Do you wish to add all of the options selected?

         Type YES.  The utility adds the selected options to your
         system, and displays the names of the files that it is
         adding.


Once you have completed these preparations, turn to Chapter 3 for a
description of the installation procedure.


















                                 2-20













                              Chapter 3

                        Installing the Gateway



This chapter explains how to install the Gateway.



3.1  Overview of VMSINSTAL

VMSINSTAL is a procedure that can be used to install optional software
products on the VMS operating system.  VMSINSTAL requires at least two
parameters:

      o  The name of the product(s) being installed

      o  The name of the device where the distribution medium is
         mounted or loaded




3.2  Installation Procedure

If possible, use a hardcopy terminal when performing the installation,
to preserve a record of the procedure in case of failure.

Remember that you can call on-line help by typing a question mark (?)
key in response to any prompt.












                                 3-1

Installing the Gateway


Complete the following steps:

      1  Log in to the SYSTEM account, and type the following command:

         $ @SYS$UPDATE:VMSINSTAL MRGATE031 ddcu OPTIONS N

         where:

          -  MRGATE031 is the identity of the product being installed

          -  ddcu is the name of the device where the distribution
             medium is to be mounted, for example, MTA0

          -  OPTIONS N provides the option of reading or printing the
             on-line release notes

                                       NOTE

                 If this is a re-installation of the Gateway
                 Version 3.1, you can omit the parameter OPTIONS
                 N, providing you have already read the release
                 notes.



      2  The procedure starts, and displays:


                 VAX/VMS Software Product Installation Procedure Vx.x

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

         where dd-mmm-yyyy and hh:mm are the current date and time,
         and x.x is the VMS version number.

      3  You may receive one or more of the following warning
         messages:


         %VMSINSTAL-W-LOWQUOTA, One or more account quotas may be too low.
         %VMSINSTAL-W-DECNET, Your DECnet network is up and running.
         %VMSINSTAL-W-ACTIVE, The following processes are still active.

         If you receive any warning messages, you are advised to exit
         from the installation procedure, by pressing RETURN, and fix
         the problem, as described in Chapter 2.  Then re-start the
         installation.




                                 3-2

                                                Installing the Gateway


         If there are any active system processes, the procedure lists
         them and asks:

         * Do you want to continue anyway [NO]?

         You are advised to shut down the active processes.  To do
         this, press RETURN to accept the default answer of NO and to
         exit from the installation procedure.  Ask other users to log
         out, as described in Section 2.3.

         Then re-start the installation.

         If there are no active system processes, or if you want to
         continue the installation regardless of the warning messages,
         type YES.

      4  The procedure asks:

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

         If the system disk has not recently been backed up, type NO
         to abort the installation and make a backup copy.  Otherwise,
         press RETURN to accept the default answer of YES.

      5  The procedure instructs you to mount the distribution volume:

         Please mount the first volume of the set on ddcu

         * Are you ready?


         where ddcu is the device name you supplied in Step 1.

         When you have mounted the distribution volume, type YES.

      6  The procedure confirms that the volume has been successfully
         mounted and displays:

         %MOUNT-I-MOUNTED, Message Router VMSmail Gateway mounted on _ddcu


         The following products will be processed:

           Message Router VMSmail Gateway V3.1

                     Beginning installation of Message Router VMSmail 
                     Gateway V3.1 at hh:mm
            
         %VMSINSTAL-I-RESTORE, Restoring product saveset A...



                                 3-3

Installing the Gateway


         where ddcu is the device name.

      7  If you did not specify OPTIONS N, the procedure continues at
         step 9.

         Otherwise, the procedure displays a list of options relating
         to the release notes.  The options offered vary from VMS
         Version 4.* to Version 5.0.  You should select the option
         that prints the release notes.

         If you select the option that prints the release notes, the
         procedure displays:

         * Queue name[SYS$PRINT]:


         Enter the name of a print queue where you want the release
         notes to be printed.  The procedure then displays a message
         telling you that the release notes have been successfully
         queued to the printer.  If you do not specify the name of a
         print queue, the output is directed by default to SYS$PRINT.

      8  The procedure asks:

         * Do you want to continue the installation [NO]?

         You are advised to exit from the installation and read the
         release notes.  Press RETURN to accept the default answer of
         NO.  Otherwise, type YES and press RETURN.

         When you have read the release notes you can restart the
         installation, omitting the parameter OPTIONS N.

      9  The procedure confirms that the product's release notes have
         been moved to SYS$HELP.

         %VMSINSTAL-I-RELMOVED, The products release notes have been
         successfully moved to SYS$HELP

     10  If you are installing the Gateway on VMS Version 4.6 or 4.7,
         or on MicroVMS, go to step 11.

         If you are installing the Gateway on VMS Version 5.0,
         VMSINSTAL displays details of the product that you want to
         install:

                Product:         MR-VMSMAIL-GATEWAY
                Producer:        DEC
                Version:         3.1
                Release Date:    dd-mmm-yyyy


                                 3-4

                                                Installing the Gateway


         where dd-mmm-yyyy is the release date.

         VMSINSTAL displays:

         * Does this product have an authorization key registered and
         loaded?

         If you have not registered and loaded the Product
         Authorization Key for the Gateway, type NO to abort the
         installation, and refer to the VMS License Management Utility
         Manual for a description of how to register and load the
         Gateway Product Authorization Key.  When you have registered
         and loaded the Product Authorization Key, restart the
         installation.

         If the Product Authorization Key for the Gateway is
         registered and loaded, type YES.

     11  The procedure asks:

         * Do you want help text printed before every question [NO]?

         Help text is available for all questions asked during the
         installation.  If you want the help text displayed before
         each question, type YES and press RETURN.  Otherwise, press
         RETURN to accept the default answer of NO.

         Remember that you can still type a question mark (?) in
         response to any prompt, to call on-line help if you do not
         want help text printed automatically.

     12  The procedure asks:

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

         Press RETURN to accept the default answer of YES.  Otherwise,
         type NO.

     13  The procedure asks:

         * Do you want to run the IVP after the installation [YES]?

         You are advised to run the IVP to check that the installation
         has been successful.  Press RETURN to accept the default
         answer of YES.  Otherwise, type NO.

     14  If the procedure finds a Message Router VMSmail Gateway
         Version 3.* installation, VMSINSTAL displays:

              An Message Router VMSmail Gateway V3.* system has been found. 


                                 3-5

Installing the Gateway


              Any data from this system will be included in the current 
              installation, unless you choose to overwrite it with data from 
              a previous V2.* system.
                           
         * Do you want to keep data from a previous installation of Message 
         Router VMSmail Gateway V2.* [NO]? 


         If the procedure does not find a previous Message Router
         VMSmail Gateway V3.* installation, VMSINSTAL displays:

         * Do you want to keep data from a previous installation of Message 
           Router VMSmail Gateway V2.* [NO]? 

                                     NOTE

                 If you do not keep data from the most recent
                 VMSmail Gateway installation that has been
                 running on your system, you will lose all
                 messages that are in the process of being
                 delivered, and your customized files, when
                 the Gateway is re-installed.

                 If there is data from previous installations
                 of both Version 2.* and Version 3.*, be very
                 careful when you answer this question.


         Decide whether you want to keep data from a previous
         installation and type your reply of YES or press RETURN to
         accept the default accordingly.

         If you typed YES, and there is data from previous
         installations of both Version 2.* and Version 3.*, VMSINSTAL
         displays:

              Any data from the previous V2.* system will be used in 
              the current installation, and will overwrite any V3.* data.

              If you have V3.* data that you do not want to lose, press 
              CTRL/Y to abandon the installation procedure.
                        

     15  If you have replied NO to Step 14, the installation procedure
         continues at Step 16.  Otherwise, the procedure asks:

         * What is the existing MRGATE directory:

         If a previous directory can be found, this is offered as a
         default.  Press RETURN to accept the default Gateway


                                 3-6

                                                Installing the Gateway


         directory.  Otherwise, enter the directory specification
         noted in Step 2 of Section 2.4.

     16  The procedure displays:

         You have answered all the questions for the Message Router 
         VMSmail Gateway installation. Message Router VMSmail Gateway is 
         now being installed. The installation takes approximately 35 
         minutes, depending on the system configuration and media type. 


     17  The procedure displays a series of messages that tell you
         that the generation phase of the Gateway installation is
         proceeding.  There is a pause between each message.

         If this is a re-installation of version 3.1 of the Gateway,
         or an upgrade from version 3.0, the procedure continues at
         Step 18.  Otherwise, for a new installation, the procedure
         displays:

         %MRG-I-CREACC, Creating the MRGATE account
         %MRG-I-CHECDIRS, Checking Directories
         %MRGATE-I-CREMBDIR, Creating directory ddcu:[MB$.MRG]

         %VMSINSTAL-I-RESTORE, Restoring product saveset B...

         %MRG-I-LNKMRGATE, Linking the VMSmail Gateway images
         %MRG-I-LNKMRGTOVMS,  ...Linking the MRTOVMS image
         %MRG-I-LNKMRGFRVMS,  ...Linking the MRFROMVMS image
         %MRG-I-LNKMRGMSG,  ...Linking the Message Router VMSmail Gateway 
         message image
         %MRG-I-SETMRGFILES, Setting Message Router VMSmail Gateway file 
         ownership and protection
         %MRG-I-ASIGNMRGATE, Assigning Message Router VMSmail Gateway files 
         to target directories


         where ddcu is the device name.

         If the installation procedure finds an account or directory
         it does not expect, the following message is displayed:

         %MRG-I-ACCEXIST, MRGATE account already existed.

                  Accounts are only expected to exist before installation 
                  for a re-installation or upgrade. Installation is 
                  continuing.

                  Check that modified accounts do not have a different use.



                                 3-7

Installing the Gateway


         The installation procedure continues at Step 19.

     18  If this is a re-installation of Version 3.1, or an upgrade
         from Version 3.0 of the Gateway, the procedure displays:

         %MRG-I-MODACC, Modifying the MRGATE account
         %MRG-I-CHECDIRS, Checking Directories

         %VMSINSTAL-I-RESTORE, Restoring product saveset B...

         %MRG-I-LNKMRGATE, Linking the VMSmail Gateway images
         %MRG-I-LNKMRGTOVMS,  ...Linking the MRTOVMS image
         %MRG-I-LNKMRGFRVMS,  ...Linking the MRFROMVMS image
         %MRG-I-LNKMRGMSG, ...Linking the Message Router VMSmail Gateway 
         message image
         %MRG-I-SETMRGFILES, Setting Message Router VMSmail Gateway file 
         ownership and protection
         %MRG-I-ASIGNMRGATE, Assigning Message Router VMSmail Gateway files 
         to target directories



     19  After VMSINSTAL has marked the files for moving to the
         Gateway, more messages are displayed:

          The generation phase of the Message Router VMSmail Gateway installation 
          is now complete.

            In order to tailor the Message Router VMSmail Gateway to your 
            requirements, you must use the MAILbus configuration procedure, 
            SYS$MANAGER:MB$CONFIG.COM.


         You will not have a working system until the Gateway has been
         configured.  The configuration procedure is described in the
         Message Router VMSmail Gateway Management Guide.  You also
         need to refer to the Message Router Configuration Guide and
         other Gateway management guides, if you want to configure all
         the MAILbus products together.

     20  The procedure moves the Gateway files to their specified
         directories:

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

         When this message appears, the installation is completing.
         The IVP will now run automatically, if you requested it
         earlier, to check that the installation was successful.



                                 3-8

                                                Installing the Gateway


3.3  Running the IVP

The IVP runs automatically after the installation is complete, if you
requested it.  The following is an example of the Gateway installation
verification procedure.


            IVP for Message Router VMSmail Gateway 

                         Version 3.1

    This is the installation verification procedure (IVP) for the 
    Message Router VMSmail Gateway. It checks that the Gateway is 
    successfully installed on your system. 
  





==================================================================
        Message Router VMSmail Gateway Version V3.1 IVP

This verification procedure is in four stages: 

Stage 1 checks that all the Gateway files exist, and are the right size.

Stage 2 sets DECnet running if necessary. 

Stage 3 tests the Gateway by sending a mail message from VMSmail to
Message Router.  When this stage is complete, a message is displayed
on the screen. 

Stage 4 tests the Gateway by sending a mail message from Message Router
to VMSmail.  When this stage is complete, you will receive a mail
message.  This message is sent to the account from which you are
performing the verification.

The verification procedure has not completed successfully
until you have seen both the screen message and the mail message. 





------------------------------------------------------------------
        Message Router VMSmail Gateway  V3.1 file check
                       
        The total number of files is 19.
  


                                 3-9

Installing the Gateway


        All files exist and are the correct size.
        End of Message Router VMSmail Gateway V3.1 file check.
------------------------------------------------------------------
 Checking ORANGE VMSmail network response
Succeeded in activating VMSmail DECnet object 27 on node ORANGE

        Starting Management Service



        Starting Transfer Service



        Starting Message Router VMSmail Gateway 



        Stage 3 of the installation verification procedure for
        the Message Router VMSmail Gateway V3.1 successful

        Waiting for delivery of VMSmail sent through Gateway V3.1.

        The IVP waits for a maximum of 10 minutes before timing out.

New mail on node ORANGE from ORANGE::MRGATE::"MRGATE::SYSTEM"

        Stage 4 of the installation verification procedure for
        the Message Router VMSmail Gateway V3.1 successful

Shutting down Message Router VMSmail Gateway 



Shutting down Transfer Service



Shutting down Management Service




        The Message Router VMSmail Gateway V3.1 IVP completed successfully

        Installation of Message Router VMSmail Gateway  V3.1 completed at 09:35

        VMSINSTAL procedure done at 09:35




                                 3-10

                                                Installing the Gateway


If you performed the installation from the console medium, you are
asked to remove the distribution volume from the console device and
replace it with the console volume:

Please mount the console volume on ddcu:
Are you ready?

where ddcu is the device name that you specified in Step 1 of Section
3.2.

When you have replaced the console volume, type YES.

The system confirms that the console volume has been mounted, and then
exits from VMSINSTAL:

%MOUNT-I-MOUNTED, CONSOLE mounted on _ddcu:

          VMSINSTAL procedure done at hh:mm

$

Providing you have received the mail message from stage 4 of the IVP,
the installation was successful.  You must now complete the
installation as described in Section 3.4.

If you do not receive the mail message from stage 4, you must
re-install the Gateway.  If the IVP did not indicate the reason for
the failure of the installation, you can set VERIFY on the
installation procedure, so that the IVP displays more information on
your screen.

To set VERIFY on the Gateway installation procedure, use the following
command:

$ VFY$MB$MRGCVP=1

You then install the Gateway again in the usual way.



3.4  Completing the Installation

The following tasks complete your installation:

      o  Following the successful completion of the installation and
         the IVP, check the location of the software (described in
         Section 3.5).  The Gateway must then be configured as
         described in Message Router VMSmail Gateway Management Guide.
         If you do not configure the Gateway you will not be able to
         use it.


                                 3-11

Installing the Gateway


         If you do not want to configure the Gateway immediately,
         restart Message Router and other MAILbus products that you
         stopped, using the command:

         $ @SYS$MANAGER:MB$CONTROL START=(MS,DDS,TS,...,ER)

         You must restart MAILbus on every node in a cluster.

                                     NOTE

                 You must not start the Gateway until it is
                 configured.


      o  If you are upgrading from Version 2.0 or 2.1 of the Gateway,
         you must delete the following line from the system startup
         command file, (SYS$MANAGER:SYSTARTUP.COM or
         SYS$MANAGER:SYSTARTUP_V5.COM):

         $ @SYS$MANAGER:MRGATEST


      o  If you asked users to log out during the installation, you
         must now restore them.  Allow them to log in again by typing:

         $ SET LOGINS/INTERACTIVE=number

         where number is the number of interactive logins that you
         noted in Section 2.3.

         Use this command on every node in a cluster.

      o  Restart DECnet using the following command:

         $ @SYS$MANAGER:STARTNET

You must restart DECnet on each node in a cluster.















                                 3-12

                                                Installing the Gateway


3.5  Location of the Gateway Software

Figure 3-1 shows the directory structure of the Gateway software in
relation to other MAILbus software.

Figure 3-1:  Directory Structure of the MRGATE Account


                    MB$
                     |
  ______________________________________
  |       |        |        |          |                  
 MR      DDS      MB      TOOLS       MRG
                                       |
                                       |
 -----------------------------------------------------------
 |         |          |       |       |       |       |     |
 *.NBS  VMSERROR  MRGINIT MRGQUEUE MRTOVMS MRTOVMS MRTOVMS MRTOVMS
        .DAT      .DAT    .DAT     .COM    .EXE    .INF    .LOG


Of the files shown in [MB$.MRG], only VMSERROR.DAT, MRTOVMS.COM, and
MRTOVMS.EXE are installed during the installation procedure.  The
remaining files are created during the configuration or operation of
the Gateway.  If you are reinstalling or upgrading the Gateway, new
versions of VMSERROR.DAT, MRTOVMS.COM, and MRTOVMS.EXE are installed,
and the previous versions of the other files are left unaffected by
the installation procedure.  Then, during configuration, MRGINIT.DAT
is recreated, with new configuration data, or data from the previous
MRGINIT.DAT, depending on whether you specify that you want to keep
old data.

Initially, allow a disk quota of at least 6000 blocks for the MRGATE
account.  When required, the quota should be raised to allow for any
increase in the volume of message traffic.














                                 3-13

Installing the Gateway


Table 3-1:  Location of Gateway Files

Directory, Definition and File          Size   Protection(S,O,G,W)
---------------------------------------------------------------------

MB$dev1:[MB$.TOOLS]                   

MRGATE$CVP.DAT                          1      (RWED,RWED,RE,)
MB$MRGATE.COM                           3      (RWED,RWED,RE,RE)

MB$dev1:[MB$.MB.MB$COM]               

MB$MRG_ER.COM                           20     (RWED,RWED,RE,E)
MB$MRG_ERRORS.DAT                       4      (RWED,RWED,RE,E)

MB$dev1:[MB$.MB.MB$WORK]              

MB$MRG$CONFIG$CUSTOMIZED.DAT            5      (RWED,RWED,RE,RE)
MB$MRG$CONFIG$DEFAULT.DAT               5      (RWED,RWED,RE,RE)

MB$dev2:[MB$.MRG]                     

MRTOVMS.COM                             10     (RWED,RWED,RE,)
MRTOVMS.EXE                             1000   (RWED,RWED,RE,)
VMSERROR.DAT                            1      (RWED,RWED,RE,)

SYS$COMMON:[SYSHLP]                   

MRGATE031.RELEASE_NOTES                 ?      (RWED,RWED,RWED,RE)
MB$MRG_CONFIG.HLB                       28     (RWED,RE,RE,RE)

SYS$COMMON:[SYSLIB]                   

MRFROMVMS.EXE                           80     (RWED,RWED,RE,RE)

SYS$COMMON:[SYSMGR]                   

MB$$MRG_CONFIG.COM                      44     (RWED,RWED,RE,RE)
MB$$MRG_START.COM                       11     (RWED,RWED,RE,RE)
MB$$MRG_STOP.COM                        9      (RWED,RWED,RE,RE)
MB$START.COM                            4      (RWED,RWED,RE,RE)
MB$STOP.COM                             4      (RWED,RWED,RE,RE)
MRGATE$STOP.DAT                         1      (RWED,RWED,RE,RE)
MRGATEST.COM                            4      (RWED,RE,RE,RE)








                                 3-14

                                                Installing the Gateway


Directory, Definition and File          Size   Protection(S,O,G,W)
---------------------------------------------------------------------

SYS$COMMON:[SYSMSG]                   

MRGATE$MSG.EXE                          7      (RWED,RWED,RWED,RE)

SYS$COMMON:[SYSTEST.MB]               

MB$MRGCVP.COM                           29     (RWED,RE,RE,RE)

where MB$dev1 is the device where Message Router is installed and
MB$dev2 is the device where you have installed the Gateway.

The file sizes given in Table 3-1 are approximate only (if you have
just performed an upgrade or re-installation, some may differ
considerably) and do not take account of the disk space needed for
actual messages.  The file protection codes are the recommended
settings that are issued in the distribution kit.



3.6  After a MicroVAX Installation on MicroVMS

The Object and Shareable Image Libraries are needed only during the
installation of the VMSmail Gateway.  As they are not needed to run
the Gateway, disk space can be released by removing them from the
MicroVAX.  If the Gateway is not installed on a MicroVAX you do not
need to read this section.

To remove the libraries from your MicroVAX, first check that no-one is
using the software.  If it is not being used, log in to the SYSTEM
account and use the command procedure REMOVE.COM to remove the
MicroVMS options or suboptions that you have installed.

Complete the following steps:

      1  Log in to the SYSTEM account

      2  Invoke the REMOVE.COM command procedure as follows:

         $ @SYS$UPDATE:REMOVE

         The procedure prompts you for the name of the option or
         suboption you want to remove.  Depending on the size of the
         option you are removing, the procedure may take several
         minutes.  You cannot remove a suboption without first
         specifying the option in which it is contained.




                                 3-15

Installing the Gateway


When you have removed the software that you do not require, you have
no further tasks to perform.  You can now configure the Gateway as
described in the Message Router VMSmail Gateway Management Guide.



3.7  After a MicroVAX Installation on VMS Version 5.0

The Object and Shareable Image libraries are needed only during the
installation of the Gateway.  As they are not needed to run the
Gateway, you can release some disk space by removing them from the
MicroVAX.  If you did not install the Gateway on a MicroVAX, you do
not need to read this section.

To remove the libraries from your MicroVAX, first check that no one is
using the software.  If it is not being used, log in to the SYSTEM
account and use the VMS Tailoring Utility to tailor the software off
your MicroVAX.

Complete the following steps:

     1   Invoke VMSTAILOR in the following way:

         a   Log in to the SYSTEM account:

         b   Type the following command:

             $ SYS$UPDATE:VMSTAILOR

         c   The procedure starts and displays:

             This is the VMS tailoring utility. It lets you customize VMS 
             for your particular system. You do this by identifying 
             classes and subclasses of VMS files that you want to add or 
             delete. 

             VMSTAILOR has three phases:

                    - First, VMSTAILOR asks if you want to tailor your 
             system by adding files ("tailor on") or by deleting files 
             ("tailor off").

                    - Second, if you choose the "tailor on" procedure, 
             VMSTAILOR lists each class of VMS files and asks if you 
             want to include them on the system disk. If you choose the 
             "tailor off" procedure, VMSTAILOR lists each class of VMS 
             files and asks if you want to delete them from the system 
             disk.

                    - Third, VMSTAILOR carries out your instructions.


                                 3-16

                                                Installing the Gateway


             NOTE: To cancel VMSTAILOR during the first and second phases, 
             press Control-C, Control-Y, or Control-Z. If you cancel 
             VMSTAILOR during the third phase, you may end up with a 
             partially tailored disk.

             Do you want to tailor files "ON" or "OFF"? 


             Type OFF and press RETURN.


     2   The procedure displays:

         TAILOR-OFF
         ----------
         You will now be prompted with a list of the classes and 
         subclasses of VMS files that are optional. The size of each 
         class and subclass is included in the list. This will help 
         you decide whether or not you want to remove a class or subclass 
         from your system.

         Under some classes, there is a set of common files that is 
         required in order for any subclasses to work. These files will 
         only be deleted if you remove the ENTIRE class. If you choose 
         to keep any subclass, this set of files is not deleted.

         Total size of the system disk is nnnnnnn blocks.
         Total space used on the system disk is nnnnnnn blocks.
         Total space left on the system disk is nnnnnnn blocks.

         CLASS - Network support
                   Size of entire class (with subclasses): 1442
                   Size of common files required for any subclass: 1221
                   Do you wish to select the entire class (default = NO)?

         where nnnnnnn are numbers.

         Press RETURN to accept the default answer, because you do not
         want to remove the entire class.

     3   The procedure displays:

         Do you wish to select any of its subclasses (default NO)?

         Press RETURN to accept the default answer, because you do not
         want to remove any of the subclasses.

     4   The procedure displays:

         CLASS - Programming Support


                                 3-17

Installing the Gateway


                   Size of entire class (with subclasses): 9749
                   Size of common files required for any subclass: 0
                   Do you wish to select the entire class (default = NO)?

         Press RETURN to accept the default answer, because you do not
         want to remove the entire class.

         The procedure displays:

         Do you wish to select any of its subclasses (default = NO)?

         Type YES and press RETURN, because the Object and Shareable
         Image Libraries are a subclass of this class.

     5   The procedure displays:

         Select the subclasses that you wish to use:

         For each subclass, press RETURN except for the following
         subclass:

         SUBCLASS - Object and Shareable Image Libraries 
         (3480 blocks) [NO]:

         Type YES and press RETURN.

     6   For all the remaining classes and subclasses, accept the
         default answer NO, because you do not want to remove any of
         those classes or subclasses.

     7   The utility removes the selected subclass from your MicroVAX,
         and displays the names of the files that it is deleting.


When you have removed the software that you do not require you have no
further tasks to perform.  You can now configure the Gateway as
described in the Message Router VMSmail Gateway Management Guide.















                                 3-18













                              Appendix A

                          Distribution Media



This appendix contains a list of the files contained in the
installation savesets.

The files supplied in the installation saveset A are:


MRGATE$PROTN.COM
MRGATE$FILES.DAT
MRGATE$IMAGES.DAT
MRGATE$MSG.OBJ
KITINSTAL.COM
MRGATE$SYSGEN.DAT
MRGATE031.RELEASE_NOTES
MB$MRGCVP.COM
MRGATE.OLB
KOALA.OLB
DCF_BASE.OLB
DCF_TRANSLATE.OLB
DCF_MAIL_CONVERSIONS.OLB
DCF_DSAF.OLB
WPADOC.OLB
WPABASE.OLB
MRMIS.OLB
MRVMS.OLB
XPORT.OLB
MRGATE$LINK.COM
MRGATE$POSTPRO.COM










                                 A-1

Distribution Media


The files supplied in the installation saveset B are:


MB$MRG_CONFIG.HLB
MB$$MRG_CONFIG.COM
MB$MRG$CONFIG$CUSTOMIZED.DAT
MB$MRG$CONFIG$DEFAULT.DAT
MB$$MRG_START.COM
MB$$MRG_STOP.COM
MRGATEST.COM
MB$START.COM
MB$STOP.COM
MB$MRG_ER.COM
MB$MRG_ERRORS.DAT
MB$MRGATE.COM
MRTOVMS.COM
VMSERROR.DAT
MRGATE$STOP.DAT
MRGATE$CVP.DAT
MRGINIT.DAT
MB$CNFDB_IVP.DAT
MRINIT_0.DAT






























                                 A-2













                              Appendix B

  Sample Installation Procedure on VMS Version 4.6, 4.7, or MicroVMS



This appendix gives an example of the log of an installation and the
IVP.  It also gives an example of the test mail message sent through
the Gateway.

$ @sys$update:vmsinstal mrgate031 mta0:

        VAX/VMS Software Product Installation Procedure V4.6    
It is 8-APR-1988 at 19:35.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]?  Y
* Are you satisfied with the backup of your system disk [YES]? 

Please mount the first volume of the set on MTA0:.
* Are you ready?  Y
%MOUNT-I-MOUNTED, MR mounted on MTA0: (ORANGE)
The following products will be processed:
  Message Router VMSmail Gateway V3.1

        Beginning installation of Message Router VMSmail Gateway V3.1 at 19:37
%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been 
successfully moved to SYS$HELP.




* Do you want help text printed before every question [NO]? 
* Do you want to purge files replaced by this installation [YES]? 
* Do you want to run the IVP after the installation [YES]? 
* Do you want to keep data from a previous installation 
  of Message Router VMSmail Gateway  V2.*  [NO]? 
 

        You have answered all the questions for the Message Router


                                 B-1

Sample Installation Procedure on VMS Version 4.6, 4.7, or MicroVMS


        VMSmail Gateway installation.  Message Router VMSmail Gateway 
        is now being installed.  The installation will take 
        approximately 30 minutes depending on system configuration 
        and media type.

%MRGATE-I-MODACC, Modifying the MRGATE account
%MRGATE-I-CHECDIRS, Checking Directories

%VMSINSTAL-I-RESTORE, Restoring product saveset B...

%MRGATE-I-LNKMRGATE, Linking the VMSmail Gateway images
%MRGATE-I-LNKMRGTOVMS,  ...Linking the MRTOVMS image
%MRGATE-I-LNKMRGFRVMS,  ...Linking the MRFROMVMS image
%MRGATE-I-SETMRGFILES, Setting Message Router VMSmail Gateway file ownership 
and protection
%MRGATE-I-ASIGNMRGATE, Assigning Message Router VMSmail Gateway files to 
target directories

 The generation phase of the Message Router VMSmail Gateway installation 
 is now complete.

    In order to tailor the Message Router VMSmail Gateway to your requirements, 
    you must use the Message Router VMSmail Gateway configuration procedure, 
    SYS$MANAGER:MB$CONFIG.COM.

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


                   IVP   for   Message Router VMSmail Gateway 

                         Version 3.1

    This is the installation verification procedure (IVP) for the 
    Message Router VMSmail Gateway. It checks that the Gateway is 
    successfully installed on your system. 
  





==================================================================
        Message Router VMSmail Gateway Version V3.1 IVP

This verification procedure is in four stages: 

Stage 1 checks that all the Gateway files exist, and are the right size.

Stage 2 sets DECnet running if necessary. 


                                 B-2

    Sample Installation Procedure on VMS Version 4.6, 4.7, or MicroVMS


Stage 3 tests the Gateway by sending a mail message from VMSmail to
Message Router.  When this stage is complete, a message is displayed
on the screen. 

Stage 4 tests the Gateway by sending a mail message from Message 
Router to VMSmail.  When this stage is complete, you will receive a 
mail message. This message is sent to the account from which you are
performing the verification.

The verification procedure has not completed successfully
until you have seen both the screen message and the mail message. 





------------------------------------------------------------------
        Message Router VMSmail Gateway V3.1 file check
                       
        The total number of files is 19.
  
        All files exist and are the correct size.
        End of Message Router VMSmail Gateway V3.1 file check.
------------------------------------------------------------------
 Checking ORANGE VMSmail network response
Succeeded in activating VMSmail DECnet object 27 on node ORANGE

        Starting Management Service



        Starting Transfer Service



        Starting Message Router VMSmail Gateway 



        Stage 3 of the installation verification procedure for
        the Message Router VMSmail Gateway V3.1 successful

        Waiting for delivery of VMSmail sent through Gateway V3.1.

        The IVP waits for a maximum of 10 minutes before timing out.

New mail on node ORANGE from ORANGE::MRGATE::"MRGATE::SYSTEM"

        Stage 4 of the installation verification procedure for
        the Message Router VMSmail Gateway V3.1 successful


                                 B-3

Sample Installation Procedure on VMS Version 4.6, 4.7, or MicroVMS


Shutting down Message Router VMSmail Gateway 



Shutting down Transfer Service



Shutting down Management Service




        The Message Router VMSmail Gateway V3.1 IVP completed successfully

        Installation of Message Router VMSmail Gateway  V3.1 completed 
        at 09:35

        VMSINSTAL procedure done at 09:35

$ MAIL

You have 1 new message

MAIL>


From:   ORANGE::MRGATE::"MRGATE::SYSTEM" 20-APR-1988 12:28:30.77
To:     ORANGE::SYSTEM
CC:     
Subj:   Message Router VMSmail Gateway 3.1 IVP


To:     SYSTEM@ORANGE@MRGATE

 
 
This is a Gateway test message. 
 
If you receive this message, stage 4 of the verification
procedure has successfully completed.
 
All stages of the verification procedure have now 
completed successfully


MAIL> EXIT





                                 B-4













                              Appendix C

           Sample Installation Procedure on VMS Version 5.0



This appendix gives an example of the log of an installation.  It also
gives an example of the test mail message sent through the Gateway.

        Welcome to VAX/VMS V5.0    


Username:  SYSTEM
Password: 

        Welcome to VAX/VMS version V5.0 on node ORANGE
    Last interactive login on Friday, 12-JULY-1988 09:00
    Last non-interactive login on Thursday, 19-MAY-1988 20:01

$ @sys$update:vmsinstal mrgate031 mta0:  options n

        VAX/VMS Software Product Installation Procedure V5.0    
                It is 20-MAY-1988 at 13:06.
                Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.

* Do you want to continue anyway [NO]?  y
* Are you satisfied with the backup of your system disk [YES]? 

Please mount the first volume of the set on MTA0:
Are you ready?  YES
%MOUNT-I-MOUNTED, Message Router VMSmail Gateway mounted on _MTA0: (HSC1)
The following products will be processed:

  Message Router VMSmail Gateway V3.1

        Beginning installation of Message Router VMSmail Gateway V3.1 at 13:06

%VMSINSTAL-I-RESTORE, Restoring product saveset A ...



                                 C-1

Sample Installation Procedure on VMS Version 5.0


    Release Notes Options:

        1.  Display release notes
        2.  Print release notes
        3.  Both 1 and 2
        4.  Copy release notes to SYS$HELP
        5.  Do not display, print or copy release notes

* Select option [2]:  4

* Do you want to continue the installation?  y
%VMSINSTAL-I-RELMOVED , The product's release notes have been 
successfully moved to SYS$HELP.

        Product:      MR-VMSMAIL-GATEWAY
        Producer:     DEC
        Version:      3.1
        Release Date: 1-MAR-1988

* Does this product have an authorization key registered and
loaded?  y
* Do you want help text printed before every question [NO]? 
* Do you want to purge files replaced by this installation [YES]? 
* Do you want to run the IVP after the installation [YES]? 
* Do you want to keep data from a previous installation of 
Message Router VMSmail Gateway V2.*  [NO]?
 

        You have answered all the questions for the Message Router
        VMSmail Gateway installation.  Message Router VMSmail Gateway 
        is now being installed.  The installation will take 
        approximately 30 minutes depending on system configuration 
        and media type.

%MRGATE-I-CREACC, Creating the MRGATE account
%MRGATE-I-CHECDIRS, Checking Directories
%MRGATE-I-CREMBDIR, Creating directory DUA0:[MB$.MRG]

%VMSINSTAL-I-RESTORE, Restoring product saveset B ...

%MRGATE-I-LNKMRGATE, Linking the VMSmail Gateway images
%MRGATE-I-LNKMRGTOVMS,  ...Linking the MRTOVMS image
%MRGATE-I-LNKMRGFRVMS,  ...Linking the MRFROMVMS image
%MRGATE-I-LNKMRGMSG,  ...Linking the Message Router VMSmail Gateway 
message  image 
%MRGATE-I-SETMRGFILES, Setting Message Router VMSmail Gateway file ownership 
and protection
%MRGATE-I-ASIGNMRGATE, Assigning Message Router VMSmail Gateway files to 
target directories



                                 C-2

                      Sample Installation Procedure on VMS Version 5.0


 The generation phase of the Message Router VMSmail Gateway installation is 
 now complete.

    In order to tailor the Message Router VMSmail Gateway to your 
    requirements, you must use the Message Router VMSmail Gateway 
    configuration procedure, SYS$MANAGER:MB$CONFIG.COM.

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


                       IVP   for   Message Router VMSmail Gateway

                         Version 3.1

    This is the installation verification procedure (IVP) for 
    the Message Router VMSmail Gateway.

    It checks that the Gateway is successfully installed on your system. 
  

==================================================================
       Message Router VMSmail Gateway Version 3.1 IVP

This verification procedure is in four stages: 

Stage 1 checks that all the Gateway files exist, and are the right size.

Stage 2 sets DECnet running if necessary. 

Stage 3 tests the Gateway by sending a mail message from VMSmail to
Message Router.  When this stage is complete, a message is displayed
on the screen. 

Stage 4 tests the Gateway by sending a mail message from Message Router
to VMSmail.  When this stage is complete, you will receive a mail
message.  This message is sent to the account from which you are
performing the verification.

The verification procedure has not completed successfully
until you have seen both the screen message and the mail message. 

------------------------------------------------------------------
        Message Router VMSmail Gateway 3.1 file check

        The total number of files is 19.
        All files exist and are the correct size.
        End of MRG 3.1 file check.
------------------------------------------------------------------
 Checking ORANGE VMSmail network response


                                 C-3

Sample Installation Procedure on VMS Version 5.0


Succeeded in activating VMSmail DECnet object 27 on node ORANGE

        Starting Management Service


        Starting Transfer Service


        Starting Message Router VMSmail Gateway

        Stage 3 of the installation verification procedure for
        the Message Router VMSmail Gateway 3.1 successful

        Waiting for delivery of VMSmail sent through Gateway 3.1.

        The IVP waits for a maximum of 10 minutes before timing out.

New mail on node ORANGE from ORANGE::MRGATE::"MRGATE::SYSTEM"
        Stage 4 of the installation verification procedure for
        the Message Router VMSmail Gateway 3.1 successful

Shutting down Message Router VMSmail Gateway


Shutting down Transfer Service


Shutting down Management Service


        The Message Router VMSmail Gateway 3.1 IVP completed 
        successfully

        Installation of Message Router VMSmail Gateway V3.1 completed at 13:25

        VMSINSTAL procedure done at 13:26
















                                 C-4

                      Sample Installation Procedure on VMS Version 5.0


$ MAIL

You have 1 new message

MAIL>

From:   ORANGE::MRGATE::"MRGATE::SYSTEM" 12-JULY-1988 13:24:42.68
To:     ORANGE::SYSTEM
CC:     
Subj:   Message Router VMSmail Gateway 3.1 CVP

From:   NAME: SYSTEM <SYSTEM@MRGATE@ORANGE>
To:     SYSTEM@ORANGE@MRGATE


  
This is a Gateway test message. 
 
If you receive this message, stage 4 of the verification
procedure has successfully completed.
 
All stages of the verification procedure have now 
completed successfully

MAIL> EXIT



























                                 C-5



                                                                 INDEX


                                INDEX



Account quota                         sample, B-1, C-1
  changing, 2-6                       upgrade, 1-2, 3-8
  recommended, 2-6                  Installation Help, 3-1
Account Quotas, 2-4                 Installation verification
Audience                                procedure
  intended                            see IVP
    of this book, i                 Installing
                                      preparations, 2-3
BYTLM                                 the Gateway, 1-1
  account quota, 2-4                Intended audience
                                      of this book, i
Configuration, 1-2, 3-11            IVP, 1-2, 3-5, 3-9
Conventions
  used in this book, x              License Management Facility, 1-1
Customer Support, 1-3
                                    Message Router
Disk quota                            shutting down, 2-5
  recommended for installation,     MicroVAX
      2-1                             MicroVMS pre-installation check,
Distribution Medium                       2-12
  list of files, A-1                  post installation check, 3-15
Documents                             removing software, 3-15, 3-16
  related to this book, v             VMS 5.0 pre-installation
                                          checklist, 2-14
Error handling, 1-3                 MRGATE account
                                      directory, 3-6
FILLM
  account quota, 2-4                Preparing
Free blocks required, 2-4             MicroVAX running MicroVMS, 2-12
                                      VAXcluster, 2-10
Gateway                               VMS 5.0 systems, 2-14
  installing, 1-1, 3-1              Prerequisites
  introduction to, 1-1                MicroVAX software, 2-2
  upgrade, 3-5                      purging Files, 3-5
 
Handling errors, 1-3                Quotas
Help                                  accounts, 2-4
  while installing, 3-1
                                    Re-installing the Gateway, 2-9
Installation                        Related documents
  backup, 3-3                         to this book, v
  check list, 2-2                   Release Notes, 3-4
  completing, 3-11, 3-13            Removing software from a MicroVAX,
  Help, 3-5                             3-15, 3-16
  new, 1-2
  on-line release notes, 3-4        Shutting down


                               Index-1

INDEX


  Message Router, 2-5               VAXcluster
Software                              Gateway limitations, 2-10
  location, 3-13                      heterogeneous, 2-10
Software Product Description          homogeneous, 2-10
  see SPD                             preparing, 2-10
Software Versions, 1-1, 2-2         Versions
SPD, 2-1                              Software, 1-1, 2-2
Store-and-forward, 1-1              VMSINSTAL, 1-2
SYSUAF.DAT, 2-11                      command procedure, 3-1
                                      overview, 3-1
Tailoring Utility, 2-15, 3-16         parameters, 3-1
                                    VMSLICENSE, 1-1
User authorization file, 2-11       VMSTAILOR, 2-15, 3-16







































                               Index-2




                                        Message Router VMSmail Gateway
                                                    Installation Guide
                                                           AA-KR24B-TE
Reader's Comments

Please give us your comments and suggestions on this manual.  They
help us to improve the quality and usefulness of our publications.

      1  How would you rate this manual for:
                                                  good    fair    bad 
         Completeness of information:
         Accuracy of information:
         Clarity:
         Organization:

      2  Did you find errors in this manual?  Please specify by page
         and paragraph, or mark corrections on pages and attach copies
         to this form.
                                                  page    paragraph
         Information that is missing: 
         Information that is incorrect:
         Information that is hard to understand: 
         Information that is hard to find: 

      3  What suggestions do you have for improving this manual?



      4  Which parts of the manual are good at helping you understand
         the product?



      5  Please mark the descriptions that apply to you.

            _  Technical
            _  Nontechnical
            _  Management
            _  Nonmanagement
            _  Other (explain)

      6  How do you use this manual, e.g., as a reference, or to
         follow procedures?



Name                                            Title
Company
Street                                          City
State                   Zip                     Date


