














                    Message Router VMSmail Gateway


                           Management Guide







                             Version 3.0




















                    digital equipment corporation,
                        maynard, massachusetts




AA-KR25A-TE
First Printing, October 1987

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) 1987 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 to Managing the Gateway

        1.1     The Message Router VMSmail Gateway . . . . . . . . 1-1
        1.2     Message Formats  . . . . . . . . . . . . . . . . . 1-7
        1.2.1     VMSmail Message Format . . . . . . . . . . . . . 1-7
        1.2.2     Message Router Message Format  . . . . . . . . . 1-8
        1.3     Versions of the Gateway that Are Compatible with 
                Message Router   . . . . . . . . . . . . . . . . . 1-8
        1.4     Management Tasks . . . . . . . . . . . . . . . . . 1-8


CHAPTER 2       Configuring the Gateway

        2.1     The Gateway Configuration Procedure  . . . . . . . 2-1
        2.2     Configuration Parameters . . . . . . . . . . . . . 2-1
        2.3     Preparing for Configuration  . . . . . . . . . . . 2-2
        2.3.1     Default Values for the Gateway Configuration 
                  Parameters . . . . . . . . . . . . . . . . . . . 2-3
        2.3.2     Device Name  . . . . . . . . . . . . . . . . . . 2-4
        2.3.3     The Re-creation Interval for the Information Log 
                  File . . . . . . . . . . . . . . . . . . . . . . 2-4
        2.3.4     The Retry Interval . . . . . . . . . . . . . . . 2-5
        2.3.5     Maximum Number of Retries  . . . . . . . . . . . 2-5
        2.3.6     Re-submission Interval . . . . . . . . . . . . . 2-6
        2.3.7     Batch Queue  . . . . . . . . . . . . . . . . . . 2-6
        2.3.8     Delivery of Gateway Mail Errors  . . . . . . . . 2-7
        2.3.9     The Gateway Mailbox Password . . . . . . . . . . 2-7
        2.3.10    Exception Reporting  . . . . . . . . . . . . . . 2-7
        2.3.11    Critical Number of Blocks  . . . . . . . . . . . 2-8
        2.3.12    The Gateway Account Password . . . . . . . . . . 2-8
        2.4     Starting the Configuration . . . . . . . . . . . . 2-8
        2.5     Performing the Configuration . . . . . . . . . . . 2-9
        2.5.1     Performing a Default Configuration . . . . . .  2-10
        2.5.2     Performing a Customized Configuration  . . . .  2-12
        2.6     Enabling and Recovering the Gateway  . . . . . .  2-15
        2.7     Running the CVP  . . . . . . . . . . . . . . . .  2-16
        2.7.1     CVP Overview . . . . . . . . . . . . . . . . .  2-16
        2.7.2     How to Run the CVP . . . . . . . . . . . . . .  2-16
        2.8     Completing the Configuration . . . . . . . . . .  2-21



                                 iii




CHAPTER 3       Management Action Procedures

        3.1     Using the Gateway Management Action Procedures   . 3-1
        3.2     Exception Report from Network Management Node  . . 3-2
                MRG MAPs . . . . . . . . . . . . . . . . . . . . . 3-5


CHAPTER 4       Gateway Commands

        4.1     Configuration Commands . . . . . . . . . . . . . . 4-1
        4.1.1     Reconfiguring the Gateway  . . . . . . . . . . . 4-2
        4.1.2     Starting the Gateway . . . . . . . . . . . . . . 4-3
        4.1.3     Stopping the Gateway   . . . . . . . . . . . . . 4-4


CHAPTER 5       Monitoring the Gateway for Errors

        5.1     Overview . . . . . . . . . . . . . . . . . . . . . 5-1
        5.2     Running the Exception Reporting Routines 
                Interactively  . . . . . . . . . . . . . . . . . . 5-1
        5.3     Using The Gateway Information Log File . . . . . . 5-2
        5.3.1     SENT Status  . . . . . . . . . . . . . . . . . . 5-2
        5.3.2     INVALID ADDRESS Status . . . . . . . . . . . . . 5-3
        5.3.3     UNABLE TO SEND Status  . . . . . . . . . . . . . 5-4
        5.4     Errors Reported by the Gateway Information Log 
                File   . . . . . . . . . . . . . . . . . . . . . . 5-4


CHAPTER 6       Error and Non-Delivery Messages

        6.1     Introduction . . . . . . . . . . . . . . . . . . . 6-1
        6.2     Error Messages Received by Gateway Users . . . . . 6-1
        6.3     Non-Delivery Messages Received by Gateway Users  . 6-5
        6.3.1     Non-Delivery Message where the Route is too 
                  Complex for VMSmail  . . . . . . . . . . . . . . 6-5
        6.3.2     Non-Delivery Message Due to an Exceeded Retry 
                  Interval . . . . . . . . . . . . . . . . . . . . 6-7


APPENDIX A      Sample Configuration

        A.1     Log of Configuration . . . . . . . . . . . . . . . A-1


APPENDIX B      Operational Files







                                  iv




APPENDIX C      Gateway Files


INDEX


FIGURES

        1-1     Role of the Gateway When Sending ALL-IN-1 Mail to 
                a VMSmail User on the Same Node  . . . . . . . . . 1-3
        1-2     Role of the Gateway When Sending VMSmail to an 
                ALL-IN-1 User on Another Node  . . . . . . . . . . 1-5
        1-3     VMSmail Message Format . . . . . . . . . . . . . . 1-7


TABLES

        2-1     Default Configuration Parameters . . . . . . . . . 2-4
        5-1     MRTOVMS.INF Error Messages . . . . . . . . . . . . 5-4
        B-1     Gateway Operational Files  . . . . . . . . . . . . B-1
        C-1     List and Description of the Gateway Files  . . . . C-1































                                  v
















                               Preface



 Purpose of this Guide

 This book describes how to manage the Message Router VMSmail Gateway,
 Version 3.0.

 Management of the Gateway has changed from previous versions of the
 Gateway, because of the introduction of a new management tool, the
 MAILBUS configuration procedure MB$CONFIG.COM.  This book provides
 all the information required to manage the Gateway.



 Intended Audience

 This book is addressed to the Gateway manager who is responsible for
 maintaining the Message Router VMSmail Gateway on a network.  The
 manager must have working knowledge of:

  o  DECnet

  o  The local VMS operating system




 Related Documents

 Before reading this book, read the Message Router VMSmail Gateway
 Release Notes.  These release notes are provided on line when the
 Gateway is installed.  During installation they are copied into
 SYS$HELP:MRG030.RELEASE_NOTES.  If the Gateway is not installed on
 your system, see the Message Router VMSmail Gateway Installation
 Guide for information about reading or printing the release notes.





                                 vii

Preface


 This book assumes that the Message Router VMSmail Gateway is already
 installed on your system.

 Full details of the configuration commands used in this book can be
 found in the Message Router Management Reference Manual.

 You may also find the following books useful:

 Message Router VMSmail Gateway User's Guide

 Message Router VMSmail Gateway Installation Guide

 Introduction to MAILBUS

 Message Router Management Action Procedures

 VAX/VMS Command Language

 Messaging Network Manager's Supplement

 VAX/VMS DCL Concepts Manual

 VAX/VMS System Messages and Recovery Procedures Reference

 Figure 1 shows how to use the publications provided with the Message
 Router VMSmail Gateway.


























                                 viii

                                                               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


                                  ix

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.|
    ------------------------------------------------------
                                                          






                                  x

                                                               Preface















 Structure of this Book

 This book comprises six chapters and three appendixes:

  o  Chapter 1 explains why the Gateway is necessary and how mail is
     transferred through it.  The chapter also introduces the tasks
     needed to manage the Gateway.

  o  Chapter 2 describes how to use the MAILBUS configuration
     procedure to configure the Gateway.  It also describes the
     configuration verification procedure (CVP).

  o  Chapter 3 contains the Gateway Management Action Procedures
     (MAPs) that provide instructions for the tasks to be carried out
     when you receive an exception report message.  You are asked
     during configuration whether or not you want to use the exception
     reporting routines.

  o  Chapter 4 describes how you can use the MAILBUS configuration
     procedure to make changes to the configuration of the Gateway.

  o  Chapter 5 describes the Gateway Information Log File.  This file
     can be used as a means of managing the Gateway.  It records
     whether or not each message sent through the Gateway is delivered
     successfully by the Gateway.  For unsuccessful deliveries, a list
     of the known reasons for failures is provided.

  o  Chapter 6 describes the error and non-delivery messages that the
     users of the Gateway may receive.  It also describes the actions
     that can be taken to recover from these errors.

  o  Appendix A contains an example of a typical configuration.

  o  Appendix B contains a list of the operational Gateway files.





                                  xi

Preface


  o  Appendix C contains a list and description of all the Gateway
     files.




 How to Use this Book

 Read Chapters 1 and 2 to gain an understanding of how the Gateway
 works and the tools available to manage the Gateway.  These chapters
 also provide information about the tasks the Gateway manager has to
 carry out, and how to use the configuration procedure to perform
 these tasks.

 Read Chapter 3 for details of the recovery actions that you take when
 you receive an exception report generated by the exception reporting
 routines.

 Use this chapter by looking up the MAP number that you want.  Each
 exception report provides the number of the MAP you need to refer to.

 Read Chapter 4 when you want to use the configuration procedure to
 change the values of the parameters for the Gateway.

 Read Chapters 5 and 6 for details of the error and non-delivery
 messages your users can receive and the recovery actions to take when
 they do receive one of these messages.

 Refer to Appendix A for an example of the configuration procedure.

 Refer to Appendixes B and C for details and descriptions of the files
 that the Gateway uses.



 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.


                                  xii

                                                               Preface


 []              Brackets are used after configuration 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





































                                 xiii















                              Chapter 1

                 Introduction to Managing the Gateway



1.1  The Message Router VMSmail Gateway

The Message Router VMSmail Gateway package contains the Message Router
VMSmail Gateway (MRGATE) and Message Router.  The Gateway acts as an
interface between Message Router and VMSmail, as VMSmail cannot
exchange mail directly with Message Router.  Version 3.0 of the
Message Router VMSmail Gateway package runs on VMS Version 4.5 (or
later) or MicroVMS Version 4.5 (or later).

The Gateway can reside on any VMS or MicroVMS system that has Message
Router installed and is part of a messaging network.

VMSmail users must use the Gateway to exchange mail with users of any
Message Router Mail System.

VMSmail users can send mail directly to other VMSmail users without
using the Gateway.  However, a VMSmail user who wants to send mail to
another VMSmail user on a node that is temporarily unavailable, can
send the mail through the Gateway taking advantage of Message Router's
store-and-forward capability.

When you send a VMSmail message, the Gateway converts the message into
Message Router format (see Section 1.2) and then passes it to Message
Router for delivery.

When a message in Message Router format addressed to a VMSmail user
arrives at the Message Router on the recipients node, it is stored in
the Gateway mailbox, MRGATE.  A batch job, MRTOVMS, runs at intervals
specified at configuration.  MRTOVMS examines the Gateway mailbox, and
if there are messages awaiting delivery, the MRTOVMS batch job
collects the messages, translates them into VMSmail format, and then
passes them to VMSmail for delivery.





                                 1-1

Introduction to Managing the Gateway


If any node is temporarily not working or any mail system is
unavailable, Message Router stores the message until the node or
system becomes available again.

Figure 1-1 shows the role of the Gateway when an ALL-IN-1 user sends
mail to a VMSmail user on the same node.

Figure 1-2 shows the role of the Gateway when a VMSmail user sends
mail to an ALL-IN-1 user on another node.











































                                 1-2

                                  Introduction to Managing the Gateway


Figure 1-1:  Role of the Gateway When Sending ALL-IN-1 Mail to a
             VMSmail User on the Same Node



                     +------------+
                     |   ALL-IN-1 |
                     |   User     |
                     +------------+
                            |  
                            |  Message Router
                            V  Format
                            |
                     +-----------------+
                     |   ALL-IN-1      |
                     +-----------------+
                            |  
                            |  Message Router
                            V  Format
                            |
                     +-----------------+
                     |  Message Router |
                     +-----------------+
                            |  
                            |  Message Router
                            V  Format
                            |
                     +-----------------+      
                     |   MRGATE        | 
                     |   Mailbox       |
                     +-----------------+
                            |  
                            |  Message Router
                            V  Format
                            |
                     +----------------+
                     |  MRGATE        |
                     +----------------+
                            |
                            |  VMSmail
                            V  Format
                            |
                     +---------------+
                     |  VMSmail      |
                     +---------------+
                            |
                            |  VMSmail
                            V  Format
                            |


                                 1-3

Introduction to Managing the Gateway


			    |
                    +------------+ 
                    |  VMSmail   | 
                    |  User      | 
                    +------------+            
Key

----->-- Message Path
















































                                 1-4

                                  Introduction to Managing the Gateway


Figure 1-2:  Role of the Gateway When Sending VMSmail to an ALL-IN-1
             User on Another Node

                    +------------+ 
                    |  VMSmail   | 
                    |  User      | 
                    +------------+            
                            |
                            |  VMSmail
                            V  Format
                            |
                     +---------------+
                     |  VMSmail      |
                     +---------------+
                            |
                            |  VMSmail
                            V  Format
                            |
                     +----------------+
                     |  MRGATE        |
                     +----------------+
                            |
                            |  Message Router
                            V  Format
                            |
                     +---------------------+
                     |  Message Router     |
                     |  (on sender's node) |
                     +---------------------+
                            |
                            |  Message Router
                            V  Format
                            |
                     +------------------------+
                     |  Message Router        |
                     |  (on recipient's node) |
                     +------------------------+
                            |
                            |  Message Router
                            V  Format
                            |
                     +------------+
                     |   ALL-IN-1 |
                     |   Mailbox  |
                     +------------+
                            |
                            |  Message Router
                            V  Format
                            |



                                 1-5

Introduction to Managing the Gateway


                            |
                     +-----------------+
                     |   ALL-IN-1      |
                     +-----------------+
                            |
                            |  Message Router
                            V  Format
                            |
                     +------------+
                     |   ALL-IN-1 |
                     |   User     |
                     +------------+
Key

----->-- Message Path







































                                 1-6

                                  Introduction to Managing the Gateway


1.2  Message Formats

Mail messages are generated by both VMSmail and Message Router Mail
Systems, such as ALL-IN-1 Electronic Messaging.  VMSmail messages are
in VMSmail format, while the mail from a Message Router Mail System is
in Message Router format.



1.2.1  VMSmail Message Format

Figure 1-3 shows a typical VMSmail message, as it appears on the
recipient's screen.

Figure 1-3:  VMSmail Message Format


  
         #1        17-JUL-1987 9:10:11             MAIL   
     From:  APPLE::ASTON                                  
     To:    BANANA::BARNES                                
     Subj:  Monthly Sales Meeting                         
                                                          
     Richard                                              
                          The monthly sales meeting has   
     been postponed until Wednesday 10-30 a.m.  I'm sorry 
     if this causes you any trouble.                      
                                                 Gary.    
                                                          
     MAIL>                                                
 



The message consists of three parts, called fields:
    
    From:              contains the address of the sender, which 
                       is supplied by the VMSmail program

    To:                contains the name of the addressee(s) and 
                       is specified by the sender

    Subj:              contains the subject of the message and 
                       is specified by the sender


These three fields are together known as the message header.  The
message text is the main body of the message entered by the sender and
displayed below the message header.



                                 1-7

Introduction to Managing the Gateway


1.2.2  Message Router Message Format

Message Router format is a format that Message Router uses when
transferring messages between mail systems.  Message Router protocol
dictates the sequence of fields that make up a message while it is
being transferred, for example:

      o  The TO field, which identifies the recipient(s) of the
         message

      o  The FROM field, which identifies the sender of the message


Message Router transfers the message, in Message Router format, across
the network.  The user does not see the message while it is in Message
Router format.  The local mail system, based on Message Router,
translates the message from Message Router format into the local
presentation format.  The user can then read the message, in local
format, on the terminal screen or as hardcopy.



1.3  Versions of the Gateway that Are Compatible with Message Router

If you have a Gateway Version 2.0 or 2.1 installed on your network, it
can be used by Message Router Version 3.0.  However, the Gateway
Version 3.0 will not operate unless there is a Message Router Version
3.0 installed on your network.

It is recommended that you upgrade to Version 3.0 of the Gateway.



1.4  Management Tasks

To manage the Gateway you need to:

      o  Find out from your Message Router manager what type of
         configuration you are running, that is, default or
         customized, and ensure that the configuration is completed
         successfully (see Chapter 2).

      o  Examine the exception reports and carry out the recovery
         procedures described in the relevant Management Action
         Procedures (MAPs) (see Chapter 3).

         If you choose not to use the exception reporting routines,
         you must manage the Gateway manually using the information
         log file (see Chapter 5).



                                 1-8

                                  Introduction to Managing the Gateway


      o  Monitor the Gateway and make any necessary changes to the
         configuration (see Chapter 4).

      o  Examine the Gateway's information log file periodically (see
         Chapter 5).

      o  Handle error and non-delivery messages reported by your users
         (see Chapter 6).












































                                 1-9















                              Chapter 2

                       Configuring the Gateway



2.1  The Gateway Configuration Procedure

The Gateway cannot be used until it has been configured successfully.

The installation procedure installs the Gateway files on your system
and builds the directory structure, but does not have enough
information about the Gateway to tailor it fully to your requirements.
The Gateway configuration procedure, which is part of the MAILBUS
configuration procedure (see the Introduction to MAILBUS), completes
the tailoring of your system.

This chapter describes how to configure the Gateway for the first
time, and provides the default values that are supplied for the
configuration parameters.

If you have already configured the Gateway, and you want to make
changes to your configuration, read Section 4.1.

If you want more information about the configuration procedure
including the configuration commands, refer to the Message Router
Management Reference Manual.



2.2  Configuration Parameters

You can configure some parameters of the Gateway to suit your system
requirements.  These parameters are saved in an initialization file,
which is constructed from your answers to questions asked during the
configuration procedure (see Section 2.5).  You can run the
configuration procedure at any time to change these parameters.  Refer
to Chapter 4 for more information about changing the configuration
parameters.




                                 2-1

Configuring the Gateway


You can configure the following Gateway parameters:

      o  The device used by the Gateway.

      o  The interval for re-creating a new information log file.

      o  The time period after which the Gateway stops trying to send
         a message, before generating a non-delivery notification, and
         deleting it.

      o  The maximum number of times an attempt is made to send a
         message, before a non-delivery notification is sent, and the
         message is deleted.

      o  The re-submission interval for the MRTOVMS command procedure.

      o  The batch queue on which the MRTOVMS command procedure is
         re-submitted.

      o  Whether or not you want the MRTOVMS error message to be
         forwarded through VMSmail to the MBMANAGER account.

      o  The password for the Gateway mailbox.

      o  Whether or not you want to enable exception reporting.  If
         you decide to enable exception reporting, you will also have
         the option to set the minimum number of free blocks the
         Gateway requires.

      o  The password for the Gateway account.

A description of these parameters can be found in Sections 2.3.2 to
2.3.11.



2.3  Preparing for Configuration

Before running the configuration procedure, as described in Section
2.5, complete the following checklist:

      o  Find out from your Message Router manager what type of
         configuration you are running, that is, default or
         customized.  You are only able to customize the Gateway
         configuration if Message Router is using a customized
         configuration.  Similarly, if Message Router is using a
         default configuration, the Gateway is configured using the
         default configuration.




                                 2-2

                                               Configuring the Gateway


         The configuration procedure asks only a subset of the
         configuration questions for a default configuration.

         The type of configuration is displayed when you invoke the
         configuration procedure using MB$CONFIG (see Section 2.5).

      o  Decide, using the table in Section 2.3.1, which default
         configuration parameter values are acceptable for your
         network, and which parameter values you need to change during
         configuration.

      o  Stop the MAILBUS components on your node.  Log in to the
         system account and type:

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

      o  If DECnet is not running on your system, ask your DECnet
         manager to set it up and start it in the usual way.
         Typically DECnet is started using the command:

         $ @SYS$MANAGER:STARTNET

         DECnet must be started on each node in a cluster.

Turn to Section 2.3.1 for details of the default values that are
assigned to the Gateway configuration parameters.



2.3.1  Default Values for the Gateway Configuration Parameters

This section describes the parameters and their initial default
values.  Once you make changes to the parameters, the new value
becomes the default.

If you are using a default configuration, you need only decide on
acceptable values for three parameters:

      o  Gateway device

      o  Gateway mailbox password

      o  Gateway account password

      o  The critical number of blocks for the Gateway

The parameters that you cannot customize take the default values that
are shown in Table 2-1.




                                 2-3

Configuring the Gateway


Table 2-1:  Default Configuration Parameters

OPTION                                               DEFAULT
----------------------------------------------------------------------

The Gateway device                                   Gateway Installed
                                                     Device
Re-creation interval for the information log file    7 days
Non-delivery notification period                     4 days
Maximum number of retries                            350
Re-submission interval                               15 minutes
Batch queue name                                     MB$BATCH
The Gateway mail errors to be sent through VMSmail   Yes
Enable exception reporting                           Yes
Critical number of free blocks                       6000

You can find a description of the parameters for the default
configuration in the following sections.



2.3.2  Device Name

The device used for the Gateway is requested during configuration.  If
the configuration procedure can identify a device, this is offered as
a default.

The default device offered as a default is the device where the
Gateway is installed.



2.3.3  The Re-creation Interval for the Information Log File

The information log file, MRTOVMS.INF, is re-created at the interval
that you specify at configuration.  This keeps the size of the file
manageable.  The information log file is described in Chapter 5 of
this book.

The default interval is seven days.  Enter the time in delta time
format, dd-hh:mm:ss, where:

      o  dd is the number of days

      o  hh is the number of hours

      o  mm is the number of minutes





                                 2-4

                                               Configuring the Gateway


      o  ss is the number of seconds

For example 7-00:00:00 represents the interval of seven days.  You
must enter the time in delta time format.

Refer to the VAX/VMS DCL Concepts Manual for more details of the time
formats.

This parameter is related to the retry interval (Section 2.3.4) and
the maximum number of retries (Section 2.3.5).  These parameters must
be considered together when working out suitable values for them.



2.3.4  The Retry Interval

The Gateway stops trying to send a message to VMSmail after an
interval that you specify at configuration.  The Gateway then sends a
non-delivery notification to the message originator and deletes the
message from the message queue.

The default interval is four days.  Enter the time in the delta time
format, dd-hh:mm:ss, where:

      o  dd is the number of days

      o  hh is the number of hours

      o  mm is the number of minutes

      o  ss is the number of seconds

For example 4-00:00:00 represents the interval of four days.  You must
enter the time in delta time format.

Refer to the VAX/VMS DCL Concepts Manual for more details of the time
formats.

This parameter is related to the maximum number of retries (Section
2.3.5) and the re-creation interval for the information log file
(Section 2.3.3).  These parameters must be considered together when
working out suitable values for them.



2.3.5  Maximum Number of Retries

The Gateway tries to send a message to VMSmail a number of times
specified at configuration.  The Gateway then sends a non-delivery
notification to the message originator and deletes the message from


                                 2-5

Configuring the Gateway


the message queue.

The default number of retries is 350.

This parameter is related to the retry interval (Section 2.3.4) and
the re-creation interval for the information log file (Section 2.3.3).
These parameters must be considered together when working out suitable
values for them.



2.3.6  Re-submission Interval

The MRTOVMS.COM command procedure is submitted to the batch queue on a
schedule at the interval specified at configuration.  You should
always see the following entry on the batch queue, if the Gateway is
started.

Jobname    Username   Entry   Status
MRTOVMS    MRGATE     nnnn    Holding until dd-mmm-yyyy hh:mm

where nnnn is the entry number of the MRTOVMS batch job and
dd-mmm-yyyy hh:mm:ss is the date and time, in combination time format,
when the job next executes.

Refer to the VAX/VMS DCL Concepts Manual for details of the time
formats.

The following are examples of the possible values of the re-submission
interval:

      o  +00:15:00 represents a re-submission interval of 15 minutes

      o  +01:30:00 represents a re-submission interval of one and a
         half hours

The re-submission interval is initially set to a default of 15 minutes
and must be entered in combination time format.



2.3.7  Batch Queue

The MRTOVMS.COM command procedure is automatically submitted on the
batch queue specified at configuration.

The default batch queue is MB$BATCH.  This is the logical name of the
batch queue.  If you provide a logical name, it should be a system
logical name.  Where you have a generic queue (for a cluster), the
logical name must be defined on all nodes.


                                 2-6

                                               Configuring the Gateway


2.3.8  Delivery of Gateway Mail Errors

MRTOVMS indicates that it has found an error by forwarding a mail
message to the MBMANAGER account through a route other than Message
Router.  If you receive one of these messages, examine the Gateway
information log file for further information (see Chapter 5).

The default is that this message is sent through VMSmail.  If you
choose not to have this error message forwarded through VMSmail, there
is no message sent.

The following is an example of the mail message you receive from
MRTOVMS:
                             
From:   ORANGE::MRGATE       22-OCT-1987 17:14
To:     ORANGE::MBMANAGER
Subj:   VMSmail Gateway produced an error




2.3.9  The Gateway Mailbox Password

Choose the password that you want to assign to the Gateway mailbox.
The password must be from 8 to 12 alphanumeric characters, inclusive,
and does not appear when you type it.  Do not include any blank
characters or tabs in the password.

You are advised to change the password frequently.



2.3.10  Exception Reporting

The exception reporting routines monitor your network for errors and
unusual events.  The Management Action Procedures (MAPs) specify tasks
to help you recover from these errors (see Chapter 3).

If you want to take advantage of the MAPs, enable exception reporting
when you configure; otherwise, manage the Gateway manually, using the
Gateway information log file.

Exception reporting is enabled by default.









                                 2-7

Configuring the Gateway


2.3.11  Critical Number of Blocks

This is the minimum number of blocks required by the Gateway if it is
to run successfully.  When the number of free blocks on the device or
the free quota falls below this minimum number, and you have enabled
exception reporting, an exception report is sent to the network
management node.  If quotas are not enabled, the exception reporting
routines do not check the available quota.

The default minimum number of blocks is 6000.



2.3.12  The Gateway Account Password

If you want to change the password, choose the password that you want
to assign to the Gateway account.  The password must be from 8 to 31
alphanumeric characters, inclusive, and does not appear when you type
it.  Do not include any blank characters or tabs in the password.

An account password is assigned to the Gateway account automatically
during installation.



2.4  Starting the Configuration

This section explains how to configure the Gateway.  You must first
prepare for configuration as described in Section 2.3.
The configuration procedure is interactive and takes you step by step
through the configuration.  Each step is fully described in Section
2.5.  Remember that you can get on-line help by typing a question mark
(?) in response to a prompt.

If you are configuring a cluster, run the configuration procedure on
each node where you installed the Gateway.  For example, if you have
installed the Gateway once on the cluster, you only need configure the
Gateway once on the node where you installed it.

If possible, use a hardcopy terminal to keep a record of the
configuration.  If you do not have a hardcopy terminal, you can make a
record of the configuration using the following command:

$ SET HOST 0/LOG=filename

where filename is the name of the file that you want to contain the
record of the configuration.





                                 2-8

                                               Configuring the Gateway


2.5  Performing the Configuration

Complete the following steps to configure the Gateway:

      1  Log in to the SYSTEM account and invoke the configuration
         procedure in the following way:

         $ @SYS$MANAGER:MB$CONFIG

         MB$CONFIG announces itself and displays the current date and
         time (dd-mmm-yyyy hh:mm:ss), its prompt, and the type of
         configuration (config_type).  The type of configuration is
         either DEFAULT or CUSTOMIZED.
          
                MAILBUS CONFIGURATION PROCEDURE

         Products currently defined in config_type configuration database
         on dd-mmm-yyyy hh:mm:ss

                 
                MR      : Message Router
          
                        MS      : Management Service
          
                        TS      : Transfer Service
          
                        DDS     : Directory Service
          
                        ER      : Exception Reporting
          
                A1      : ALL-IN-1
          
                MRG     : MRGATE
           
                       
         MBC>


                                     NOTE

                 It takes a few minutes to display the table
                 of all the MAILBUS components on your system.

         If you do not want to take advantage of the ALL-IN-1
         Electronic Messaging Subsystem exception reporting routines,
         or you do not have the ALL-IN-1 Electronic Messaging
         Subsystem installed on your node, ignore the A1 identifier in
         the display of products currently defined in the
         configuration database.



                                 2-9

Configuring the Gateway


         If you do want to use the ALL-IN-1 Electronic Messaging
         Subsystem exception reporting routines, see the Messaging
         Network Manager's Supplement.

      2  If you need to create your Gateway configuration file, enter
         the following command:

         MBC> CREATE MRG

         The procedure responds with the following message, indicating
         that it has created the Gateway configuration database.

         %MB-I-MBC$CREATE, Creating new configuration data file


      3  Type:

         MBC> SET MRG

         The procedure responds:

         %MB-I-MBC$SET, Setting configuration parameters


The procedure prompts you to answer a series of questions.  If you are
performing a default configuration, turn to Section 2.5.1.  If you are
performing a customized configuration, turn to Section 2.5.2.



2.5.1  Performing a Default Configuration

This section takes you step by step through the default configuration
questions.

      1  The configuration procedure displays:

         * What device do you want to use for MRGATE [ddcu:] ?

         Type the name of the device and press RETURN, or press RETURN
         to accept the default device.

      2  The configuration procedure displays:

         * Do you wish to modify the MRGATE mailbox password [N]?

         If you do not want to change the Gateway mailbox password,
         press RETURN; otherwise, type YES and press RETURN.




                                 2-10

                                               Configuring the Gateway


      3  If you have answered NO to Step 2, the configuration
         procedure continues at Step 5; otherwise the procedure
         displays:

         * What password do you want for the MRGATE mailbox [] ?

         Enter the password you want to assign to the Gateway mailbox
         and press RETURN.

         The password must be from 8 to 12 characters, inclusive, and
         is not displayed as you type it.

      4  The configuration procedure displays:

         Please confirm

         * What password do you want for the MRGATE mailbox [] ?

         Re-type the password.  If the password that you type here is
         not the same as the password that you typed in Step 3, the
         configuration procedure displays an error message and returns
         to Step 3.

      5  The configuration procedure displays:

         * What alarm level of free blocks do you want to set for
         MRGATE [6000] ?

         Type the alarm level of blocks you want to set for Gateway,
         or press RETURN to accept the default.

      6  The configuration procedure displays:

         * Do you wish to modify the MRGATE account password [N]?

         If you do not want to change the Gateway account password,
         press RETURN; otherwise, type YES and press RETURN.

      7  If you have answered NO to Step 6, the configuration
         procedure continues at Step 9; otherwise, the procedure
         displays:

         * What password do you want for the MRGATE account [] ?

         Enter the password you want to assign to the Gateway account
         and press RETURN.

         The password must be from 8 to 31 characters, inclusive, and
         is not displayed as you type it.



                                 2-11

Configuring the Gateway


      8  The configuration procedure displays:

         Please confirm

         * What password do you want for the MRGATE account [] ?

         Re-type the password.  If the password that you type here is
         not the same as the password that you typed in Step 7, the
         configuration procedure displays an error message and returns
         to Step 7.

      9  After you have completed entering the configuration
         parameters, you must enable and recover the Gateway, and then
         run the configuration verification procedure (CVP).  The CVP
         checks that the current configuration of the Gateway is
         correct.  See Section 2.6 for details about enabling and
         recovering the Gateway, and Section 2.7 for details of how to
         run the CVP.




2.5.2  Performing a Customized Configuration

This section takes you step by step through the customized
configuration questions.

      1  The configuration procedure displays:

         * What device do you want to use for MRGATE [ddcu:] ?

         Type the name of the device and press RETURN, or press RETURN
         to accept the default device.

      2  The configuration procedure displays:

         * How often do you want to create a new information file
         (specify a delta-time) [7-00:00:00] ?

         Type the interval you want to specify for the creation of the
         information log file, or press RETURN to accept the default.

      3  The configuration procedure displays:

         * For how long (in delta-time format) do you want MRGATE to
         keep trying to send a message [4-00:00:00] ?

         Type the period over which you want the Gateway to keep
         trying to send a message before issuing a non-delivery
         notification, or press RETURN to accept the default.


                                 2-12

                                               Configuring the Gateway


      4  The configuration procedure displays:

         * How many times do you want MRGATE to try sending a message
         [350]?

         Type the number of times you want the Gateway to try to send
         a message before issuing a non-delivery notification, or
         press RETURN to accept the default.

      5  The configuration procedure displays:

         * How often do you want MRTOVMS to run (specify a combination
         time) [+00:15:00]?

         Type the interval you want to specify for resubmitting
         MRTOVMS to the batch queue, or press RETURN to accept the
         default.

      6  The configuration procedure displays:

         * Which batch queue do you want MRTOVMS to use [MB$BATCH] ?

         Type the batch queue that you want MRTOVMS to use, or press
         RETURN to accept the default.

      7  The configuration procedure displays:

         * Do you want to send MRTOVMS error messages by VMSmail to
         the network manager [Y] ?

         Type NO if you do not want MRTOVMS error messages to be sent
         to the network manager by VMSmail, or press RETURN to accept
         the default of YES.

      8  The configuration procedure displays:

         * Do you wish to modify the MRGATE mailbox password [N] ?

         If you do not want to change the Gateway mailbox password,
         press return; otherwise, type YES and press return.

      9  If you have answered NO to Step 8, the procedure continues at
         Step 11; otherwise the procedure displays:

         * What password do you want for the MRGATE mailbox [] ?

         Enter the password you want to assign to the Gateway mailbox
         and press RETURN.




                                 2-13

Configuring the Gateway


         The password must be from 8 to 12 characters, inclusive, and
         is not displayed as you type it.

     10  The configuration procedure displays:

         Please confirm

         * What is the MRGATE mailbox password []?

         Re-type the password.  If the password that you type here
         does not correspond with the password that you types in Step
         9, the configuration procedure displays an error message and
         returns to Step 9.

     11  The configuration procedure displays:

         * Do you want to enable MRGATE exception reporting [Y] ?

         If you do not want to enable exception reporting, type NO and
         press RETURN; otherwise, press RETURN to accept the default
         answer of YES.

     12  If you have answered NO to Step 11, the configuration
         procedure continues at Step 13(); otherwise, the
         configuration procedure displays:

         * What alarm level of free blocks do you want to set for
         MRGATE [6000] ?

         Type the alarm level of blocks you want to set for the
         Gateway, or press RETURN to accept the default.

     13  The configuration procedure displays:

         * Do you wish to modify the MRGATE account password [N]?

         If you do not want to change the Gateway account password,
         press return; otherwise type YES and press return.

     14  If you have answered NO to Step 13, the procedure continues
         at Step 16; otherwise the procedure displays:

         * What password do you want for the MRGATE account [] ?

         Enter the password you want to assign to the Gateway account
         and press RETURN.

         The password must be from 8 to 31 characters,inclusive, and
         is not displayed as you type it.



                                 2-14

                                               Configuring the Gateway


     15  The configuration procedure displays:

         Please confirm

         * What password do you want for the MRGATE account [] ?

         Re-type the password.  If the password that you type here
         does not correspond with the password that you typed in Step
         14, the configuration procedure displays an error message and
         returns to Step 14.

     16  After you have completed entering the configuration
         parameters, you must enable and recover the Gateway, and then
         run the configuration verification procedure (CVP).  The CVP
         checks that the current configuration of the Gateway is
         correct.  See Section 2.6 for details about enabling and
         recovering the Gateway, and Section 2.7 for details of how to
         run the CVP.




2.6  Enabling and Recovering the Gateway

This section describes the tasks you must carry out to enable and
recover the Gateway.  When you have performed these tasks, you can run
the CVP as described in Section 2.7 to check the configuration.  Then
start the Gateway if the configuration is successful.

To enable and recover the Gateway, you use the configuration
procedure:

      1  Enable the Gateway by typing:

         MBC> ENABLE MRG

         The configuration procedure displays:

         %MB-I-MBC$ENABLE, Enabling messaging process


      2  Recover the Gateway:

         MBC> RECOVER MRG

         The configuration procedure displays:

         %MB-I-MBC$RECOVER, Recovering configuration database
         %MB-I-CREMRGINI, Creating initialization file for MRGATE ...
         %MB-I-UPDMRGMBX, Updating TS mbx directory database for MRGATE...


                                 2-15

Configuring the Gateway


         %MB-I-UPDXRPTENBF, Updating MB Exception Reporting flag for MRGATE...
         %MB-I-MBC$REPLETE, Configuration database recovery complete


      3  Exit from the configuration procedure:

         MBC> EXIT

Once you have recovered the Gateway, you can run the CVP as described
in Section 2.7.



2.7  Running the CVP

2.7.1  CVP Overview

The configuration verification procedure (CVP) checks that the Gateway
has been configured correctly.

Run the CVP when you make changes to the configuration database using
the configuration procedure.  The CVP checks that the new
configuration is correct.

The CVP uses the operational configuration to check the configuration
parameters, so Message Router must already be configured correctly
before the Gateway CVP can run successfully.

A successful CVP means that the Gateway is ready to use.  The CVP
produces a message to confirm that all the parameters of the
configuration are correct.

                                 NOTE

        As the CVP uses the operational configuration to check
        the configuration parameters, you may find that
        messages that were awaiting delivery before
        configuring the Gateway are delivered while the CVP is
        running, and before you receive your test mail message
        indicating that the CVP is successful.




2.7.2  How to Run the CVP

If possible, use a hard copy terminal to keep a record of the CVP.  If
you do not have a hard copy terminal, you can make a record of the CVP
as described in Section 2.4.  To run the CVP, complete the following
steps:


                                 2-16

                                               Configuring the Gateway


      1  Log in to the SYSTEM account.

      2  Start the Transfer Service by typing:

         $ @SYS$MANAGER:MB$CONTROL START=TS

         Use this command on every node in a cluster.

      3  Start the Gateway by typing:

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

         Use this command on every node in a cluster.

      4  Invoke the CVP, by typing:

         $ @SYS$TEST:MB$MRGCVP

         The following is an example of the output generated by the
         CVP.

         The configuration verification procedure announces itself as
         follows:


         ==================================================================

                Message Router VMSmail Gateway Version V3.0 CVP

         This verification procedure is in four stages: 

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

         Stage 2 checks that DECnet is running. 

         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. 






                                 2-17

Configuring the Gateway


         ------------------------------------------------------------------
                MRG V3.0 file check


                The total number of files is 18.
                All files exist and are the correct size.
                End of MRG V3.0 file check.
         ------------------------------------------------------------------

          Checking ORANGE VMSmail network response
         Succeeded in activating VMSmail DECnet object 27 on node ORANGE

         Starting Management Service



                Stage 3 of the configuration verification procedure for
                the Message Router VMSmail Gateway V3.0 successful


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

                The CVP waits for a maximum of mm minutes before timing out.

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

                Stage 4 of the configuration verification procedure for
                the Message Router VMSmail Gateway V3.0 successful
                                        
         Shutting Management Service


         where mm is a variable number of minutes that the CVP waits
         for, before timing out.  The number of minutes that the CVP
         waits, depends on the MRTOVMS resubmission interval.

      5  Before shutting down the Transfer Service and the Gateway,
         you must wait for the test mail message from stage four of
         the CVP to arrive.  This confirms that the Gateway has been
         configured correctly.

         The test mail message appears on your screen like any other
         mail message.









                                 2-18

                                               Configuring the Gateway



         $
         New mail on node nodename from nodename::MRGATE::"MRGATE::SYSTEM"
         $ mail
         You have 1 new message.

         MAIL> 

             #1          08-OCT-1987 12:33:19                                     NEWMAIL
         From:  nodename::MRGATE::"MRGATE::SYSTEM"
         To:    MRGATE::"nodename::SYSTEM"
         Subj:  Message Router VMSmail Gateway V3.0


          
          
         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> ex

         where nodename is the name of the node on which you are
         configuring the Gateway.

      6  If you do not receive a mail message within the MRTOVMS
         timeout period, reconfigure the Gateway.  (See Chapter 4).
         It is possible that the Gateway is in the process of
         delivering a large message.  If you think this might be the
         case, run the CVP again.  If your CVP message is still not
         delivered, reconfigure the Gateway.

         If the CVP fails again, you are advised to stop the Transfer
         Service and the Gateway, as described in Steps 7 and 8, and
         contact:

          -  Your Customer Support Center, if you have a Basic or a
             DECsupport contract

          -  Your local DIGITAL office to arrange for a service
             contract, if you do not have a Basic or a DECsupport
             contract






                                 2-19

Configuring the Gateway


      7  After receiving the test mail message, stop the Gateway by
         typing:

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

         You see the following displayed, when you stop the Gateway:


         Working, please wait ... 




         Beginning STOP operation for MRG.
         MRGATE shutdown procedure has completed.


         $

      8  Stop the Transfer Service by typing:

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

         The following is displayed when the Transfer Service is
         stopped:


         Working, please wait ... 




         Beginning STOP operation for TS.

         Beginning Transfer Service user shutdown procedure.
         stopping user talkers

         Transfer Service user shutdown procedure has completed.
                 This is MRMAN V3.0

         Transfer Service shutdown procedure has completed.


         $


      9  If you requested that DECnet was started for the
         configuration, you must now request that it is stopped.  Ask
         your DECnet manager to shut down DECnet by typing:



                                 2-20

                                               Configuring the Gateway


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

Read Section 2.8 to complete the configuration.



2.8  Completing the Configuration

In order to complete the configuration, you must edit the
site-specific start-up file, SYSTARTUP.COM, to include the Gateway.

If you are installing the Gateway on a single node, edit the startup
command file, SYS$MANAGER:SYSTARTUP.COM, and add the Gateway
identifier, MRG, as follows:

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

This ensures that the Gateway is automatically restarted whenever the
system is rebooted.

                                 NOTE

        Do not include the equivalent MB$CONTROL STOP command
        in the system stop file, SYS$SYSTEM:SHUTDOWN.COM.


If you are configuring the Gateway on a VAXcluster, you must edit the
node-specific startup command file on every node that runs the
Gateway, to include the above command.  If you are running a
homogeneous cluster that shares the same Gateway database, you can
edit the cluster-wide startup command file instead.

When you have successfully completed configuring the Gateway, log in
to the SYSTEM account and restart MAILBUS, including the Gateway,
using the following command:

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

Use this command on every node in a cluster.











                                 2-21















                              Chapter 3

                     Management Action Procedures



3.1  Using the Gateway Management Action Procedures

The Management Service component of Message Router contains a set of
exception reporting routines that monitor your Message Router network
and look for potential problems and errors.

If an exception reporting routine finds a problem on a node, it
generates a report, saying what the problem is and giving any
necessary details.  All the reports for each node are collected into a
report message, which is sent by VMSmail to the MBMANAGER account on
the network management node.  The command procedures use VMSmail to
send the report message to make sure that the problem is reported,
even if the Transfer Service is not working.

The network management node is monitored by the Message Router
manager.  Network management tasks are performed on this node.

Carry out the task on the node that sent the exception report, unless
the MAP tells you otherwise.

On the following pages is an example of a Gateway report message.  The
first page of the report is a summary.  Subsequent pages of the report
message can include more details of the error.














                                 3-1

Management Action Procedures


3.2  Exception Report from Network Management Node

The following is an example of an exception report forwarded from the
network management node.
From:   ORANGE::SYSTEM       13-OCT-1987 17:32
To:     ORANGE::MBMANAGER
Subj:   Exception report from ORANGE


THIS MESSAGE REPORTS 1 EXCEPTION CONDITION ON YOUR NETWORK

         REPORTED FROM NODE ORANGE - MR VERSION V3.0
                 ON 13-OCT-1987 AT 17:32


Summary
-------

1:   INVLOGIN - Node ORANGE VMS account for VMSmail and NCP settings do not correspond
        For further action, refer to MAP MRG 13
        Further details follow.































                                 3-2

                                          Management Action Procedures


1: Further details
------------------

%DCL-E-OPENIN, error opening ORANGE::"27=" as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node















End of Report
-------------





























                                 3-3

Management Action Procedures


When you receive a report, read the message and turn to the
appropriate Management Action Procedure (MAP) for each report.

There is a MAP to follow for each problem, which leads to a solution
in the form of tasks to carry out.  Tasks are graded to show the level
of difficulty.  They range from one star (*) for an easy task, to
three stars (***) for a difficult task requiring detailed knowledge of
the product.  The gradings are as follows:




Rating *        The task does not require you to make any decisions. 
                Full instructions are given in the MAP.
  
Rating **       The task requires you to make simple decisions 
                based on information provided or information
                you find by following the instructions given in
                the MAP.  

Rating ***      The task requires a little knowledge of the Gateway.
                You have to make decisions based on information you 
                are given, on information you find by following the 
                MAP, or on knowledge of the product.

Rating ****     The task requires detailed knowledge of the Gateway
                and other products in the network. You have to make 
                decisions based on this knowledge.



Some of the MAPs describe problems that are not problems in the
Message Router VMSmail Gateway.  You may need to ask for help from
other managers in your network, such as the VMS system manager or the
Message Router manager.  The MAPs tell you what you need to ask the
relevant manager to do.

If you think the task is too difficult, contact your internal support
department or DIGITAL for assistance.  To get help from DIGITAL,
contact either:

      o  Your Customer Support Center, if you have a Basic or a
         DECsupport contract

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






                                 3-4

                                                             MAP MRG 1


MRG MAPs

MAP MRG 1


NODEVICE - Device <device> used by MRG is not online

where <device> is the name of the device that is off line.



Task 1 *

The device may be off line for maintenance.  If you do not know why
the device is off line, ask the VMS system manager



Task 2 *        

When the VMS system manager has told you that the device has been put
on line again, start the Gateway.

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

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

Use this command on every node in a VAXcluster.
























                                 3-5

MAP MRG 2


MAP MRG 2


NOLOGICAL - Logical name <name> is not defined.  MRGATE checks not 
            performed

BADLOG - Logical name <name> is incorrect.  MRGATE checks not performed

where <name> is the logical name and is one of:

      o  MRG$DIR for the Gateway directory

      o  MAIL$PROTOCOL_MR for the Gateway image

      o  MRGATE which directs mail to Message Router

      o  MB$ROOT which identifies the location of the exception
         reporting files


The logical named in the error message is incorrectly defined.



Task 1 *        

If the logical name given in the error message is MB$ROOT, carry out
Task 2.  Otherwise, define the logicals by restarting the Gateway.

To restart the Gateway, log in to the SYSTEM account and type the
following command:

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

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



Task 2 *

Check with the Message Router manager on the node that exception
reporting routines can be started.  If the Message Router manager has
not stopped the exception reporting routines deliberately, restart
them as follows.  Log in to the SYSTEM account and type:

$ @SYS$MANAGER:MB$CONTROL START=ER

Use this command on every node in a VAXcluster.




                                 3-6

                                                             MAP MRG 3


MAP MRG 3


DEVFULL - Device <device> used by MRG is full
   
DEVLOW - Device <device> used by MRG has insufficient free space

where <device> is the name of the device used by the Gateway.



Task 1 **       

Try to free more space on the device specified in the error message.

      1  Log in to the SYSTEM account and use the following command to
         examine the device:

         $ SHOW DEVICE device

         where device is the name of the device displayed in the error
         message.

         The number of free blocks on the device is displayed.

      2  Purge the directory and subdirectories of any extra log files
         by typing the command:

         $ PURGE MRG$DIR:*.LOG /LOG

         This command displays a list of the files that are purged.


If, after purging your files, you still do not have sufficient space,
ask your Message Router manager if the same device is used by Message
Router.  If it is, ask the Message Router manager to purge the Message
Router files in the same way (see the Message Router Management Action
Procedures).  If there is still not sufficient space, tell the VMS
system manager that there is not enough free space on the device.













                                 3-7

MAP MRG 4


MAP MRG 4


LOWQUO - Account MRGATE on <device> is running out of quota

INSUFQUO - Account MRGATE has insufficient quota on <device>


where <device> is the name of a device used by the Gateway.

The Gateway has either run out of quota or is running out of quota on
the specified device.



Task 1 **       

Try to free some space on the device specified in the error message.

      1  Log in to the Gateway account and examine the state of the
         quota by using the command:

         $ SHOW QUOTA/DISK=device

         where device is the name of the device you are investigating.

         Note the quota still available.

      2  Use the DIRECTORY command to find out if there are many log
         files in the system:

         $ DIR MRG$DIR:*.LOG

         Purge the existing log files by typing:

         $ PURGE MRG$DIR:*.LOG /LOG

         This command displays a list of the files that are purged.

      3  Examine the quota again.  If you still do not have enough
         room on the device, tell the VMS system manager that you need
         an increased disk quota.










                                 3-8

                                                             MAP MRG 5


MAP MRG 5


NODBF - MRG database file <filename> missing

where <filename> is the name of the missing file.

A Gateway configuration file is missing; recover the Gateway database
as described in Task 1.



Task 1 *

Run the configuration procedure using the RECOVER command, as follows:

      1  Log in to the SYSTEM account

      2  Stop MAILBUS by typing:

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

      3  Run the configuration procedure with the RECOVER option by
         typing:

         $ @SYS$MANAGER:MB$CONFIG RECOVER MRG

      4  Restart MAILBUS by typing:

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

         Use this command on every node in a VAXcluster.




















                                 3-9

MAP MRG 6


MAP MRG 6


MRGSTOP - MRGATE has been stopped

The Gateway has been stopped by someone using the MB$CONTROL STOP
command.



Task 1 *        

Find out why the Gateway has been stopped.

Find out if the Gateway has been stopped deliberately or accidentally.
If there is a reason for it being stopped, wait until it can be
restarted, and then follow the instructions in Task 2.  If it has been
stopped by mistake, you can start it immediately, as described in Task
2.

This error may have occurred if the system startup failed before the
Gateway started.



Task 2 *        

Start the Gateway to resubmit MRTOVMS to the batch queue.  Log in to
the SYSTEM account and type the following command:

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

Use this command on every node in a VAXcluster.



















                                 3-10

                                                             MAP MRG 7


MAP MRG 7


CONNECFAIL - Connection to node <remotenode> - VMSmail object 27

LINKABORT - Node <localnode> connection aborted to <remotenode>

LINKEXIT - Node <localnode> exited connection to <remotenode>

where:

      o  <localnode> is the name of the node trying to make a DECnet
         connection to a remote node

      o  <remotenode> is the name of the node that the local node is
         trying to connect to


The local node could not be connected to the remote node specified in
the error message.  This happens occasionally, and DECnet recovers
from the problem.



Task 1 *        

If any of these problems occurs frequently, contact your DECnet or
system manager and find out why network access to VMSmail on the
remote node is not available.























                                 3-11

MAP MRG 8


MAP MRG 8


DEVNOTMOUNT - DECnet not running locally on node <nodename>
              
DNR - DECnet not running locally on node <nodename>
              
where <nodename> is the name of the network management node.



Task 1 *        

Find out why DECnet is not running on the local node.  If there is no
special reason, ask the DECnet manager to restart DECnet.





































                                 3-12

                                                             MAP MRG 9


MAP MRG 9

   
OLDMG - Old messages are still held in MRGATE

Included as additional information in the exception report containing
this message, is a VMS list of the messages held in the MRTOVMS queue.

Excess messages may be in the queue for one of the following reasons:

      o  There may not be an entry for the MRTOVMS command file on the
         batch queue.  This should already be reported.  Follow the
         instructions for NOBAT in MAP MRG 10.

      o  The system logical for the Gateway directory is not defined.
         This should already be reported.  Follow the instructions for
         NOLOGICAL in MAP MRG 2.


The Gateway stores messages until it can deliver them to the VMSmail
recipient.  In doing so, it may receive two types of error message:

      1  Unrecoverable - the message can never be delivered:  for
         example, "INVALID ADDRESS".  The Gateway dequeues the message
         and sends a non-delivery message to the sender.

      2  Recoverable - for example, the node could not be reached.
         The Gateway stores the message and tries to deliver the
         message later.


Therefore, at any time, there may be messages in the Gateway waiting
for delivery to nodes that are not available.  If you think a message
should not be stored in the Gateway, examine the Gateway Information
Log File as described in Task 2.



Task 1 *        

Follow the instructions for NOBAT, MRG 10, or NOLOGICAL, MRG 2, where
the appropriate error has been reported.



Task 2 ***      

Examine the Gateway Information Log File.




                                 3-13

MAP MRG 9


Look at the Gateway Information Log File, MRTOVMS.INF, for any
messages that have not been sent.  To do this, log in to the SYSTEM
account and display the information file by typing:

$ TYPE MRG$DIR:MRTOVMS.INF

The undelivered messages have a status of "unable to send" as shown in
the example below.

+1 Msg 03130131407891/116@RED, attempt 2, on 13-APR-1987 11:35:28.18
           unable to send  : BLUE::BLOGGS    error 1 = 007E802A
-1 Msg 03130131407891/116@RED (0 days old)


Make a note of the 8-digit error status.  In the example, the error
status is 007E802A.  Error 1 indicates that the Gateway was unable to
make a connection to the remote node.

To find out why the message is stuck in the Gateway, type the
following command:

$ SET MESSAGE SYS$MESSAGE:CLIUTLMSG
$ EXIT %X007E802A


Substitute the error status that you noted previously for 007E802A.

The output from this command gives the reason why the message is still
in the Gateway, for example:
      
MAIL-E-LOGLINK, network error creating link to node !AS

where !AS is the node name or the node number of a node to which a
link cannot be created.

Read Chapter 5 for details of the error messages and how to recover
from the error if you receive one of these messages.

If the message identifies a problem with the destination node that you
were unaware of, tell the VMS system manager of the destination node
about the problem.











                                 3-14

                                                            MAP MRG 10


MAP MRG 10


NOBAT - MRTOVMS is missing from the batch queue


The MRTOVMS.COM entry is missing from the queue.  There should always
be an entry for MRTOVMS on the batch queue.



Task 1 ***      

Resubmit the MRTOVMS.COM job on the batch queue.

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

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

         This submits MRTOVMS to the batch queue.  Use this command on
         every node in a VAXcluster.

      2  There is no problem if this error occurs only occasionally,
         but if this message appears regularly, the jobs are failing
         for a specific reason; for instance, the batch job may have
         been aborted by the operator.  You can identify this reason
         by examining your MRTOVMS.LOG file:

         $ TYPE MRG$DIR:MRTOVMS.LOG;*

         The following is an example of the contents of the file.  The
         reason for failure, in this case, is that the Gateway cannot
         access the initialization file, MRGINIT.DAT, on the device
         provided.

         Job MRTOVMS (Queue MB$BATCH, entry 1627) holding until 13-OCT-1987 14:37
         Message Router -- VMSmail Gateway V3.0
         %MRGATE-F-BADINITFILE, Error MRGINIT.DAT initialization file
         -SYSTEM-W-NOSUCHDEV, no such device available
         -RMS-F-DEV, error in device name or inappropriate device type for 
         operation
         $      exit     ! 0
           MRGATE       job terminated at 13-OCT-1987 14:21:28.09

           Accounting information:
           Buffered I/O count:          159      Peak working set size:  1051
           Direct I/O count:            191      Peak page file size:    1193
           Page faults:                1300      Mounted volumes:           0
           Charged CPU time:     0 00:00:42.84   Elapsed time:   0 00:02:22.08
            


                                 3-15

MAP MRG 10


         In this case, the solution is to recover the Gateway using
         the configuration procedure, MB$CONFIG.


















































                                 3-16

                                                            MAP MRG 11


MAP MRG 11


NOSUCHNODE - Node <remotenode> is not known at node <localnode>


where:

      o  <remotenode> is the name of the remote node

      o  <localnode> is the name of the local node




Task 1 *        

The DECnet database on the remote node does not have a correct entry
for the local node.  Ask the VMS system manager or DECnet manager to
make sure that the DECnet database is up to date.
































                                 3-17

MAP MRG 12


MAP MRG 12


UNREACHABLE - Node <nodename> not currently available


where <nodename> is the name of a node



Task 1 *        

DECnet is not able to make a link to the specified node.  This may
happen occasionally, and DECnet should recover from the problem.  If
this error message occurs frequently, tell the VMS system manager or
the DECnet manager.




































                                 3-18

                                                            MAP MRG 13


MAP MRG 13



INVLOGIN - Node <localnode> VMS account for VMSmail and NCP settings do 
not correspond

NOSUCHOBJ - Node <localnode> does not know VMSmail object 27


where <localnode> is the name of the node trying to make a DECnet
connection to another node.

The local node could not be connected to the remote node detailed by
the error message.  This happens occasionally and DECnet recovers from
the problem.



Task 1 *        

Contact your DECnet or VMS system manager and find out why network
access to VMSmail is not available on <localnode>.





























                                 3-19

MAP MRG 14


MAP MRG 14


REMRSRC - Insufficient resources at node <remotenode> to process connection from node <localnode>

where:

      o  <remotenode> is the name of the remote node

      o  <nodename> is the name of the node trying to make the
         connection




Task 1 *        

There are too many processes on the remote node; wait until one of the
processes has finished.  If the problem is occurring frequently, carry
out Task 2.



Task 2 *

Ask your VMS manager to increase the either or both the SYSGEN
parameters, MAXPROCESSCNT and PAGEDYN, on the node to enable more
processes to be active on the node.  This increased SYSGEN parameters
do not take effect immediately, you will have to wait until the system
is rebooted.






















                                 3-20

                                                            MAP MRG 15


MAP MRG 15


SWVERS - Incompatible software version <version> on node <nodename> 

where:

      o  <version> is the version of the Gateway that is incompatible

      o  <nodename> is the name of the node that is running the
         incompatible version of the Gateway




Task 1 *

This error message might have been reported as an exception condition
in Message Router.  Ask the Message Router manager if this SWVERS
error has been reported and if he has recovered from it.  If he has
not recovered from this error, carry out Task 2.



Task 2 *

The node specified in the message cannot be monitored for exception
conditions by the Message Router Version 3.0 system.

Reinstall the Message Router VMSmail Gateway V3.0 on the node as
described in the Message Router VMSmail Gateway Installation Guide.
This task has a rating of ***.




















                                 3-21

MAP MRG 16


MAP MRG 16


NOCNFDB - No configuration database set up on node <nodename>

where <nodename> is the name of the node that does not have a
configuration database.



Task 1 *

This error message might have been reported as an exception condition
in Message Router.  Ask the Message Router manager if this SWVERS
error has been reported and if he has recovered from it.  If he has
not recovered from this error, carry out Task 2.



Task 2 ***

Ask the VMS system manager to retrieve the database from a backup
copy.

The name of the configuration file is given by the translation of the
logical MB$CNFDB.  Use the following commands to identify the database
name:

$ @SYS$MANAGER:MB$LOCATION
$ SHOW LOGICAL MB$CNFDB

Re-apply any changes known to have been made to the database since it
was backed up.

Carry out Task 2.



Task 2 *

Ask the Message Router manager, and the Gateway manager of other any
Gateways included in the system to re-apply any changes known to have
been made to the database since it was backed up.  Use the MB$CONFIG
SET and RECOVER commands to do this.








                                 3-22

                                                            MAP MRG 17


MAP MRG 17

This MAP explains how to recover from the error OLDMR, described in
the Message Router Management Action Procedures, where messages have
been in the Gateway mailbox queue for more than two hours.  Once a
message has been in the mailbox queue for more than two hours, the
Gateway assumes that an error has occurred.



Task 1 **       

The reason for the blocked queue may already be reported.  See whether
any other error reports relating to this error have been reported, and
follow the instructions accordingly.
                  


Reconfigure the Gateway using the RECOVER command of the configuration
procedure.              

      1  Log in to the SYSTEM account.

      2  Stop MAILBUS by typing:

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

      3  Run the configuration procedure with the RECOVER option by
         typing:

         $ @SYS$MANAGER:MB$CONFIG RECOVER MRG

      4  Restart MAILBUS by typing:

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

         Use this command on every node in a VAXcluster.

If this task does not solve the problem, contact your support center
or DIGITAL.












                                 3-23

MAP MRG 18


MAP MRG 18

This MAP explains how to recover from the error BADIDENT, described in
the Message Router Management Action Procedures.  This error message
indicates that the Gateway attempted to connect to Message Router but
could not be identified.  This may be due to an incorrect password for
the Gateway mailbox, or incorrect ownership of the mailbox.



Task 1 *        

Redefine the Gateway password and mailbox entry using the RECOVER
option of the configuration procedure.

      1  Log in to the SYSTEM account

      2  Stop MAILBUS by typing:

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

      3  Run the configuration procedure with the RECOVER option by
         typing:

         $ @SYS$MANAGER:MB$CONFIG RECOVER MRG

      4  Restart MAILBUS by typing:

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

         Use this command on every node in a VAXcluster.





















                                 3-24

                                                            MAP MRG 19


MAP MRG 19

This MAP explains how to recover from the error NORETADR, described in
the Message Router Management Action Procedures, where a service
message could not be delivered to the Gateway mailbox.



Task 1 *        

Redefine the Gateway mailbox entry using the RECOVER option of the
configuration procedure.

      1  Log in to the SYSTEM account

      2  Stop MAILBUS by typing:

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

      3  Run the configuration procedure with the RECOVER option by
         typing:

         $ @SYS$MANAGER:MB$CONFIG RECOVER MRG

      4  Restart MAILBUS by typing:

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

         Use this command on every node in a VAXcluster.























                                 3-25















                              Chapter 4

                           Gateway Commands



This chapter briefly describes the commands that are available with
the configuration procedure, and how they can be used to reconfigure
the Gateway.  A more detailed description of the commands can be found
in the Message Router Management Reference Guide.

The chapter also describes how to start and stop the Gateway (see
Sections 4.1.2 and 4.1.3).



4.1  Configuration Commands

The configuration procedure has the following commands:

      o  CREATE, which builds a configuration data file for either a
         default or customized configuration.  This data file is not
         implemented until you use the RECOVER command.

      o  DISABLE, which indicates to the exception reporting routines
         and the system that a component is not started.

         This command is not implemented until you use the RECOVER
         command.

      o  ENABLE, which indicates to the exception reporting routines
         and the system that a component is started.

         This command is not implemented until you use the RECOVER
         command.

      o  HELP, which provides on-line Help about the configuration
         commands.





                                 4-1

Gateway Commands


      o  RECOVER, which implements the current data file produced from
         a CREATE, SET, ENABLE, or DISABLE command.

      o  SET, which allows you to change parameters previously entered
         in the data file.  These changes are not implemented until
         you use the RECOVER command.

      o  SHOW, which displays the settings in the current
         configuration data file.




4.1.1  Reconfiguring the Gateway

You can use the configuration procedure if you want to change the
values of the Gateway configuration parameters for any reason.  You
may also want to reconfigure the Gateway if the CVP indicates that the
configuration has failed.

     1.  Log in to the system account and type:

         $ @SYS$MANAGER:MB$CONFIG

     2.  Display the existing values for the Gateway parameters by
         typing:

         MBC> SHOW MRG

         The configuration procedure displays the parameter values for
         your current configuration.

         If you are using a default configuration, the configuration
         procedure displays the subset of the parameters.  The
         remaining configuration parameters take the values specified
         in Section 2.3.1.

     3.  Use the SET command to set the parameter value that you want
         to change.  Type:

         MBC> SET MRG

         Accept the default values for all the parameters, except
         those you want to change.  Enter the new value for the
         parameter you are changing.

         Any new parameter values that you set are not used in the
         Gateway system until you have used the RECOVER command.




                                 4-2

                                                      Gateway Commands


     4.  Use the ENABLE command if you want to use the exception
         reporting routines for the Gateway.  Type:

         MBC> ENABLE MRG

         You must recover the configuration database to implement this
         command.

     5.  Use the DISABLE command if you do not want to use the
         exception reporting routines for the Gateway.  Type:

         MBC> DISABLE MRG

         You must recover the configuration database to implement this
         command.

     6.  Use the RECOVER command to implement the new parameter values
         input when using the SET, ENABLE or DISABLE commands.  Type:

         MBC> RECOVER MRG

     7.  Exit from the configuration procedure.  Type:

         MBC> EXIT




4.1.2  Starting the Gateway

You use the MB$CONTROL START command to start the Gateway.

      1  Log in to the SYSTEM account

      2  Type:

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















                                 4-3

Gateway Commands


         The following is an example of the message that is displayed
         when you start the Gateway:

           
         Working, please wait ... 




         Beginning START operation for MRG.
         Job MRTOVMS (queue MB$BATCH, entry nnnn) started on MB$BATCH_ORANGE
         MRGATE startup procedure has completed.

         $

You can edit the site-specific start-up file, SYSTARTUP.COM, to
include the Gateway.  The Gateway is then started automatically if the
system is rebooted.



4.1.3  Stopping the Gateway

You use the MB$CONTROL STOP command to stop the Gateway.

      1  Log in to the SYSTEM account

      2  Type:

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

         The following is an example of the message that is displayed
         when you stop the Gateway:


         Working, please wait ...




         Beginning STOP operation for MRG.
         MRGATE shutdown procedure has completed.

         $

Do not include the MB$CONTROL STOP command in the system shutdown
file, SYS$SYSTEM:SHUTDOWN.COM.





                                 4-4













                              Chapter 5

                  Monitoring the Gateway for Errors



5.1  Overview

The Gateway information log file, MRTOVMS.INF, in the MRG$DIR
directory should be monitored to help the Gateway run smoothly.  It is
also useful as a means of identifying a problem if you are not running
the exception reporting routines.

If you find or suspect that there is an error in the Gateway, you can
run the exception reporting routines interactively to find out more
information.



5.2  Running the Exception Reporting Routines Interactively

You can run the Gateway exception reporting routines interactively on
the node where you suspect there is an error.

Before running the exception reporting routines interactively, use the
configuration procedure SHOW command to display the current parameter
values for the Gateway.  You need to compare the current parameter
values with the status report generated by the exception reporting
routines, to determine whether or not there are errors.

To run the exception reporting routines, log in to the MBMANAGER
account on the suspect node, and type:

$ @MB$ROOT:[MB$COM]MB$MRG_ER

As the exception reporting routines run, they display messages on your
terminal screen indicating any errors they find.

Error messages for the Gateway are described in Chapter 6.  The
description of the error will, in most cases, describe the recovery
procedure that you should follow.


                                 5-1

Monitoring the Gateway for Errors


5.3  Using The Gateway Information Log File

MRTOVMS.INF logs traffic from Message Router to VMSmail.  It contains
an entry for each attempt to send a message.  Here is an example of an
entry:
  

+1 Msg 24821117207891/125@PLUM, attempt 1, on 06-OCT-1987 11:29:16.04
        sent            : LEMON::JONES
        sent            : APPLE::SMITH
        invalid address : PINEAPPLE::BLOGGS    error1 = 007E802A
        unable to send  : PEAR::BARNES    error2 = 07E2072
-1 Msg 24821117207891/125@PLUM (0 days old) 


+1 and -1 show the first and last lines of the log entry.  The number
(in this case, 1) is incremented and decremented as messages are
processed.

The first line of the entry shows the message identification, the
number of attempts made to send it, and the current date and time.
Subsequent lines show the name of each addressee, and the status of
the message.

The information file contains three types of status entry:

      o  SENT, if the message is delivered successfully

      o  INVALID ADDRESS, if the address does not exist

      o  UNABLE TO SEND, if the message could not reach the addressee




5.3.1  SENT Status

Sent, followed by an address, means that the message reached this
recipient.  For example:


sent            : LEMON::JONES










                                 5-2

                                     Monitoring the Gateway for Errors


5.3.2  INVALID ADDRESS Status

Invalid address, followed by an address, means that the Gateway could
not handle the address given.  For example:


invalid address : PINEAPPLE::BLOGGS    error1 = 007E802A

Check that the form of the address is correct.  In this example, the
address is illegal because the nodename, PINEAPPLE, has more than 6
characters.

error1 indicates which error prevented the Gateway making a connection
to the node.

The 8-digit hexadecimal number gives you more information about the
error.  The number points to an error message in the VMSmail error
message file, SYS$MESSAGE:CLIUTLMSG.EXE.  A summary of the error can
be found in the MRTOVMS.INF file.  The errors that you are most likely
to see are described in Section 5.4.  If you receive messages other
than these, they can be looked up as described below.

To look up the error message, type:

$ SET MESSAGE SYS$MESSAGE:CLIUTLMSG
$ EXIT %Xnumber

where number is the 8-digit hexadecimal number given in the
information file.  You can do this from an unprivileged account.  The
following example shows an 8-digit hexadecimal number and its
corresponding error message.

$ EXIT %X007E802A

%MAIL-E-LOGLINK, error creating network link to node !AS

where, in this example, !AS represents the name of the node that
cannot be reached.  The nodename is given in the same line as the
hexadecimal number.  In this case, !AS represents the nodename
PINEAPPLE.

The string !AS may not always represent a nodename, but it always
represents information contained on the same line of MRTOVMS.INF as
the hexadecimal number.  The Gateway is not able to translate this
string because it is not provided with enough information from
VMSmail.

See the VAX/VMS System Messages and Recovery Procedures Reference
Manual or Section 5.4 for more information about these error messages.



                                 5-3

Monitoring the Gateway for Errors


5.3.3  UNABLE TO SEND Status

Unable to send, followed by an address, means that the Gateway is
unable to forward the message to this recipient.  For example:

unable to send  : PEAR::BARNES    error2 = 07E2072 

error2 indicates that the error occurred after the connection was made
when attempting to hand the message over to VMSmail.  Look up the
error number as described in Section 5.3.2.



5.4  Errors Reported by the Gateway Information Log File

Table 5-1 shows the most frequently occurring errors in the
MRTOVMS.INF file.

Table 5-1:  MRTOVMS.INF Error Messages

Hexadecimal  Message
Number     
---------------------------------------------------------------------

000020F4     %SYSTEM-F-LINKEXIT, network partner exited
007E10A2     %MAIL-E-OPENOUT,error opening !AS as output
007E10FA     %MAIL-E-SYNTAX, error parsing '!AS'
007E1130     %MAIL-W-TEXT, !AS
007E2072     %MAIL-E-PROTOCOL, network protocol error
007E802A     %MAIL-E-LOGLINK, error creating network link to node !AS
007E8102     %MAIL-E-NOSUCHUSR, no such user !AS at node !AS


An explanation of each of these errors is described below.

      o  000020F4 translates to the following error message:

         %SYSTEM-F-LINKEXIT, network partner exited


         For example:

                 unable to send  : GRAPE::PIKE    error1 = 000020F4   

         or:

                 unable to send  : GRAPE::PIKE    error2 = 000020F4





                                 5-4

                                     Monitoring the Gateway for Errors


         The Gateway was forced to timeout, because VMSmail did not
         respond within the timeout period.  This error may occur
         either when the connection is made or when the message is
         transferred.  However, VMSmail may have received the message
         and because Message Router continues to try and send the
         message, two copies of the message may be delivered.

         This occurs only on heavily loaded nodes where response times
         are slow.

      o  007E10A2 translates to the following error message:

         %MAIL-E-OPENOUT, error opening !AS as output


         For example:

                unable to send  : RODGERS    error2 = 07E10A2   


         A problem occurred when attempting to open a mail file for
         user RODGERS.  This may indicate that the user's disk quota
         has been exceeded.

      o  007E10FA translates to the following error message:

         %MAIL-E-SYNTAX, error parsing '!AS'


         This may occur for two reasons.

          -  For example:

                invalid address : 'APPLE::RODGERS'    error1 = 007E10FA 


             This error occurs when an incorrect address string is
             used.  In the example, the syntax of the address is
             incorrect because it includes unnecessary quotes.  The
             incorrect syntax is noted in the MRTOVMS.INF file.

          -  For example:

                invalid address : MRGATE    error1 = 007E10FA   

             It is not possible to send a message just to the Gateway,
             you must send a message to a VMSmail user.  The Gateway
             generates a non-delivery message for this error.




                                 5-5

Monitoring the Gateway for Errors


      o  007E1130 translates to the following error message:

         %MAIL-W-TEXT, !AS

         For example:

                invalid address : APPLE::RODGERS    error1 = 007E1130 


         This error occurs when user RODGERS does not exist on node
         APPLE or because user RODGERS has the VMSmail autoforwarding
         facility set up in a loop.  It causes a Gateway non-delivery
         message to be generated.

      o  007E2072 translates to the following error message:

         %MAIL-E-PROTOCOL, network protocol error


         For example:

                unable to send  : PEAR::GARDENER    error2 = 07E2072   


         This may indicate that there is a problem with DECnet on your
         node.  Contact your DECnet manager.

      o  007E802A translates to the following error message:

         %MAIL-E-LOGLINK, error creating network link to node !AS


         For example:

                invalid address : BANNAA::BRADLEY    error1 = 007E802A  

         This occurs when the nodename is invalid, for example,
         BANNAA.  Check that the nodename is spelled correctly.  This
         error produces a non-delivery message.

         or:

                unable to send : PEAR::GARDENER   error1 = 007E802A   

         This error occurs when the node, in this example PEAR, is
         unavailable at the time the connection was attempted.  The
         Gateway will continue to try to send the message until it
         succeeds or reaches either the retry interval or the maximum
         number of retries.



                                 5-6

                                     Monitoring the Gateway for Errors


      o  007E8102 translates to the following error message:

         %MAIL-E-NOSUCHUSR, no such user !AS at node !AS


         For example:

                invalid address : BUNCE    error1 = 007E8102   


         In this case, there is no such user as BUNCE on this node.
         Check the username is spelled correctly.  The Gateway sends a
         non-delivery notification to the message sender if this error
         occurs.






































                                 5-7















                              Chapter 6

                   Error and Non-Delivery Messages



6.1  Introduction

This chapter describes the error and non-delivery messages that your
users can receive when sending messages to or from VMSmail.



6.2  Error Messages Received by Gateway Users

This section describes the error messages that your users can receive
when sending messages to and from VMSmail.  It also describes actions
you can take to recover from these errors.

The following are the error messages you may see immediately after you
try to send a VMSmail message to the Gateway, together with an
explanation of what the message means, and what to do when it is
received:


Error transferring message to Message Router
Not all requested privileges authorized
Error transferring message to Message Router

These messages are received when you are using VAXnotes.  The messages
indicate that you do not have the privileges required to send mail
from VAXnotes through the Gateway using the FORWARD or SEND commands.
Refer to the Message Router VMSmail Gateway User's Guide for details
of how to address mail from VAXnotes using the Gateway.









                                 6-1

Error and Non-Delivery Messages




%LIB-E-ACTIMAGE, error activating image mail-image
-RMS-E-FNF, file not found

where mail-image is the file specification of the mail image.

The system logical for MRFROMVMS has not been defined.  Restart the
Gateway as follows:

$ @SYS$MANGER:MB$CONTROL START=MRG

Use this command on every node in a VAXcluster.


%MAIL-E-LOGLINK, error creating network link to node MRGATE
-SYSTEM-F-NOSUCHNODE, remote node is unknown

The system logical for the Gateway has not been defined.  Restart the
Gateway by logging into the SYSTEM account and typing:

$ SYS$MANAGER:MB$CONTROL START=MRG

Use this command on every node in a VAXcluster.


%MAIL-E-LOGLINK, Error creating network link to node MRGATE
-SYSTEM-F-REJECT, Connect to network object rejected

The password in your configuration file for the Gateway mailbox does
not correspond to the password in the Message Router directory.

Reconfigure Message Router using the RECOVER option.  See the Message
Router manager.


%MRGATE-E-MRFROMVMS, Error transferring message to Message Router


This message appears before all other messages.  The other messages
help you identify the precise problem.


%MRGATE-F-NOCONN, Cannot connect to Message Router

Your Message Router is not set up correctly.  Tell your Message Router
manager.  Alternatively, there are insufficient system resources.  Try
to send the message later.




                                 6-2

                                       Error and Non-Delivery Messages


%MRGATE-E-NOINIT, Error during initialization

One of the configuration options is missing from the initialization
file.  Configure the Gateway using the RECOVER command as follows:

      1  Log into the SYSTEM account and stop MAILBUS by typing:

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

      2  Run the configuration procedure using the RECOVER option:

         $ SYS$MANAGER:MB$CONFIG RECOVER MRG

      3  Start the Gateway by typing:

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

         Use this command on every node in a VAXcluster.



%MROUTER-E-CREFIL, Could not create file
-RMS-E-CRE, ACP file create failed
-SYSTEM-F-EXDISKQUOTA, Disk quota exceeded

The Transfer Service has exceeded its disk quota.  Ask the Message
Router manager to tidy the Transfer Service files, or ask your VMS
system manager for a larger quota.

If you have enabled exception reporting, this error should also have
been reported by the exception reporting routines.


%MROUTER-E-FILERR, Failed to access file MRG$DIR:MRGINIT.DAT

Check that the logical name MRG$DIR is defined correctly; and that the
file MRGINIT.DAT exists; and that the ownership allows users of the
system to read it.

To check that the logical name MRG$DIR exists:

      1  Log in to the SYSTEM account and display the definition for
         MRG$DIR by typing:

         $ SHOW LOGICAL MRG$DIR

         The display shows the definition for MRG$DIR, for example:





                                 6-3

Error and Non-Delivery Messages


         "MRG$DIR" = "ddcu:[MB$.MRG]" (LNM$SYSTEM_TABLE)

         If the logical name MRG$DIR is not defined, start MAILBUS by
         typing:

         $ SYS$MANAGER:MB$CONTROL START=MRG

         Use this command on every node in a VAXcluster.

      2  Check that the file MRGINIT.DAT has the correct ownership and
         protection.  Use the command:

         $ DIR /PROTECTION /OWNER MRGINIT.DAT

         The ownership and protection of this file should be as
         follows:

         MRGINIT.DAT

         Owner:    [MBMANAGER]

         File protection:    System:RWED, Owner:RWED, Group:RE, World:R

         If the file has incorrect protection or does not exist,
         configure the Gateway using the RECOVER option, as follows:

          a  Log into the SYSTEM account and stop MAILBUS by typing:

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

          b  Run the configuration procedure using the RECOVER option:

             $ SYS$MANAGER:MB$CONFIG RECOVER MRG

          c  Start the Gateway by typing:

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

             Use this command on every node in a VAXcluster.




%MROUTER-E-OPSYS, System interface error

This error message relates to system resources.  Usually a secondary
message identifies the precise fault.  If there is no secondary
message you may have run out of virtual memory.  Ask your VMS system
manager to adjust the SYSGEN parameters.



                                 6-4

                                       Error and Non-Delivery Messages


-SYSTEM-F-INVLOGIN, login information invalid at remote node

The password of the MRNET account is not the same as the DECnet
database password for object type 22 (Message Router).

Reconfigure Message Router using the SET option to update the
passwords.  See the Message Router manager.



6.3  Non-Delivery Messages Received by Gateway Users

If the Gateway or Message Router fails to deliver a message, the
intended recipients of the message receive one of the following
non-delivery messages:

      o  MRGATE is not a valid recipient address

      o  NODE::NAME - invalid address

      o  NODE::NAME - timeout period expired

      o  NODE::NAME - maximum retry count (n) exceeded

      o  Invalid reply path generated - Route too complex


Details of non-delivery messages that your users might receive and are
able to recover from can be found in the Message Router VMSmail
Gateway User's Guide.

The non-delivery messages explained in Section 6.3.1 and Section 6.3.2
are messages your users are unable to recover from.  Further examples
can be found in Chapter 5.



6.3.1  Non-Delivery Message where the Route is too Complex for VMSmail

The following is a description of how the Gateway traps a message that
has a route that is too complex for VMSmail.  It also describes the
format of the associated error message.

A message can only enter VMSmail once through the Gateway.  This is
because the Gateway alters the addresses on the message as they pass
through it, so that the return address is valid.  VMSmail understands
addresses that have been altered once by the Gateway, but does not
understand addresses that have been altered more than once.  A message
only passes through the Gateway twice into VMSmail if VMSmail
recipients have set autoforwarding to send their mail out of VMSmail


                                 6-5

Error and Non-Delivery Messages


and then forward it back into VMSmail.

To prevent VMSmail receiving messages with addresses it does not
understand, the Gateway traps messages that have already passed once
through the Gateway into VMSmail, and sends a non-delivery message to
the sender of the message.  The non-delivery message has the following
format:

ERROR MESSAGE


  Delivery of this message through the Gateway had the following results:

        Invalid reply path generated - Route too complex
            Unable to deliver to :  nodename::username

The original message follows:

   The original message is included here

where:

      o  nodename is the name of the node where the message would pass
         through the Gateway a second time into VMSmail

      o  username is the username of the recipient.


If users receive this service message, they must find an alternative
address of the recipient by some other means and send the message
there.

For example, suppose a user called Smith has two VMSmail accounts, one
on node PEAR and one on node APPLE, and an ALL-IN-1 account on node
PEAR.  A user called Jones sends a message to Smith's VMSmail account
on PEAR from an ALL-IN-1 account on node PEACH.  The message is
addressed to SMITH@MRGATE@PEAR, and passes through the Gateway.

Smith has set autoforwarding from the VMSmail account on PEAR to the
ALL-IN-1 account on the same node, so the message is forwarded to
MRGATE::"A1::SMITH".  Smith has also set autoforwarding from the
ALL-IN-1 account on PEAR to the VMSmail account on APPLE.  So the
message is forwarded again to SMITH@MRGATE@APPLE.  The message tries
to pass through the Gateway again, but is prevented from doing so.








                                 6-6

                                       Error and Non-Delivery Messages


The Gateway sends the following non-delivery message to user Jones on
node PEACH:

ERROR MESSAGE


  Delivery of this message through the Gateway had the following results:

        Invalid reply path generated - Route too complex
            Unable to deliver to :  APPLE::SMITH

In this case, user Jones should send the message again to
SMITH@MRGATE@APPLE.



6.3.2  Non-Delivery Message Due to an Exceeded Retry Interval

If a node or a link to a node is not available long enough for the
Gateway to deliver a message, your users may receive one of the
following error messages:

      o  NODE::nodename - timeout period expired

      o  NODE::nodename - maximum retry count (n) exceeded

These errors are generated when one of the following configuration
parameters is exceeded:

      o  The retry interval (see Section 2.3.4)

      o  The maximum number of retries (see Section 2.3.5)

Check that you have not set the parameter value too low.  This is
particularly important if you are sending large messages, or the
network is heavily loaded.  If the parameter values are reasonable,
examine the Gateway information log file on the node where the problem
is occurring and make any changes that might be affecting the message
deliveries.  Refer to Chapter 5 for details of the Gateway information
log file.












                                 6-7















                              Appendix A

                         Sample Configuration



A.1  Log of Configuration

$ @sys$manager:mb$config

 
        MAILBUS CONFIGURATION PROCEDURE

Products currently defined in CUSTOMIZED configuration database
on 11-OCT-1987 10:58:18
 
        MR      : Message Router
 
                MS      : Management Service
 
                TS      : Transfer Service
 
                DDS     : Directory Service
 
                ER      : Exception Reporting
 
        A1      : ALL-IN-1
 
        MRG     : MRGATE
MBC> set mrg
%MB-I-MBC$SET, Setting configuration parameters
*  What device do you want to use for MRGATE [DUA0:] ? 
*  How often do you want to create a new information file (specify a
delta time) [7-00:00:00] ? 
*  For how long (in delta-time format) do you want MRGATE to keep
trying to send a message [4-00:00:00] ? 
*  How many times do you want MRGATE to try sending a message [350] ? 
*  How often do you want MRTOVMS to run (specify a combination time) [+00:15:00] ? 
*  Which batch queue do you want MRTOVMS to use [MB$BATCH] ? 
*  Do you want to send MRTOVMS error messages by VMSmail to the
network manager [Y] ? 


                                 A-1

Sample Configuration


*  Do you wish to modify the MRGATE mailbox password [N] ? 
*  Do you want to enable MRGATE exception reporting [Y] ? 
*  What alarm level of free blocks do you want to set for MRGATE [6000] ? 
*  Do you wish to modify the MRGATE account password [N] ? 
MBC> enable mrg
%MB-I-MBC$ENABLE, Enabling messaging process
MBC> recover mrg
%MB-I-MBC$RECOVER, Recovering configuration database
%MB-I-MBC$RECPHASE, Beginning recovery phase for MRG
%MB-I-CHKMRGREL, checking if MRGATE relocated to different location ...
%MB-I-CREMRGINI, creating initialization file for MRGATE ...
%MB-I-UPDTSMBX, updating TS mbx directory database for MRGATE ...
%MB-I-UPDXRPTENBF, updating MB Exception Reporting flag for MRGATE ...
%MB-I-MBC$REPLETE, Configuration database recovery complete
MBC> exit

$ @sys$manager:mb$control start=ts

Working, please wait ... 




Beginning START operation for TS.
%RUN-S-PROC_ID, identification of created process is 20206722
%RUN-S-PROC_ID, identification of created process is 20206723

MR$TIDY Requested operations:

SUBMIT


Transfer Service startup has completed.

Beginning Transfer Service user startup procedure.
starting user talkers

Transfer Service user startup has completed.


$ @sys$manager:mb$control start=mrg

Working, please wait ... 




Beginning START operation for MRG.
Job MRTOVMS (queue MB$BATCH, entry 763) started on MB$BATCH_ORANGE
MRGATE startup procedure has completed.


                                 A-2

                                                  Sample Configuration


$ @sys$test:mb$mrgcvp


==================================================================

        Message Router VMSmail Gateway Version V3.0 CVP

This verification procedure is in four stages: 

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

Stage 2 checks that DECnet is running. 

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. 






------------------------------------------------------------------
        MRG V3.0 file check




        The total number of files is 18.
        All files exist and are the correct size.
        End of MRG V3.0 file check.
------------------------------------------------------------------

 Checking ORANGE VMSmail network response
Succeeded in activating VMSmail DECnet object 27 on node ORANGE

Starting Management Service



        Stage 3 of the configuration verification procedure for
        MRGATE V3.0 successful


                                 A-3

Sample Configuration


        Waiting for delivery of VMSmail sent through Gateway V3.0.
              
        The CVP waits for a maximum of 30 minutes before timing out.

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

        Stage 4 of the configuration verification procedure for
        MRGATE V3.0 successful


Shutting Management Service

$ $ @sys$manager:mb$control stop=mrg

Working, please wait ... 
        



Beginning STOP operation for MRG.

MRGATE shutdown procedure has completed.

$ @sys$manager:mb$control stop=ts

Working, please wait ... 




Beginning STOP operation for TS.

Beginning Transfer Service user shutdown procedure.
stopping user talkers

Transfer Service user shutdown procedure has completed.
        This is MRMAN  V3.0

Transfer Service shutdown procedure has completed.

$











                                 A-4













                              Appendix B

                          Operational Files



Table B-1:  Gateway Operational Files

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

ddcu:[MB$.MRG]                    

MRGQUEUE.DAT                        (RWED,RWED,RW,)
MRTOVMS.INF                         (RWED,RWED,RE,)
MRTOVMS.LOG                         (RWED,RWED,RE,)
MRGINIT.DAT                         (RWED,RWED,RE,)



The directory may also contain some message files:  MESSAGEnnnn.NBS.






















                                 B-1















                              Appendix C

                            Gateway Files



Table C-1:  List and Description of the Gateway Files

File                                Name
----------------------------------------------------------------------

CVP Data File                       MRGATE$CVP.DAT
MRGATE Exception Reporting Error    MB$MRG_ERRORS.DAT
File
Configuration Data File             MB$MRG$CONFIG$CUSTOMIZED.DAT
(customized)
Configuration Data File (default)   MB$MRG$CONFIG$DEFAULT.DAT
VMSmail Error File                  VMSERROR.DAT
MRGATE Lock File                    MRGATE$STOP.DAT
MRGATE Initialization File          MRGINIT.DAT
MRGATE Queue File                   MRGQUEUE.DAT
MRGATE Exception Reporting          MB$MRG_ER.COM
Procedure
MRTOVMS Command Procedure           MRTOVMS.COM
Configuration Command Procedure     MB$$MRG_CONFIG.COM
Start Up Command Procedure          MB$$MRG_START.COM
Stop Command Procedure              MB$$MRG_STOP.COM
Transfer Service, MRGATE and        MB$START.COM
Exception Reporting Start Up
Command Procedure (for
compatibility with V2.1)
Transfer Service, MRGATE and        MB$STOP.COM
Exception Reporting Stop Command
Procedure (for compatibility with
V2.1)
MRGATE Start Command Procedure      MRGATEST.COM
(V2.0)
CVP Command File                    MB$MRGCVP.COM
MRTOVMS Image                       MRTOVMS.EXE
MRFROMVMS Image                     MRFROMVMS.EXE
MRTOVMS Information Log File        MRTOVMS.INF


                                 C-1

Gateway Files


File                                Name
----------------------------------------------------------------------
MRTOVMS Log File                    MRTOVMS.LOG
Message Files                       MESSAGEnnnn.NBS
















































                                 C-2

                                                                 INDEX


                                INDEX



Accepting exception reporting,      Default configuration parameters,
    2-7                                 2-3
Account                             Defining logicals, 3-6
  password, 2-8                     Defining system logicals
ALL-IN-1, 1-7                         Gateway, 6-2
Audience                            defining system logicals
  intended                            MRFROMVMS.COM, 6-1
    of this guide, i                Delivery of MRTOVMS error
                                        messages, 2-7
BADIDENT, 3-24                      Description of the Gateway Files,
BADLOG, 3-6                             C-1
Batch Queue                         DEVFULL, 3-7
  for MRTOVMS, 2-6                  Device name
Body                                  for the Gateway, 2-4
  of a message, 1-7                 DEVLOW, 3-7
                                    DEVNOTMOUNT, 3-12
Cluster                             DIGITAL
  configuring a, 2-8                  how to contact, 2-19, 3-4
Configuration                       DNR, 3-12
  checklist, 2-2                    Documents
  commands, 4-1                       related to this book, i
  customized, 2-2, 2-12
  default, 2-2, 2-3, 2-10           Error messages, 6-1
  Help, 2-8                         Exception Reporting, 2-7
  introduction, 2-1
  log, A-1                          Field
  parameters, 2-1, 2-3                From:, 1-7
  preparation, 2-2                    Subj:, 1-7
  sample, A-1                         To:, 1-7
  starting the, 2-8                 Fields
  step by step description, 2-8       of a message, 1-7
Configuration Procedure, 2-8, 2-9   Format
Configuring a cluster, 2-8            Message, 1-7
CONNECFAIL, 3-11                      Message Router, 1-8
Contacting                            VMSmail, 1-7
  DIGITAL, 2-19                     From: field, 1-7
Conventions
  used in this guide, xi            Gateway
Critical Block Count, 2-8             defining system logical, 6-2
Customer Support, 3-4                 Device name, 2-4
Customized configuration, 2-2,        error messages, 6-1
    2-12                              operational files, B-1
CVP, 2-16                             Overview, 1-3
                                      recovering, 4-1
Default configuration, 2-2, 2-3,      restarting, 3-5, 3-6, 3-9, 3-23,
    2-10                                  3-24, 3-25


                               Index-1

INDEX


  starting, 3-10, 6-2, 6-3, 6-4       system logical, 6-1
  stopping, 3-24, 6-3, 6-4          MRG$DIR
Gateway account                       system logical, 6-3
  password, 2-8                     MRGINIT.DAT, 6-4
Gateway files, B-1                  MRGQUEUE.DAT, B-1
Gateway Information file            MRGSTOP, 3-10
    (MRTOVMS.INF), 3-14             MRTOVMS error messages, 2-7
Gateway mailbox password            MRTOVMS.COM, 3-15
  setting the, 2-7                    batch queue, 2-6
Gateway message files, B-1          MRTOVMS.INF, B-1
Grading Tasks, 3-4                    Gateway information log file,
                                          5-2
Header                              MRTOVMS.LOG, B-1
  Message, 1-7
                                    NOBAT, 3-15
Information Log File                NOCNFDB, 3-22
  creation interval, 2-4            NODBF, 3-9
INSUFQUO, 3-8                       NODEVICE, 3-5
Intended Audience                   NOLOGICAL, 3-6
  of this guide, i                  Non-delivery messages, 6-5
INVLOGIN, 3-19                      Non-delivery notification, 2-5
                                    NORETADR, 3-25
LINKABORT, 3-11                     NOSUCHNODE, 3-17
LINKEXIT, 3-11                      NOSUCHOBJ, 3-19
LOWQUO, 3-8
                                    OLDMG, 3-13
Mailbox                             OLDMR, 3-23
  password, 2-3, 2-7                On-line Help for configuration,
Management Action Procedures            2-8
  see MAP                           Operational files, B-1
Managing
  error messages, 1-8               Password
  information log file, 1-9           Gateway account, 2-8, 3-24
  introduction to, 1-1                Gateway mailbox, 2-7
  non-delivery messages, 1-8        Purging files, 3-7
  overview, 1-1
  tasks, 1-8                        Quota, 3-8
MAP
  Management Action Procedure,
      3-4                           Rating Tasks, 3-4
  solutions, 3-4                    Re-submission Interval, 2-6
  tasks, 3-4                        Reconfiguring the Gateway, 4-1
MB Command Procedures, 3-1          Related documents
Message body, 1-7                     to this book, i
Message Fields, 1-7                 REMRSRC, 3-20
Message files, B-1                  Report Message, 3-4
Message Formats, 1-7                Restarting the Gateway, 3-5, 3-6,
Message header, 1-7                     3-9, 3-23, 3-24, 3-25, 6-2
Message Router format, 1-2, 1-8     Retries
MRFROMVMS.COM                         number of, 2-5


                               Index-2

                                                                 INDEX


Software Versions                     editing, 2-21
  compatible with the Gateway,
      1-1                           To: field, 1-7
Starting the Gateway, 2-21, 3-10,
    6-3, 6-4                        UNREACHABLE, 3-18
Stopping the Gateway, 3-24, 6-3,
    6-4                             Versions
Subj: field, 1-7                      Software, 1-1
SWVERS, 3-21                        VMSmail format, 1-7
SYSTARTUP.COM                       VMSmail Report Message, 3-4






                                        Message Router VMSmail Gateway
                                                      Management Guide
                                                           AA-KR25A-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

