Message Router Installation Guide Version 3.1 digital equipment corporation, maynard, massachusetts AA-KR16B-TE First Printing, September 1988 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used and copied only in accordance with the terms of such license. Digital Equipment Corporation assumes no responsibility for the use or reliability of its software on equipment that is not supplied by DIGITAL or its affiliated companies. Copyright (c) 1988 Digital Equipment Corporation. All rights reserved. Please fill in and send us the prepaid reader's comments at the end of this book. It will help us to keep improving our documentation. The following are trademarks of Digital Equipment Corporation: --------------- TM |d|i|g|i|t|a|l| --------------- DNA Rainbow ALL-IN-1 LQP RSTS DEC MAILbus RSX DECmate MASSBUS ULTRIX DECnet Message Router UNIBUS DECset MicroPDP VAX DECstart MicroVAX VAXmate DECUS MicroVMS VMS DECSYSTEM-10 OSAK VOTS DECSYSTEM-20 PDP WPS-PLUS DIBOL Q-BUS WPS-8 ii CONTENTS Preface CHAPTER 1 Introduction 1.1 Introducing Message Router . . . . . . . . . . . 1-1 1.2 Installing and Configuring Message Router . . . . 1-1 1.2.1 The Installation Procedure . . . . . . . . . . . 1-2 1.2.2 The Configuration Procedure . . . . . . . . . . 1-3 1.2.3 Cluster Limitations . . . . . . . . . . . . . . 1-3 1.3 Handling Installation Errors . . . . . . . . . . . 1-4 CHAPTER 2 Preparing to Install Message Router 2.1 Preparation Checklist . . . . . . . . . . . . . . 2-1 2.2 Prerequisite Software and Hardware . . . . . . . . 2-1 2.2.1 Preparing MicroVMS for a Message Router Installation Procedure . . . . . . . . . . . . . 2-3 2.2.2 Preparing VMS Version 5.0 for a Message Router Installation Procedure . . . . . . . . . . . . . 2-8 2.2.2.1 Preparing to Use the VMS Tailoring Utility . . 2-9 2.2.2.2 Using the VMS Tailoring Utility . . . . . . 2-10 2.3 Preparing Your System for Installation . . . . . 2-15 2.3.1 System Parameters . . . . . . . . . . . . . . 2-15 2.3.2 System Account Quotas . . . . . . . . . . . . 2-19 2.3.3 Remaining Preparations . . . . . . . . . . . . 2-19 2.3.4 Preparing to Install Message Router on a VAXcluster or Local Area VAXcluster . . . . . 2-23 2.3.4.1 Cluster Limitations in the Directory Service 2-24 2.3.4.2 Cluster Limitations in the Transfer Service 2-24 2.3.4.3 Installing the Directory Service and a Homogeneous Transfer Service . . . . . . . 2-24 2.3.4.4 Installing a Heterogeneous Transfer Service 2-25 2.3.4.5 Installing the Management Service . . . . . 2-25 2.3.5 Preparing to Upgrade Message Router from Message Router Version 2.0 or 2.1 . . . . . . 2-26 2.3.6 Preparing to Upgrade Message Router from Message Router Version 3.0 . . . . . . . . . . 2-27 2.3.7 Preparing to Re-install Message Router Version 3.1 . . . . . . . . . . . . . . . . . . . . . 2-29 iii CHAPTER 3 Installing Message Router 3.1 Starting the Installation . . . . . . . . . . . . 3-1 3.2 Running the Installation Procedure . . . . . . . . 3-4 CHAPTER 4 Running the IVP 4.1 Introduction . . . . . . . . . . . . . . . . . . . 4-1 4.2 Running the IVP . . . . . . . . . . . . . . . . . 4-1 4.3 Checking the IVP . . . . . . . . . . . . . . . . . 4-6 CHAPTER 5 After the Installation 5.1 Restarting DECnet . . . . . . . . . . . . . . . . 5-1 5.2 Configuration Information . . . . . . . . . . . . 5-2 5.3 Location of the Message Router Software . . . . . 5-2 5.4 After an Installation on a Homogeneous Cluster . . 5-6 5.5 After an Installation on a Heterogeneous Cluster . 5-7 5.6 After a Message Router Installation on MicroVMS . 5-7 5.7 After a Message Router Installation on VMS Version 5.0 . . . . . . . . . . . . . . . . . . . . . . . 5-8 APPENDIX A Distribution Media APPENDIX B Sample Installation Procedure Running VMS Version 4.6, 4.7 Or MicroVMS APPENDIX C Sample Installation Procedure Running VMS Version 5.0 INDEX FIGURES 5-1 Message Router Directory Structure . . . . . . . . 5-2 TABLES 2-1 SYSGEN Parameters . . . . . . . . . . . . . . . 2-16 2-2 Account Quotas Values . . . . . . . . . . . . . 2-19 5-1 Location of the Transfer Service Files . . . . . . 5-2 5-2 Location of the Management Service Files . . . . . 5-4 5-3 Location of the Directory Service Files . . . . . 5-6 iv Preface Purpose of This Book This book describes how to install Message Router Version 3.1 on a VMS or MicroVMS operating system. It also describes how to upgrade from earlier versions of Message Router. Intended Audience This book is intended for the person responsible for installing Message Router. That person must be familiar with operating system management and DECnet, and have access to the SYSTEM account on the VMS or MicroVMS system. How This Book Is Organized This book has five chapters and three appendixes: o Chapter 1 introduces: - The installation procedure - The configuration procedure o Chapter 2 describes the tasks that you have to carry out before installing Message Router and lists the prerequisite hardware and software o Chapter 3 describes the installation procedure v Preface o Chapter 4 describes the installation verification procedure (IVP), which checks that the software is installed correctly on the system o Chapter 5 lists the tasks that you must carry out immediately after installation o Appendix A lists the items in the distribution kit o Appendix B contains a log of a typical Message Router installation on VMS Version 4.6 or 4.7 or on MicroVMS o Appendix C contains a log of a typical Message Router installation on VMS Version 5.0 How to Use This Book Read Chapters 1 and 2 before starting the installation. If you are installing Message Router on VMS Version 5.*, refer to the VMS License Management Utility Manual, for details of how to register and load the Message Router Product Authorization Key. Use the rest of the book during the installation procedure. Remember that the installation Help can give you most of the information that you are likely to need during the installation. Related Documents You may find the following books useful: Introduction to MAILbus Introduction to Message Router Message Router Management Guide Message Router Management Reference Manual Message Router Configuration Guide You may also need to refer to: VAX/VMS Command Language vi Preface VAX/VMS System Manager's Reference Manual Guide to VAX/VMS Software Installation MicroVMS User's Manual VAX/VMS Authorize Utility Reference Manual VAX/VMS Guide to System Management and Daily Operations VAX/VMS License Management Utility Manual Figure 1 shows how to use the publications provided with Message Router. vii Preface Figure 1: Message Router Documentation Map ------------------------------------------ |Read the Introduction to Message Router.| ------------------------------------------ | V ------------------------------------------------------ | Read the release notes. See the Message Router | |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 ------------------------------------------------- |Read the Message Router Configuration Guide for| | details of how to configure Message Router. | ------------------------------------------------- | 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.| ------------------------------------------------------ viii Preface Conventions The following conventions are used in this book: red print Indicates commands or responses that you type. Unless otherwise stated, press RETURN after each command or response. this typeface Indicates prompts and messages from the computer. lowercase Lowercase text in a function call, or in a DCL command or command procedure, indicates that you substitute a valid expression in that place. [] Brackets are used after installation questions to enclose the default answer. Press RETURN to accept the default value. Brackets in a function or in a DCL command indicate an optional entry. ... Horizontal ellipses appear in the commands used to stop and start the MAILbus components. The ellipses indicate that you can enter the name of any other Gateways available on your system to the command line. For example, the Message Router VMSmail Gateway (MRGATE). 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 Press Indicates that you make one keystroke with an editing or command key. For example, press RETURN. Type Indicates characters that you type from the keyboard. ix Chapter 1 Introduction 1.1 Introducing Message Router Message Router is part of MAILbus. MAILbus comprises Message Router and its Gateways, for example, the Message Router VMSmail Gateway. Refer to the Introduction to MAILbus for details of MAILbus. Message Router has three components: o A message transfer component, called the Transfer Service, which transfers messages from one node to another. The management utility MRMAN is used to manage this component. o A directory component, called the Directory Service, which keeps a record of users in the network who can send and receive mail. The management utility MBMAN is used to manage this component. o A set of management service routines, called the Management Service, which comprises the exception reporting routines and the management command procedures. These components are all installed together and the instructions for installing them are in this book. 1.2 Installing and Configuring Message Router You cannot use Message Router until you have installed and configured it. It is important that you plan the installation and configuration of Message Router before you start the installation. Read the Message Router Configuration Guide for information about planning your mail network before installing Message Router Version 3.1. 1-1 Introduction If you are installing Message Router Version 3.1 on VMS Version 5.0, you must use the VMS License Management Utility to register the Message Router product license before starting the installation procedure. An attempt to run an unlicensed Message Router Version 3.1 on VMS Version 5.0 will fail. See the VMS License Management Utility Manual for details of how to use the VMS License Management Utility. NOTE If you install Message Router Version 3.1 on VMS Version 4.6 or 4.7, or on MicroVMS, and later upgrade VMS to Version 5.0, then you must register the Message Router license, and re-install Message Router. An attempt to run Message Router Version 3.1 on VMS Version 5.0 will fail if you have not registered the license. After you have installed Message Router, you can either install the MAILbus Gateway(s) that you want to use, or configure Message Router. However, you must configure Message Router before configuring any Gateway(s) that you want to use. This book deals with the installation of Message Router on VMS Versions 4.6, 4.7, and 5.0, and on MicroVMS Versions 4.6 or 4.7. 1.2.1 The Installation Procedure You might not need to install Message Router on every node that is to use its services. User Agents and gateways can use the Transfer Service component of Message Router remotely. However, they can only use the Directory Service component locally. Therefore, if you intend to use the Directory Service component, you need to install Message Router on all nodes that are to use Message Router; but, if you do not intend to use the Directory Service you can install Message Router on fewer nodes, and only configure the Transfer Service component. NOTE ALL-IN-1 Version 2.2 and earlier, and Message Router VMSmail Gateway Version 3.1 and earlier, do not use the Directory Service. It does not matter on which node you install Message Router first, but if you are going to use the Directory Service component, the first node you configure must be the Directory Service master node. See the Message Router Configuration Guide for more information about 1-2 Introduction configuration. There are special considerations when installing on a VAXcluster or Local Area VAXcluster (see Section 1.2.3). This guide explains how to install Message Router on VMS or MicroVMS operating systems. Message Router is installed using VMSINSTAL, a command procedure used to install optional software products on the VMS or MicroVMS operating system. Basic knowledge of VMSINSTAL is required to perform the installation. You can check that the installation has succeeded by running the installation verification procedure (IVP), after the installation is complete. The IVP, if you request it, runs automatically after the installation and is described fully in Chapter 4. If the IVP is successful, the Message Router software resides on your system, but cannot be used until it is configured. The procedure to install Message Router and run the IVP should take about 60 minutes, depending on the system configuration and type of media used. The installation procedure is the same, whatever the distribution media. You can use your Message Router V3.1 system with any Message Router V2.* or V3.0 system in the same network. The installation procedure provides a command procedure that enables the V3.1 system to monitor the V2.1 and V3.0 systems for exception conditions. Refer to the Message Router Configuration Guide for details of the procedure and how it is used. 1.2.2 The Configuration Procedure The configuration procedure for Message Router is described in the Message Router Configuration Guide. For details of how to install and configure other MAILbus products, such as the Message Router VMSmail Gateway, refer to the relevant installation and management guides. 1.2.3 Cluster Limitations VAXclusters and the applications that use them can be set up either homogeneously or heterogeneously. Section 2.3.4 describes both types of cluster configuration and the preparations that you must make before installing Message Router on a cluster. The cluster and the applications that run on it can be considered separately when deciding how to set up the cluster. Even within an application, the components of the application may be independent of each other. This is the case with Message Router V3.1; the Transfer 1-3 Introduction Service gives more choice of configuration on a cluster than the Directory Service. Therefore, you can run different configurations of the Transfer Service and Directory Service on the same cluster. 1.3 Handling Installation Errors During the installation and IVP, you are told to ignore certain error messages that may appear. It is a good idea to use a hardcopy terminal to keep a record of any errors. However, if you receive an unexpected error message during the installation, act as follows: 1 Check that you have responded to the prompts correctly. 2 If you have made a mistake and have been re-prompted, enter the correct information. 3 If that fails, restart the installation. 4 If the installation fails again at the same point, contact DIGITAL as follows: o Contact your Customer Support Center, if you have a service contract o Contact your local DIGITAL office to arrange for a service contract, if you do not have one Turn to the next chapter to prepare for installation. 1-4 Chapter 2 Preparing to Install Message Router 2.1 Preparation Checklist Prepare for installation as follows: 1 Check that the distribution kit is complete and correct according to the bill of materials included with the kit. The distribution medium may be a magnetic tape or disk(s) containing all the files listed in Appendix A. The type of media depends on the hardware of your system. 2 Check that you have a Software Product Description (SPD). 3 Ensure that your system has the prerequisite software and hardware. See Section 2.2. 4 Prepare the system for installation 2.2 Prerequisite Software and Hardware To install Message Router Version 3.1 you must have: o A valid VAX or MicroVAX system configuration. o A registered Product Authorization Key for Message Router, if you are installing it on VMS Version 5.0. o DECnet installed. o A minimum of 18000 free blocks on the system disk available for installation, and 10000 blocks available permanently. 2-1 Preparing to Install Message Router o Disk space to hold messages, directory database files and queue files. Initially, you need about 30000 free blocks on the target disk. This is the disk where the MBMANAGER account is to be installed. The following software must be installed on a VAX: o VAX/VMS Version 4.6 or later o DECnet NOTE If you are installing Message Router on VMS Version 5.0, DECnet must have a registered Product Authorization Key. The following software must be installed on a MicroVAX if you are installing on MicroVMS (Section 2.2.1 gives details of how to install any missing software): o MicroVMS base system Version 4.6 or 4.7 o Object and Shareable Image Libraries (SYS$SHARE:IMAGELIB.OLB) from diskette PROG o Print and Batch Queue Utilities (SYS$BATCH) from diskette USER o The ANALYZE /RMS_FILE utility from diskette PROG o The SEARCH Utility from diskette UTIL o The VAXTPU Utility from diskette UTIL o The VMS MAIL Utility from diskette UTIL o DECnet from diskette DECNET The following software must be installed if you are installing on VMS Version 5.0 (Section 2.2.2 describes how to use the VMSTAILOR Utility to install any missing software): o VAX/VMS Version 5.0 o Object and Shareable Image Libraries (SYS$SHARE:IMAGELIB.OLB) 2-2 Preparing to Install Message Router o File Access Control List utilities o Print and Batch Queue utilities o ANALYZE /RMS_FILE utility o The VMS MAIL utility o VAXTPU utility 2.2.1 Preparing MicroVMS for a Message Router Installation Procedure Complete the following checklist to prepare your MicroVMS system for the installation or update: 1 Check that you have the MicroVMS base system Version 4.6 or later installed. 2 Check that the Object and Shareable Image Libraries are installed (SYS$SHARE:IMAGELIB.OLB). If the libraries are installed the file IMAGELIB.OLB is in SYS$SHARE. If the libraries are missing, then install them from the diskette labeled PROG, as described in the installation section of the MicroVMS User's Manual. VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption, you are asked if it is required. Answer NO to all questions except: Do you want to install the Object and Shareable Image Libraries? Type YES 3 Check that you have the Print and Batch Queue Utilities installed, and that the batch queue, SYS$BATCH, is running. If the queue utilities are missing, then install them from the diskettes labeled USER, as described in the installation section of the MicroVMS User's Manual. 2-3 Preparing to Install Message Router VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption, you are asked if it is required. Answer NO to all questions except: Do you want to install the Print and Batch queue utilities? Type YES If you do not have a batch queue SYS$BATCH, use the following command: $ START /QUEUE /MANAGER /BUFFER_COUNT=10 /EXTEND_QUANTITY=25 To ensure that the batch queue starts at system startup, edit the system startup file (SYS$MANAGER:SYSTARTUP.COM) to include that command line. 4 Check that you have the ANALYZE /RMS_FILE utility installed. If you are not sure whether the ANALYZE /RMS_FILE is installed, try to analyze a file in your current directory, as follows: $ ANALYZE /RMS_FILE filename where filename is the name of a file. If the command produces an error message indicating that ANALYZE /RMS_FILE is not installed, install it from the diskette labeled PROG, as described in the installation section of the MicroVMS User's Manual. VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption you will be asked if it is required. Answer NO to all questions except: Do you want to install the ANALYZE/RMS_FILE utility? Type YES. 2-4 Preparing to Install Message Router 5 Check that the SEARCH utility is installed (SYS$SYSTEM:SEARCH.EXE). If the SEARCH utility is installed, the file SEARCH.EXE is in SYS$SYSTEM. If the SEARCH utility is not installed, install it from the diskette labeled UTIL, as described in the MicroVMS User's Manual. VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption you will be asked if it is required. Answer NO to all questions except: Do you want to install the SEARCH Utility? Type YES. 6 Check that you have the VAXTPU utility installed. If the VAXTPU utility is installed on your MicroVMS system, the file TPU.EXE is in SYS$SYSTEM. If TPU.EXE is not in SYS$SYSTEM, install the VAXTPU utility from the diskette labeled UTIL, as described in the MicroVMS User's Manual. VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption you will be asked if it is required. Answer NO to all questions except: Do you want to install the VAXTPU utility? Type YES. 7 Check that you have the VMSmail utility installed. If you are not sure whether VMSmail is installed on your MicroVMS system, try to invoke the utility with the following command: $ MAIL 2-5 Preparing to Install Message Router If the MAIL> prompt appears, the VMSmail utility is installed on your system. If the MAIL> prompt does not appear, install the VMSmail utility from the diskette labeled UTIL, as described in the MicroVMS User's Manual. VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption you will be asked if it is required. Answer NO to all questions except: Do you want to install the MAIL utility? Type YES. Check that the system startup file includes a command line that installs the MAIL image during every system startup. To check whether the MAIL image is installed by the system startup file on a MicroVMS system, edit SYSTARTUP.COM, and look for the following lines, which may have been commented out: $ RUN SYS$SYSTEM:INSTALL SYS$SYSTEM:MAIL/OPEN/HEADER/PRIV=(SYSPRV,OPER,WORLD,NETMBX) If these lines do not appear in your system startup file, include them in the file where similar images are installed. If the lines are commented out, remove the comment flags. 8 Check that you have DECnet installed. If you are not sure whether DECnet is installed, try running the Network Control Program (NCP), by typing: $ RUN SYS$SYSTEM:NCP If the NCP> prompt is displayed, DECnet is installed. If DECnet is missing, then install it from the diskettes labeled DECNET, as described in the installation section of the MicroVMS User's Manual. 2-6 Preparing to Install Message Router VMSINSTAL displays: Do you want to install the entire kit? Type NO For each suboption you will be asked if it is required. Answer NO to all questions except: Do you want to install the Incoming Remote File Access files? Do you want to install the Incoming Remote Terminal files? Do you want to install the Outgoing Remote Terminal files? Type YES to each. Follow the instructions in the network section of the MicroVMS User's Manual to install the appropriate key from diskette DECNET/ENDNET for the type of routing you want, and create the database. 9 Calculate how many processes you are likely to need running on your MicroVAX. Add the following: o The number of permanent processes. You will have at least seven processes after installing DECnet and rebooting your MicroVAX. o The number of users who may wish to log in at any one time. o The number of batch jobs that can run at any one time. o The number of nodes that are likely to be connected to this Message Router at any one time. o The number of User Agents that may be connected to this Message Router at any one time. o One for the MBMANAGER account. o At least four for the Directory Service. o At least two for the Transfer Service. o At least five for the Management Service. 2-7 Preparing to Install Message Router The maximum process limit should be at least this value. To examine the value, use the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW MAXPROCESSCNT If the maximum process limit is less than the value you calculated above, edit the file SYS$SYSTEM:MODPARAMS.DAT to include the following line: ADD_MAXPROCESSCNT=maxprocesscnt_quota where maxprocesscnt_quota is the extra quota you require. NOTE Change the MAXPROCESSCNT before the Message Router installation, or the installation may fail. If the process count is not high enough, you are likely to see the following error from DECnet: %SYSTEM-F-REMRSRC, insufficient system resource at remote node When you have altered MODPARAMS.DAT, you need to run AUTOGEN. However, Section 2.3 describes how to check other SYSGEN parameters and modify them where necessary. Perform the steps described in that section before running AUTOGEN. Once you have completed these preparations, turn to Section 2.3. 2.2.2 Preparing VMS Version 5.0 for a Message Router Installation Procedure This section explains how to prepare a VMS Version 5.0 system for a Message Router installation procedure. 2-8 Preparing to Install Message Router Firstly, check that the Message Router Version 3.1 Product Authorization Key is registered and loaded. To do this, type the following command: $ LICENSE LIST If the list of licenses does not include Message Router, refer to the VMS License Management Utility Manual for details of how to register and load the license. Also, you might need to use the VMS tailoring utility to prepare your system for the Message Router installation procedure. The tailoring utility enables you to add and remove software from the VMS Version 5.0 system. You must ensure that all the software required for the installation procedure is installed. (You can use the VMS Tailoring Utility on any VAX system, but you are most likely to need it on a MicroVAX.) 2.2.2.1 Preparing to Use the VMS Tailoring Utility Message Router Version 3.1 requires the following software: o Object and Shareable Image Libraries o File Access Control List utility o Print and Batch Queue utilities o ANALYZE /RMS_FILE utility o The VMS MAIL utility o VAXTPU utility Complete the following checklist to see whether these files and utilities are already installed on your system. 1 Check that the Object and Shareable Image Libraries are installed (SYS$SHARE:IMAGELIB.OLB). If the libraries are installed the file IMAGELIB.OLB is in SYS$SHARE. 2 Check that the File Access Control List Utilities (SYS$SYSTEM:ACLEDT.EXE) are installed. If the File Access Control Utilities are installed, the file ACLEDT.EXE is in SYS$SYSTEM. 2-9 Preparing to Install Message Router 3 Check that the Print and Batch Queue Utilities are installed, and have a running batch queue, SYS$BATCH. Check that the file SMBSRVSHR.EXE is in SYS$LIBRARY. If you find the file, use the following command to see whether the batch queue is running: $ SHOW QUEUE /BATCH /ALL If the utilities are installed but there is no running batch queue, edit SYS$MANAGER:SYSTARTUP_V5.COM to ensure that it includes the following command line: $ START /QUEUE /MANAGER /BUFFER_COUNT=10 /EXTEND_QUANTITY=25 4 Check that the ANALYZE /RMS_FILE utility is installed. If you are not sure whether the command is installed, try to analyze a file in your current directory, as follows: $ ANALYZE /RMS_FILE filename where filename is the name of any file in your directory. If the command succeeds, the utility is installed. 5 Check that the VAXTPU Utility is installed. If the utility is installed, the file TPU.EXE is in SYS$SYSTEM. 6 Check that the VMSmail utility is installed. To do this, type: $ MAIL If the MAIL> prompt appears, the VMSmail utility is installed. If any of these libraries and utilities are missing, use the VMS Tailoring Utility to install them as described in Section 2.2.2.2. If these VMS features are installed on your system, go to Section 2.3 to make further preparations. 2.2.2.2 Using the VMS Tailoring Utility If you need to install any of the VMS libraries and utilities mentioned in Section 2.2.2.1, complete the following steps: 2-10 Preparing to Install Message Router 1 Invoke VMSTAILOR in the following way: a Log in to the SYSTEM account. b Type the following command: $ RUN SYS$UPDATE:VMSTAILOR c The procedure starts and displays: This is the VMS tailoring utility. It lets you customize VMS for your particular system. You do this by identifying classes and subclasses of VMS files that you want to add or delete. VMSTAILOR has three phases: - First, VMSTAILOR asks if you want to tailor your system by adding files ("tailor on") or by deleting files ("tailor off"). - Second, if you choose the "tailor on" procedure, VMSTAILOR lists each class of VMS files and asks if you want to include them on the system disk. If you choose the "tailor off" procedure, VMSTAILOR lists each class of VMS files and asks if you want to delete them from the system disk. - Third, VMSTAILOR carries out your instructions. NOTE: To cancel VMSTAILOR during the first and second phases, press Control-C, Control-Y, or Control-Z. If you cancel VMSTAILOR during the third phase, you may end up with a partially tailored disk. Do you want to tailor files "ON" or "OFF"? Type ON and press RETURN. 2 The procedure displays: TAILOR-ON ---------- You will now be prompted with a list of the classes and subclasses of VMS files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. 2-11 Preparing to Install Message Router Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. Total size of the system disk is nnnnnnn blocks. Total space used on the system disk is nnnnnnn blocks. Total space left on the system disk is nnnnnnn blocks. CLASS - Network support Size of entire class (with subclasses): 1442 Size of common files required for any subclass: 1221 Do you wish to select the entire class (default = NO)? where nnnnnnn are numbers. Press RETURN to accept the default answer, because Message Router does not require the entire class. 3 The procedure displays: Do you wish to select any of its subclasses (default NO)? Press RETURN to accept the default answer, because Message Router does not require any of the subclasses. 4 The procedure displays: CLASS - Programming Support Size of entire class (with subclasses): 9749 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Press RETURN to accept the default answer, as Message Router does not require the entire class. The procedure displays: Do you wish to select any of its subclasses (default = NO)? If the Object and Shareable Image Libraries and the ANALYZE /RMS_FILE utility are already installed on your system, type NO and go to Step 6. Otherwise, type YES and press RETURN. 5 The procedure displays: Select the subclasses that you wish to use: 2-12 Preparing to Install Message Router For each subclass, press RETURN except for the following subclasses: SUBCLASS - RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL) (371 blocks) [NO]: SUBCLASS - Object and Shareable Image Libraries (3480 blocks) [NO]: If you need to install the libraries or the ANALYZE /RMS_FILE utility, type YES and press RETURN. Otherwise, press RETURN. 6 The procedure displays: CLASS - RMS journaling files Size of entire class (with subclasses): 72 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? Press RETURN to accept the default answer, because Message Router does not require the class. 7 The procedure displays: CLASS - System programming Support Size of entire class (with subclasses): 1290 Size of common files required for any subclass: 87 Do you wish to select the entire class (default = NO)? Press RETURN to accept the default answer, because Message Router does not require the entire class. 8 The procedure displays: Do you wish to select any of its subclasses (default = NO)? Press RETURN to accept the default answer, because Message Router does not require any of the subclasses. 9 The procedure displays: CLASS - Secure User's Environment Size of entire class (with subclasses): 613 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Press RETURN to accept the default answer, because Message Router does not require the entire class. 2-13 Preparing to Install Message Router 10 The procedure displays: Do you wish to select any of its subclasses (default = NO)? If the File Access Control List utilities and the Print and Batch Queue utilities are already installed on your system, press RETURN and go to Step 12. If you need to install either the File Access Control utilities, or the Print and Batch queue utilities, type YES and press RETURN. 11 The procedure displays: Select the subclasses that you wish to use: For each subclass, press RETURN except for the following subclasses: SUBCLASS - File Access Control List utilities (386 blocks) [NO]: SUBCLASS - Print and Batch Queue utilities (106 blocks) [NO]: If you need to install these utilities, type YES and press RETURN. Otherwise, press RETURN. 12 The procedure displays: CLASS - Utilities Size of entire class (with subclasses): 8692 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Press RETURN to accept the default answer, because Message Router does not require the entire class. 13 The procedure displays: Do you wish to select any of its subclasses (default = NO)? If the VMSmail utility and the VAXTPU utility are already installed on your system, press RETURN and go to Step 15. If you need to install either of the VMSmail or VAXTPU utilities, type YES and press RETURN. 14 The procedure displays: Select the subclasses that you wish to use: 2-14 Preparing to Install Message Router For each subclass, press RETURN, except for the following subclasses: SUBCLASS - MAIL utility (394 blocks) [NO]: SUBCLASS - VAXTPU utility (1824 blocks) [NO]: If you need to install these utilities, type YES and press RETURN. Otherwise, press RETURN. 15 For all the remaining classes and subclasses offered by the procedure, press RETURN because Message Router does not require them. 16 The procedure displays: Do you wish to add all of the options selected? Type YES to add the selected options. The utility adds the selected options, and displays the names of the files it is adding to your system. Once you have completed these preparations, go to Section 2.3. 2.3 Preparing Your System for Installation 2.3.1 System Parameters You must ensure that the SYSGEN parameters for Message Router are set to allow sufficient quota for the installation. It is important that you do any tailoring of your system before you make the checks and alterations described in the following sections. Table 2-1 shows the minimum values applicable to each parameter for Message Router. NOTE These values do not include the quotas required for other products you may have installed on your system. 2-15 Preparing to Install Message Router Table 2-1: SYSGEN Parameters Parameter Value ---------------------------------------------------------------------- PROCSECTCNT 32 GBLSECTIONS 250 GBLPAGES 12288 CLISYMTBL 250 GBLPAGFIL 1500 If you need to change the quotas for the system parameters, change them before you install Message Router. Otherwise, the installation will fail. If you are installing on a cluster, you must modify the quota on each node in the cluster where you want to use Message Router, as described later in this section. Work out your system's quotas for these parameters and modify them if necessary, using the SYSGEN utility. Find out the current settings for the SYSGEN parameters: 1 Log in to the SYSTEM account 2 Invoke the SYSGEN utility by typing: $ RUN SYS$SYSTEM:SYSGEN The system responds with the SYSGEN prompt, SYSGEN>. 3 To ensure that you retrieve values from the current system parameter file on disk, use the command: SYSGEN> USE CURRENT 4 Type the following command to find out the quota available for the global sections: SYSGEN> SHOW GBLSECTIONS Make a note of the current value. 5 Type the following command to find out the quota available for the global pages: SYSGEN> SHOW GBLPAGES Make a note of the current value. 2-16 Preparing to Install Message Router 6 Type the following command to find out the quota available for the CLI symbol table: SYSGEN> SHOW CLISYMTBL Make a note of the current value. 7 Type the following command to find out the quota available for the process section count: SYSGEN> SHOW PROCSECTCNT Make a note of the current value. 8 Type the following command to find out the quota available for the global page-file sections: SYSGEN> SHOW GBLPAGFIL Make a note of the current number. 9 To exit from SYSGEN, type: SYSGEN> EXIT Find out how many Global Pages and Global Sections are in use on your system using the Install utility. 1. If you are running VMS Version 4.6 or 4.7 or MicroVMS, invoke the Install utility by typing the following commands: $ INSTALL:=$SYS$SYSTEM:INSTALL/COMMAND_MODE $ INSTALL If you are running VMS Version 5.0, invoke the Install utility by typing the following command: $ INSTALL 2. The system responds with the Install prompt. Type the following command to list the global sections that are in use on your system: INSTALL> LIST/GLOBAL At the end of the display are the numbers of Global Sections and Global Pages used. Take these values and subtract them from the current values that you obtained from the SYSGEN utility. If you do not have at least 40 Global Sections and 5000 Global Pages remaining, you must modify either or both 2-17 Preparing to Install Message Router of the GBLSECTIONS and GBLPAGES parameters to give the required quota, as described later in this section. Also, the values for GBLSECTIONS must be at least 250, and the value for GBLPAGES must be at least 12288, regardless of how many are actually free. 3. To exit from the Install utility, type: INSTALL> EXIT If you do not have a quota of 32 for the Process Section Count or 250 for the CLI Symbol Table, or 1500 for the global page-file sections, you must modify the parameters as appropriate. To modify the value of all these parameters, edit the file SYS$SYSTEM:MODPARAMS.DAT to include the following lines: ADD_GBLSECTIONS=gblsections_quota ADD_GBLPAGES=gblpages_quota ADD_PROCSECTCNT=procsectcnt_quota ADD_CLISYMTBL=clisymtbl_quota ADD_GBLPAGFIL=gblpagfil_quota where gblsections_quota, gblpages_quota, procsectcnt_quota, clisymtbl_quota, and gblpagfil_quota represent the additional quota that the system requires to give at least the minimum values specified in Table 2-1. Now run AUTOGEN to re-calculate your system parameters. First ensure that there are no active users on the system, using the following command: $ SET LOGINS/INTERACTIVE The system displays the maximum number of active users allowed on your system. Make a note of this number to enable the logins at the end of the installation. Ask the users currently on the system to log out, and disable logins by typing: $ SET LOGINS/INTERACTIVE=0 $ REPLY/BELL/ALL "PLEASE LOG OUT" If you are preparing to install on VMS Version 5.0, type the following commands to re-calculate your system parameters: 2-18 Preparing to Install Message Router $ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS NOFEEDBACK $ @SYS$UPDATE:AUTOGEN SETPARAMS REBOOT Otherwise, type: $ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS $ @SYS$UPDATE:AUTOGEN SETPARAMS REBOOT Modification of the current system parameters does not immediately affect the system. AUTOGEN performs an automatic shutdown and reboot when it has finished. 2.3.2 System Account Quotas You must ensure that the system account is set up with sufficient quota. Table 2-2 shows the minimum values applicable to the system account. Table 2-2: Account Quotas Values Account Quota ---------------------------------------------------------------------- ASTLM 24 BIOLM 18 BYTLM 24576 DIOLM 18 ENQLM 400 FILLM 20 PGFLQUOTA 10000 PRCLM at least 1 TQELM 20 You can modify the account quotas using the Authorize utility. See the VAX/VMS Authorize Utility Reference Manual for details of how to use the Authorize utility. You need to log out and log in again for the new values to take effect. 2.3.3 Remaining Preparations Follow these steps before invoking VMSINSTAL: 1 Log in to the privileged system manager's account at the operator's console. 2-19 Preparing to Install Message Router 2 Backup your system disk. If a system failure occurs at a critical point during the installation, some files may be corrupted. Also, you are given the choice of purging old files during the installation. If possible, use the backup copy of the system disk for installation. In this way: o You can verify that the backup copy contains a working system image o The backup disk will have more adjoining free space for use during installation 3 If you have not already done so, ensure that there are no active users on the system using the following command: $ SET LOGINS/INTERACTIVE The system responds with a message indicating the maximum number of active users allowed on your system. Make a note of this number to enable the logins at the end of the installation. Ask the users currently on the system to log out, and disable logins by typing: $ SET LOGINS/INTERACTIVE=0 $ REPLY/BELL/ALL "PLEASE LOG OUT" 4 Ensure that there are 18000 blocks available on the system disk for the installation of Message Router. After installation, Message Router needs 10000 on the system disk and 30000 blocks on the target disk. You may need more space on the target disk if you have a large message area. Use the SHOW DEVICE command to find out how many blocks are available on the system. To display the number of blocks available on the system disk, type: $ SHOW DEVICE SYS$SYSDEVICE 2-20 Preparing to Install Message Router To display the number of blocks available on the target disk, type: $ SHOW DEVICE device where device is the name of the target disk. 5 Make sure you have enough disk space to hold your expected message traffic. In addition to the Message Router software, Message Router needs disk space to hold messages, directory database files, and queue files in its database. You need to estimate your expected message traffic, and make sure that you have enough disk space to hold these messages. As a guide, the initial software in the MBMANAGER account needs approximately 1000 blocks of disk space. Allow a further 29000 for messages and database files. 6 If you are upgrading from a previous version of Message Router, run the Transfer Service talker on all systems to clear the message queues before the upgrade begins. Refer to the Message Router Management Guide for details of how to run the Message Router talker manually. You must ensure that the talker is no longer running before completing the next step of shutting down DECnet. 7 Shut down DECnet by issuing the following commands: $ RUN SYS$SYSTEM:NCP NCP> SET EXECUTOR STATE OFF NCP> EXIT You must shut down DECnet on every node in a cluster. 8 If you are updating an existing Version 2.0 or 2.1 Message Router, and you want to preserve your database, find out the initialization file specification and note the name in the space provided. The file specification should be as follows: SYS$COMMON:[SYSEXE]MRINIT_n.DAT where n represents the database number. _________________________________ 2-21 Preparing to Install Message Router 9 If you are installing Message Router for the first time on the system, decide which disk the new MBMANAGER account and message directories (the MB$ directory) are to reside on initially, and note the name here: _________________________________ 10 If you are updating an existing Version 2.0 or 2.1 Message Router and want to retain data or messages from the existing Message Router installation, find out the directory specification for the Version 2.0 or 2.1 miscellaneous directory. The directory specification should be in the form: ddcu:[directoryname] where ddcu is the name of the device where the miscellaneous directory is located, and directoryname is the name of the miscellaneous directory. Note the directory specification in the space provided. ________________________________ 11 If you are installing Message Router for the first time on the system, choose a UIC to hold the MBMANAGER account and record it in the space below. Do not choose a DECnet or system UIC; if you do, the installation may fail. The UIC must be unique to Message Router. If you have already installed Message Router V2.0 or V2.1, you will have a UIC for the MRMANAGER or the MBMANAGER account. Providing you have not used a system or DECnet UIC, you can use the same UIC, if you wish. If you have previously used a system UIC, enter a new non-system UIC. If you have already installed Message Router V3.0 or V3.1 you must continue to use the same UIC. UIC of the MBMANAGER account [________,________]. You must also choose a password for the MBMANAGER account. The password must contain at least eight and not more than 31 characters. 12 Ensure that you have started the system job queue manager. See the VAX/VMS Guide to System Management and Daily Operations for details of starting the queue manager. 2-22 Preparing to Install Message Router The rest of the preparation depends on the type of installation, as follows: o If you are installing on a VAXcluster, see Section 2.3.4. o If you upgrading from Version 2.*, see Section 2.3.5 o If you are upgrading from Version 3.0, see Section 2.3.6 o If you are re-installing Version 3.1, see Section 2.3.7 In all other cases, for example a new installation, you have finished preparing for installation. If you are installing Message Router on VMS Version 5.0, and you have not used the VMS License Management Facility to register and load the Product Authorization Key for Message Router, refer to the VMS License Management Utility Manual. Otherwise, turn to Chapter 3. 2.3.4 Preparing to Install Message Router on a VAXcluster or Local Area VAXcluster You can run Message Router on any VMS Version 4.6 or later VAXcluster or Local Area VAXcluster configuration. If you are running VMS Version 5.0, you must use the VMS License Management Facility on every node in the cluster. (See the VMS License Management Utility Manual for details of VMSLICENSE.) If you group several nodes into a VAXcluster, you must make sure that they are running the same version of Message Router. You must also make sure that for each node on the cluster, the SYSGEN parameters are set up as described in Section 2.3.1. If you want these nodes to share the same Message Router database, you must either choose one of the original databases to become the shared database, or create a new one. Message Router databases cannot be merged. There are two types of cluster: homogeneous clusters and heterogeneous clusters. In a homogeneous VAXcluster there is little difference between each node on the cluster. All the machines in the cluster share the same user community and access the same devices. Each node provides access to the devices that it owns for the other nodes. In a heterogeneous VAXcluster the nodes do not share the same user community. Individual nodes may have different user communities and different devices available at each node. The nodes in the same 2-23 Preparing to Install Message Router heterogeneous cluster can be started from different devices, although there are some shared disk areas. Message Router can be installed on a heterogeneous or homogeneous VAXcluster, with some limitations. 2.3.4.1 Cluster Limitations in the Directory Service The following restrictions apply to the Directory Service component when installed on any type of cluster: o You can only have one Directory Service database o You must keep the Directory Service database in a common area, so that it is accessible to all nodes in the cluster o You must run the Directory Service on all the nodes in the cluster 2.3.4.2 Cluster Limitations in the Transfer Service You have more choice with the Transfer Service component of Message Router V3.1. You can run the Transfer Service homogeneously, or you can run multiple Transfer Service databases on the same cluster. However, you cannot run multiple Transfer Service databases on the same node. DIGITAL recommends that you run the Transfer Service homogeneously because it is easier to manage than a heterogeneous configuration. 2.3.4.3 Installing the Directory Service and a Homogeneous Transfer Service If you are installing the Directory Service or the Transfer Service on a homogeneous cluster, you need only install Message Router once to modify the system user authorization file (SYSUAF.DAT) and the DECnet permanent database. If you are installing a homogeneous Message Router component on a heterogeneous cluster, you may have to install Message Router on more than one node, although you might only need to configure Message Router once. You must install Message Router so that it modifies the user authorization file (SYSUAF.DAT) and the DECnet permanent database 2-24 Preparing to Install Message Router on every node. If the SYSUAF and the DECnet database are shared between a set of nodes, you need only install Message Router on one node in the set. List the smallest number of nodes from which all the copies of SYSUAF.DAT and the DECnet database can be modified, and install Message Router on all nodes in the list. 2.3.4.4 Installing a Heterogeneous Transfer Service You have a heterogeneous Transfer Service when you run multiple Transfer Service databases on the same cluster. A Transfer Service database comprises the mailbox directory, the queue file, and message areas. Another type of heterogeneous cluster configuration is where you are running a single Transfer Service database, but not all the nodes in the cluster run the Transfer Service. You can only run the Transfer Service heterogeneously on a heterogeneous cluster. A set of nodes using the same user authorization file must use the same Transfer Service database. However, if a set of nodes use a single Transfer Service database, they might use multiple SYSUAF.DAT files. This might be the case if the SYSUAF.DAT files are identical, that is, defined in the same user community, even though they are maintained separately. In a heterogeneous cluster you must install Message Router on more than one node. The installation procedure must modify the SYSUAF.DAT file and DECnet permanent database on every node. If the SYSUAF and the DECnet databases are shared between a set of nodes, however, you need only install Message Router on one node in the set. List the smallest number of nodes from which all the copies of SYSUAF.DAT and the DECnet database can be modified, and install Message Router on all nodes in the list. 2.3.4.5 Installing the Management Service Follow the guidelines for installing the Transfer Service on a cluster, described in Section 2.3.4.2, to install the Management Service component of Message Router. Once you have completed these preparations: o Turn to Section 2.3.5 if you are upgrading from Message Router Version 2.* o Turn to Section 2.3.6 if you are upgrading from Message Router Version 3.0 2-25 Preparing to Install Message Router o Turn to Section 2.3.7 if you are re-installing o If none of the above options apply to you, turn to Chapter 3 for details of the installation procedure 2.3.5 Preparing to Upgrade Message Router from Message Router Version 2.0 or 2.1 Complete the following steps to upgrade your Message Router system: o If Message Router is already running on your system, you must shut it down in your usual way. For instance: - If you are running Message Router Version 2.0, shut down Message Router, using the command: $ @SYS$MANAGER:MRSTOP Use this command on every node in a VAXcluster. - If you are running Message Router Version 2.1, that is, Message Router, MRGATE, and the exception reporting routines, shut down Message Router using the command: $ @SYS$MANAGER:MB$STOP Use this command on every node in a VAXcluster. o If you have Version 1.1 of Message Router, upgrade to Version 2.0 or 2.1 before installing Version 3.1 of Message Router. NOTE During installation, the MRMANAGER account is updated to point to a new directory. This is for completeness only: the MRMANAGER account is not required for the management of Message Router V3.1. o If you are upgrading from Message Router Version 2.0 or 2.1, old Message Router files are moved automatically to the new directory structure during installation: you do not have to do it yourself. The old directory structure and files are retained. 2-26 Preparing to Install Message Router o Backup your queue file, MRMAILBOX.DAT, directory file, MRMDIRECT.DAT, and message file(s), MRn.NBS. If a system failure occurs at a critical point during installation, some files may be corrupted. o If you are upgrading from Message Router Version 2.0 or 2.1 and you have stopped Message Router, you will not lose messages that are in transit. These messages will be delivered after Message Router has been configured. The installation procedure starts Message Router and DECnet in order to run the installation verification procedure (IVP). The IVP then shuts Message Router and DECnet down again. This ensures a successful installation in cases where you want to install on another node in a cluster. When you have completed these preparations, turn to Chapter 3 for details of the installation procedure. 2.3.6 Preparing to Upgrade Message Router from Message Router Version 3.0 Complete the following steps to upgrade your Message Router system: o If Message Router is already running on your system, you must shut it and all MAILbus components down in your usual way. For example: $ @SYS$MANAGER:MB$CONTROL STOP=(ER,...,DDS,TS,MS) Use this command on every node in a VAXcluster. o Backup your queue file, MRMAILBOX.DAT, directory file, MRMDIRECT.DAT, and message file(s), MRn.NBS. If a system failure occurs at a critical point during the installation, some files may be corrupted. o Backup the Directory Service database directory, [MB$.DDS.DB], in case of system failure during the installation. o During the installation, you are given the option of purging files from a previous installation. If you are upgarding from Message Router Version 3.0 and purge your files, as recommended, you must also remove the following jobs from the batch queue: 2-27 Preparing to Install Message Router - MR$TIDY.COM - DDS$TIDY.COM - DDS$DEFER.COM - DDS$REFRESH.COM If you do not remove all these jobs from the batch queues, they will fail when they execute, because the files no longer exist. To remove these jobs from the batch queue, type the following commands: $ SHOW QUEUE queuename /ALL where queuename is the name of the batch queue the jobs are running on. The default queue name is MB$BATCH. This shows the list of all the jobs queued to run on the specified batch queue. Examine the queue for the above entries and make a note of the entry numbers. You can delete the entries from the queue by typing: $ DELETE/ENTRY=entrynumber queuename where entrynumber is the entry number noted and queuename is the name of the queue. Delete each entry noted. o If you were running exception reporting in your previous installation, you must also delete the following jobs: - MB$NET from the batch queue MB$BATCH_nodename - MB$DDS from the batch queue MB$BATCH_nodename - MB$TS from the batch queue MB$BATCH_nodename where nodename is the name of the node you are using. You must submit these commands for each node in the cluster. The installation procedure starts Message Router and DECnet in order to run the installation verification procedure (IVP). The IVP then shuts Message Router and DECnet down again. This ensures a successful installation in cases where you want to install on another node in a 2-28 Preparing to Install Message Router cluster. (If, despite DIGITAL's recommendations, you do not stop DECnet before the insatllation, the IVP does not shut it down.) Once you have completed these preparations, turn to Chapter 3 for details of the installation procedure. 2.3.7 Preparing to Re-install Message Router Version 3.1 Complete the following steps to prepare to re-install Message Router Version 3.1. o If Message Router is running, stop it and all MAILbus components with the following command: $ @SYS$MANAGER:MB$CONTROL STOP=(ER,...,DDS,TS,MS) where ... is a list of the identifiers of other MAILbus components that are installed on your system. You must use this command on every node in a VAXcluster. o If you are re-installing Message Router Version 3.1, and have customized any files to your own requirements, do not select purging in Step 2 in Section 3.2. After installation, you will find a later version of the files superseding your customized version. To use your customized files, check that they meet your requirements and then delete the newer version of the files you do not need. o During the installation, you are given the option of purging files from a previous installation. If you are re-installing Message Router Version 3.1 and purge your files, as recommended, you must also remove the following jobs from the batch queue: - MR$TIDY.COM - DDS$TIDY.COM - DDS$DEFER.COM - DDS$REFRESH.COM If you do not remove all these jobs from the batch queues, they will fail when they execute, because the files no longer exist. 2-29 Preparing to Install Message Router To remove these jobs from the batch queue, type the following commands: $ SHOW QUEUE queuename /ALL where queuename is the name of the batch queue the jobs are running on. The default queue name is MB$BATCH. This shows the list of all the jobs queued to run on the specified batch queue. Examine the queue for the above entries and make a note of the entry numbers. You can delete the entries from the queue by typing: $ DELETE/ENTRY=entrynumber queuename where entrynumber is the entry number noted and queuename is the name of the queue. Delete each entry noted. o If you were running exception reporting in your previous installation, you must also delete the following jobs: - MB$NET from the batch queue MB$BATCH_nodename - MB$DDS from the batch queue MB$BATCH_nodename - MB$TS from the batch queue MB$BATCH_nodename where nodename is the name of the node you are using. You must submit these commands for each node in the cluster. The installation procedure starts Message Router and DECnet in order to run the installation verification procedure (IVP). The IVP then shuts Message Router and DECnet down again. This ensures a successful installation in cases where you want to install on another node in a cluster. Once you have completed these preparations, turn to Chapter 3 for details of the installation procedure. 2-30 Chapter 3 Installing Message Router 3.1 Starting the Installation This chapter explains how to install Message Router. You must make the preparations described in Chapter 2 before you install Message Router. If you are installing Message Router on VMS Version 5.0, you must also register and load your Message Router Product Authorization Key using the VMS License Management Utility. If you have not registered and loaded the Message Router Product Authorization Key, refer to the VMS License Management Utility Manual. VMSINSTAL is interactive and takes you step by step through the installation. Each step is fully described in this chapter. Remember that you can get on-line help by typing a question mark (?) in response to a prompt. If possible, use a hardcopy terminal to keep a record of the installation. Perform the following steps to install Message Router: 1 Invoke VMSINSTAL in the following way: a Log in to the VMS SYSTEM account. b Type the following command: $ @SYS$UPDATE:VMSINSTAL MR031 ddcu OPTIONS N where: MR031 identifies the product being installed ddcu is the name of the device where the distribution medium is to be mounted, for example MTA0 3-1 Installing Message Router OPTIONS N provides the option of reading or printing the on-line release notes NOTE If this is a re-installation of Message Router V3.1, you can omit the parameter OPTIONS N, if you have already read the release notes. c The procedure starts and displays: VAX/VMS Software Product Installation Procedure Vx.x It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. where dd-mmm-yyyy and hh:mm are the current date and time, and x.x is the VMS version number. d You may receive one or more of the following warning messages: %VMSINSTAL-W-LOWQUOTA, One or more account quotas may be too low. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. %VMSINSTAL-W-ACTIVE, The following processes are still active: If you receive any warning messages you are advised to exit from the installation procedure and fix the problem, as described in Chapter 2. Then restart the installation. If there are any active system processes the procedure lists them and asks: * Do you want to continue anyway [NO]? It is not advisable to continue. In particular, it is not advisable to continue if there are any active processes that use the Directory Service. Press RETURN to halt VMSINSTAL and ask users to log out (see Step 3 of Section 2.3.3). Then restart the installation procedure. If there are no active system processes, or if you want to continue the installation regardless of the warning messages, type YES. 3-2 Installing Message Router 2 The procedure asks: * Are you satisfied with the backup of your system disk [YES]? If the system disk has not recently been backed up, type NO to abort the installation, and make a backup copy. Otherwise, press RETURN to accept the default answer of YES. 3 The procedure instructs you to mount the distribution volume: Please mount the first volume of the set on ddcu * Are you ready? where ddcu is the device name you supplied in Step 1. Mount the first distribution volume on the device. When you have mounted the distribution volume, type YES. 4 The procedure confirms that the volume has been successfully mounted and displays: %MOUNT-I-MOUNTED, MR mounted on _ddcu The following products will be processed: MR V3.1 Beginning installation of MR V3.1 at HH:MM %VMSINSTAL-I-RESTORE, Restoring product saveset A... 5 If you have not specified OPTIONS N, the installation continues at Section 3.2. Otherwise, the procedure displays a menu of options relating to the release notes. The menu varies from VMS Version 4.* to 5.0. Release notes are available on-line and can be displayed and printed as required. Select the option you require. If you select the option to print the release notes, the procedure displays: * Queue name[SYS$PRINT]: 3-3 Installing Message Router Enter the name of a print queue. The procedure then displays a message indicating that the release notes have been successfully queued to the printer. If you do not specify a print queue, the output is directed to SYS$PRINT by default. 6 The procedure asks: * Do you want to continue the installation [NO]? You are advised to exit from the installation and read the release notes. Press RETURN to accept the default answer of NO. Otherwise, type YES. When you have read the release notes, you can restart the installation procedure, starting from Step 1 of this section, omitting the parameter OPTIONS N. 3.2 Running the Installation Procedure 1 The procedure confirms that the product's release notes have been moved to SYS$HELP, if appropriate, with the following message: %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP 2 If you are installing Message Router on VMS Version 4.6 or 4.7 or on MicroVMS, go to Step 3. If you are installing Message Router on VMS Version 5.0, VMSINSTAL displays details of the product that you want to install: Product: MESSAGE-ROUTER Producer: DEC Version: 3.1 Release Date: dd-mmm-yyyy VMSINSTAL displays: * Does this product have an authorization key registered and loaded? 3-4 Installing Message Router If you have not registered and loaded the Product Authorization Key for Message Router Version 3.1, type NO to abort the installation, and refer to the VMS License Management Utility Manual. When you have registered and loaded the Message Router Product Authorization Key, start the installation procedure again. If the Product Authorization Key for Message Router is registered and loaded, type YES. 3 VMSINSTAL displays: * Do you want help text printed before every question [NO]? Help is available for all questions asked during the installation. If you want to see the explanation before each question, type YES and press RETURN. Otherwise, press RETURN. NOTE If you choose not to see all the help, you can still get help for any question by typing a question mark (?) as a response. 4 VMSINSTAL displays: * Do you want to purge files replaced by this installation [YES]? If you want the installation procedure to purge files replaced by this installation, press RETURN. Otherwise, type NO and press RETURN. 5 VMSINSTAL displays: * Do you want to run the IVP after the installation [YES]? An installation verification procedure (IVP) is provided to indicate whether the installation has succeeded. If you want to run the IVP immediately after the installation has finished, press RETURN. If you do not want to run the procedure, type NO and press RETURN. You are strongly recommended to run the IVP after installation. 6 If the procedure finds data from a Message Router Version 3.* installation, VMSINSTAL displays: 3-5 Installing Message Router A Message Router V3.* system has been found. Any data from this system will be included in the current installation, unless you choose to overwrite it with data from a previous V2.* system. * Do you want to keep data from a previous installation of MR V2.* [NO]? If the procedure does not find data from a Message Router Version 3.* installation, VMSINSTAL displays: * Do you want to keep data from a previous installation of MR V2.* [NO]? NOTE If you do not keep data from the most recent Message Router installation that has been running on your system, you will lose all messages that are in the process of being delivered. If there is data from previous installations of both Version 2.* and Version 3.*, be very careful when you answer this question. Decide whether you want to keep data from a previous V2.* installation, and type your reply of YES or press RETURN to accept the default accordingly. If you type YES, and there is data from both V2.* and V3.*, VMSINSTAL displays: Any data from the previous V2.* system will be used in the current installation, and will overwrite any V3.* data. If you have V3.* data that you do not want to lose, press CTRL/Y to abandon the installation procedure. If you do not want the V2.* data to overwrite the V3.* data, abandon the installation. 7 If you have replied NO to Step 6, the installation procedure continues at Step 9. Otherwise, the procedure displays: 3-6 Installing Message Router * What is the existing Message Router initialization file? If an initialization file can be found, this is offered as a default. Press RETURN if you want to accept the default Message Router initialization file. Otherwise, type the name noted in Step 8 of Section 2.3.3. 8 VMSINSTAL displays: * What is the existing Message Router directory? If a directory can be found, this is offered as a default. Press RETURN if you want to accept the default directory. Otherwise, type the directory specification noted in Step 10 of Section 2.3.3. 9 VMSINSTAL displays: * What device is to be used for the MBMANAGER account? If a previous device name can be found for the MBMANAGER account, this is offered as a default. Press RETURN to accept the default location provided, or enter the device name noted in Step 9 of Section 2.3.3. VMSINSTAL checks that the specified device is available. If the specified device is unavailable, VMSINSTAL displays an error message and returns to this question. 10 VMSINSTAL displays: * What is the UIC for the MBMANAGER account? If a previous UIC can be found, this is offered as a default. If you are upgrading from Version 2.*, you can either accept the default or enter the UIC noted in Step 11 of Section 2.3.3 and press RETURN. You must give the UIC's numerical format. If you are upgrading from Version 3.0, or re-installing Version 3.1, you must accept the default. 11 VMSINSTAL displays: You will now be prompted for the password for the Message Router accounts, and then for a confirmation of the password. * What is the password for the Message Router accounts: 3-7 Installing Message Router Enter the password of the Message Router accounts. There are some strings that you must not include in your password. If you include any of these strings, the password is rejected and the installation procedure displays an error message asking you to enter the password again. The strings that must not be included are: MAIL, MANAGER, DDS, GATE, ROUTE, MESSAGE, PASSWORD. 12 VMSINSTAL displays: * Confirm the password for the Message Router accounts: Re-type the password. If the password entered here does not correspond to the password entered in the previous step, VMSINSTAL displays an error message and returns to the previous step. 13 VMSINSTAL displays: You have answered all the questions for the Message Router Installation. Message Router is now being installed. The installation takes approximately 60 minutes depending on the system configuration and media type. 14 The procedure displays a series of messages that tell you that the generation phase of the Message Router installation is proceeding. There is a pause between each message. If this is an upgrade installation, the procedure continues at Step 15; otherwise, the following messages are displayed: %MR-I-CREACC, Creating the MBMANAGER account %MR-I-CREACC, Creating the MBWATCH account %MR-I-CREACC, Creating the MRNET account %MR-I-CREACC, Creating the MRMANAGER account %MR-I-CREACC, Creating the DDSNET account If the installation procedure finds an account or directory it does not expect, the following message is displayed: %MR-I-ACCEXIST, accountname account already existed. The account already exists. It should only exist where Message Router is re-installed. The installation is continuing. 3-8 Installing Message Router You are advised to check that the modified account does not have another use. The string accountname is the name of the account. Other messages relating to this warning may also be displayed. The installation procedure continues. %MR-I-IGNERR, Ignore the following reports which may occur on NCP object definition: %NCP-I-NMLRSP, listener response - Success Object = MRLISTEN %NML-I-RECDELET, Database entry deleted %NCP-I-NMLRSP, listener response - Success Object = DDSLSTN %NML-I-RECDELET, Database entry deleted %MR-I-CHECDIRS, Checking directories %MR-I-DEVICE, Checking Message Router device ddcu: %MR-I-CHECQUOT, Checking quota use on ddcu: Setting disk quota for Message Router accounts to 30000 blocks with an overdraft of 0 blocks. If a quota file entry for this UIC already exists, no change will be made to the quota allocation. %MR-I-CREMRDIR, Creating directory ddcu:[MB$] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MR] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MR.WRK] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MR.MSG1] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MR.MSG2] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MR.SCR] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MR.DB] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MB] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.TOOLS] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MB.MB$COM] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MB.MB$WORK] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.MB.MB$SCRATCH] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.DDS] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.DDS.WRK] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.DDS.SCR] %MR-I-CREMRDIR, Creating directory ddcu:[MB$.DDS.DB] %VMSINSTAL-I-RESTORE, Restoring product saveset B... %MR-I-LNKDDS, Linking the DDS images %MR-I-LNKDDSMSG, ...Linking the DDS Message file %MR-I-LNKDDSSHAR, ...Linking the DDS shareable image %MR-I-LNKDDSSERV, ...Linking the DDS Server %MR-I-LNKDDSLSTN, ...Linking the DDS Listener 3-9 Installing Message Router %MR-I-LNKDDSEXTP, ...Linking the DDS external processors %MR-I-LNKDDSTMPUPD, ...Linking the DDS V3.0/V3.1 Template Update Utility %MR-I-SETDDSFILES, Setting DDS file ownership and protection %MR-I-ASGNDDSFILES, Assigning DDS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset C... %MR-I-LNKMR, Linking the TS images %MR-I-LNKMRMSG, ...Linking the TS Message file %MR-I-LNKMRTALK, ...Linking the TS Talker %MR-I-LNKMRLSTN, ...Linking the TS Listener %MR-I-LNKMRMAN, ...Linking the TS Manager %MR-I-LNKMRLOG, ...Linking the TS Logger %MR-I-LNKMRSHAR, ...Linking the TS Shareable image %MR-I-LNKMRNBS, ...Linking the TS NBS Dump utility %MR-I-LNKMRSTATS, ...Linking the TS Statistics utility %MR-I-SETMRFILES, Setting TS file ownership and protection %MR-I-ASGNMRFILES, Assigning TS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %VMSINSTAL-I-RESTORE, Restoring product saveset F... %VMSINSTAL-I-RESTORE, Restoring product saveset G... %MR-I-LNKMBMAN, Linking the MR Management images %MR-I-LNKMBUTIL, ...Linking the MB Utility %MR-I-LNKMBMAN, ...Linking the MB Manager %MR-I-LNKMBMSG, ...Linking the MB Message File %MR-I-CREMRDIR, Creating directory SYS$SYSROOT:[SYSTEST.MB] %MR-I-SETMBFILES, Setting MR file ownership and protection %MR-I-ASGNMBFILES, Assigning MR files to target directories The installation procedure continues at Step 16. 15 If this is an upgrade installation, the following messages are displayed: %MR-I-MODACC, Modifying the MBMANAGER account %MR-I-MODACC, Modifying the MBWATCH account %MR-I-MODACC, Modifying the MRNET account %MR-I-MODACC, Modifying the MRMANAGER account %MR-I-MODACC, Modifying the DDSNET account If the installation procedure finds an account or directory it does not expect, the following message is displayed: %MR-I-ACCEXIST, accountname account already existed. 3-10 Installing Message Router The account already exists. It should only exist where Message Router is re-installed. The installation is continuing. You are advised to check that the modified account does not have another use. where accountname is the name of the account. Other messages relating to this warning may also be displayed. %MR-I-IGNERR, Ignore the following reports which may occur on NCP object definition: Ignore> %NCP-I-NMLRSP, listener response - Unrecognized component, Object %NCP-I-NMLRSP, listener response - Success Object = MRLISTEN %NML-I-RECDELET, Database entry deleted %NCP-I-NMLRSP, listener response - Success Object = DDSLSTN %NML-I-RECDELET, Database entry deleted %MR-I-CHECDIRS, Checking directories %MR-I-DEVICE, Checking Message Router device ddcu: %MR-I-CHECQUOT, Checking quota use on ddcu: Setting disk quota for Message Router accounts to 30000 blocks with an overdraft of 0 blocks. If a quota file entry for this UIC already exists, no change will be made to the quota allocation. %VMSINSTAL-I-RESTORE, Restoring product saveset B... %MR-I-LNKDDS, Linking the DDS images %MR-I-LNKDDSMSG, ...Linking the DDS Message file %MR-I-LNKDDSSHAR, ...Linking the DDS shareable image %MR-I-LNKDDSSERV, ...Linking the DDS Server %MR-I-LNKDDSLSTN, ...Linking the DDS Listener %MR-I-LNKDDSEXTP, ...Linking the DDS external processors %MR-I-LNKDDSTMPUPD, ...Linking the DDS V3.0/V3.1 Template Update Utility %MR-I-SETDDSFILES, Setting DDS file ownership and protection %MR-I-ASGNDDSFILES, Assigning DDS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset C... %MR-I-LNKMR, Linking the TS images %MR-I-LNKMRMSG, ...Linking the TS Message file %MR-I-LNKMRTALK, ...Linking the TS Talker %MR-I-LNKMRLSTN, ...Linking the TS Listener 3-11 Installing Message Router %MR-I-LNKMRMAN, ...Linking the TS Manager %MR-I-LNKMRLOG, ...Linking the TS Logger %MR-I-LNKMRSHAR, ...Linking the TS Shareable image %MR-I-LNKMRNBS, ...Linking the TS NBS Dump utility %MR-I-LNKMRSTATS, ...Linking the TS Statistics utility The following message appears if the upgrade installation is keeping data from Message Router Version 2.*: %MR-I-MOVMRV2, Retrieving files from TS V2.* database The procedure then displays: %MR-I-SETMRFILES, Setting TS file ownership and protection %MR-I-ASGNMRFILES, Assigning TS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %VMSINSTAL-I-RESTORE, Restoring product saveset F... %VMSINSTAL-I-RESTORE, Restoring product saveset G... %MR-I-LNKMBMAN, Linking the MR Management images %MR-I-LNKMBUTIL, ...Linking the MB Utility %MR-I-LNKMBMAN, ...Linking the MB Manager %MR-I-LNKMBMSG, ...Linking the MB Message File %MR-I-SETMBFILES, Setting MR Management file ownership and protection %MR-I-ASGNMBFILES, Assigning MR Management files to target directories 16 After VMSINSTAL has marked the files for moving to the Message Router directories, more messages are displayed. The generation phase of the Message Router installation is now complete. In order to tailor Message Router to your requirements, you must use the configuration procedure, SYS$MANAGER:MB$CONFIG.COM. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... You do not have a working system until Message Router has been configured. See the Message Router Configuration Guide for details of the configuration procedure. If you have chosen to run the IVP, turn to Chapter 4 and follow the instructions there. You are advised to run the IVP to check that the installation has completed successfully. 3-12 Chapter 4 Running the IVP 4.1 Introduction The installation verification procedure (IVP) checks that all components of Message Router have been installed correctly. If you selected the IVP in the installation, VMSINSTAL automatically runs the IVP when the installation is completed. It is advisable to select the IVP because this provides the only check that Message Router has been installed properly. The IVP sets up a test database to check that the installation is correct, so you do not need to configure Message Router before running the IVP. A successful IVP does not mean that Message Router is ready to use. Before you use Message Router, you must configure it to your own requirements. See the Message Router Configuration Guide for details of how to configure Message Router. The IVP produces a message to confirm that all components of Message Router have been installed successfully. 4.2 Running the IVP If you requested to run the IVP, VMSINSTAL displays: IVP for Message Router Version V3.1 This is the installation verification procedure (IVP) for Message Router. It checks that the components of Message Router are installed successfully on your system. 4-1 Running the IVP Starting Management Service ------------------------------------------------------------------ TRANSFER SERVICE V3.1 IVP This is the installation verification procedure (IVP) for the Transfer Service. It tests whether or not the Transfer Service is successfully installed on your system. The procedure starts by checking that all the files for the Transfer Service exist and are the correct size. It then starts DECnet and MRMAN if necessary. The verification procedure creates a test mailbox, using the MRMAN utility, and sends a test message to the mailbox. The verification procedure fetches the test message from the mailbox and displays it, and then shuts down DECnet and MRMAN. The IVP has not completed successfully until you have received this test message. ------------------------------------------------------------------ Transfer Service V3.1 file check The total number of files is 27. All files exist and are the correct size. End of Transfer Service V3.1 file check. ------------------------------------------------------------------ This is MRMAN Starting Transfer Service 4-2 Running the IVP This is MRMAN %Added MB$TSIVP, This is MRMAN %Using mailbox MB$TSIVP at node ORANGE % Message from: MB$TSIVP % Subject: TEST ************************************************** Output of this test message indicates that the Transfer Service V3.1 is installed successfully on your system. ************************************************** %Finished reading from mailbox MB$TSIVP %Directory entry MB$TSIVP deleted Shutting down the Transfer Service The Transfer Service V3.1 IVP was successful END OF TS V3.1 IVP ================================================================== DIRECTORY SERVICE V3.1 IVP This is the installation verification procedure (IVP) for the Directory Service. It tests whether or not the Directory Service is successfully installed on your system. The procedure completes the following steps: 1. Checks that the Directory Service files exist and that they are the correct size 2. Retrieves preset entries from the database ------------------------------------------------------------------ Directory Service V3.1 file check The total number of files is 8. 4-3 Running the IVP All files exist and are the correct size. End of Directory Service V3.1 file check. ------------------------------------------------------------------ Starting the Directory Service The Directory Service V3.1 IVP was successful END OF DDS V3.1 IVP Shutting down Directory Service ================================================================== MANAGEMENT SERVICE V3.1 IVP This is the installation verification procedure (IVP) for Management Service. It tests whether or not the Management Service is successfully installed on your system. The procedure checks that the Management Services files exist and that they are the correct size. ------------------------------------------------------------------ Management Service V3.1 file check The total number of files is 73. All files exist and are the correct size. End of Management Service V3.1 file check. ------------------------------------------------------------------ The Management Service V3.1 IVP was successful END OF MS V3.1 IVP ================================================================== Installation verification was successfully performed for all 3 components of Message Router Shutting down Management Service 4-4 Running the IVP The Message Router V3.1 IVP completed successfully Installation of MR V3.1 completed at 09:06 VMSINSTAL procedure done at 09:07 4-5 Running the IVP 4.3 Checking the IVP If the IVP has been completely successful, it displays: The Message Router V3.1 IVP completed successfully Installation of MR V3.1 completed at hh:mm where hh:mm represents the current time in hours and minutes. VMSINSTAL procedure done at hh:mm If the IVP fails, the IVP displays: Please re-install Message Router If you receive this message, you must re-install Message Router. If the IVP fails, but does not indicate the reason for the failure, you can set VERIFY on the installation procedure, so that the IVP displays more information on your screen. You can specify the component of Message Router you want verified by using one of the following commands before starting the installation procedure: $ VFY$TSCVP=1 $ VFY$DDSVP=1 $ VFY$MBMBVP=1 where: o TSCVP specifies the Transfer Service component o DDSVP specifies the Directory Service component o MBMBVP specifies the Management Service component You can use any or all of these commands before the same installation procedure. You then install Message Router in the usual way. Turn to Chapter 5 for what to do after a successful installation. 4-6 Chapter 5 After the Installation After the installation has been completed, you should: 1 Restart DECnet. 2 Pass on details of the installation to the person doing the configuration. 3 Install other MAILbus products as necessary for your network. Refer to the appropriate installation guide for details of the installation procedure for the products you require. 4 Enable logins as follows: $ SET LOGINS/INTERACTIVE=n where n is the number of logins noted in Chapter 2. 5 Ensure that Message Router is configured, as you cannot run Message Router unless it is configured 5.1 Restarting DECnet After successfully installing Message Router, you must restart DECnet by typing the following command: $ @SYS$MANAGER:STARTNET You must restart DECnet on each node in a cluster. 5-1 After the Installation 5.2 Configuration Information You must configure Message Router before you can use it. The configuration procedure is described in the Message Router Configuration Guide. To help in configuring Message Router, note the name of device on which you installed Message Router. 5.3 Location of the Message Router Software Figure 5-1 shows the directory structure of the Message Router software. Figure 5-1: Message Router Directory Structure MB$ | _______________________________________________________________ | | | | | | | | MR DDS MB TOOLS | | | ______________ | ______________ | | | | | | | | WRK DB SCR MSGN | MB$WORK MB$COM MB$SCRATCH ___________________ | | | DB WRK SCR When you have completed the installation, the Message Router software occupies about 7000 blocks of disk space, and is distributed as shown in Table 5-1. The file sizes are approximate only, and if you have just upgraded an installation some of them may differ considerably. The file protection codes are the recommended settings that are issued in the distribution kit. Table 5-1: Location of the Transfer Service Files Directory, Definition and File Size Protection (S,O,G,W) --------------------------------------------------------------------- SYS$COMMON:[SYSEXE] MRTALK.EXE 633 (RWED,RWED,RE,RE) MRLSTN.EXE 648 (RWED,RWED,RE,RE) MRLOG.EXE 99 (RWED,RWED,RE,RE) 5-2 After the Installation Directory, Definition and File Size Protection (S,O,G,W) --------------------------------------------------------------------- MRSTAT.EXE 49 (RWED,RWED,RE,RE) MRMAN.EXE 476 (RWED,RWED,,) MRLISTEN.COM 3 (RWED,RWED,RE,RE) [MB$.MR.WRK] MRSTOP_0.DAT 0 (RWED,RWED,RE,RE) MB$TALK_RUN_TEMPLATE.COM 19 (RWED,RWED,RE,RE) MB$TALK_SCHEDULE_TEMPLATE.COM 22 (RWED,RWED,RE,RE) MB$TALK_NOTIFY_TEMPLATE.COM 17 (RWED,RWED,RE,RE) MB$TALK_RUN_DEF.COM 18 (RWED,RWED,RE,RE) MRMWRK.COM 4 (RWED,RWED,RE,E) MR$NODES_DEF.DAT 1 (RWED,RWED,RE,E) MRINITUTL.COM 99 (RWED,RWED,RE,E) MRINITHELP.COM 48 (RWED,RWED,RE,E) MRINITDEF.DAT 33 (RWED,RWED,RE,E) SYS$COMMON:[SYSLIB] MRAPPSHAR.EXE 166 (RWED,RWED,RE,RE) MRSHAR.EXE 689 (RWED,RWED,RE,RE) SYS$COMMON:[SYSMSG] MRMSG.EXE 49 (RWED,RWED,RE,RE) MRAPPMSG.EXE 11 (RWED,RWED,RE,RE) SYS$COMMON:[SYSMGR] MB$TALK_NOTIFY_DEF.COM 17 (RWED,RWED,RE,E) MB$TALK_SCHEDULE_DEF.COM 21 (RWED,RWED,RE,E) MR$TIDY.COM 70 (RWED,RWED,RE,RE) [MB$.TOOLS] MR$COMPRESS.COM 17 (RWED,RWED,RE,E) MB$REPOST.COM 15 (RWED,RWED,RE,E) MRNBSDMP.EXE 211 (RWED,RWED,RE,RE) MR$CVP.DAT 2 (RWED,RE,RE,RE) 5-3 After the Installation Table 5-2: Location of the Management Service Files Directory, Definition and File Size Protection (S,O,G,W) --------------------------------------------------------------------- SYS$COMMON:[SYSTEST.MB] MB$CVP.COM 20 (RWED,RE,RE,RE) MB$CVPSETUP.COM 7 (RWED,RE,RE,RE) MB$CVPFILES.COM 10 (RWED,RE,RE,RE) MB$DDSCVP.COM 17 (RWED,RE,RE,RE) MB$MSCVP.COM 9 (RWED,RE,RE,RE) MB$TSCVP.COM 22 (RWED,RE,RE,RE) SYS$COMMON:[SYSMSG] XPORTMSG.EXE 16 (RWED,RWED,RE,RE) MB$MSG_CONFIG.EXE 107 (RWED,RWED,RE,RE) MB$MSG.EXE 69 (RWED,RWED,RE,RE) SYS$COMMON:[SYSMGR] MB$CONFIG.COM 168 (RWED,RWED,RE,RE) MB$$TS_CONFIG.COM 88 (RWED,RWED,RE,RE) MB$$DDS_CONFIG.COM 114 (RWED,RWED,RE,RE) MB$$ER_CONFIG.COM 34 (RWED,RWED,RE,RE) MB$$A1_CONFIG.COM 18 (RWED,RWED,RE,RE) MB$CONTROL.COM 20 (RWED,RWED,RE,RE) MB$$ER_START.COM 33 (RWED,RWED,RE,RE) MB$$ER_STOP.COM 11 (RWED,RWED,RE,RE) MB$$MS_START.COM 31 (RWED,RWED,RE,RE) MB$$MS_STOP.COM 12 (RWED,RWED,RE,RE) MB$$TS_START.COM 32 (RWED,RWED,RE,RE) MB$$TS_STOP.COM 12 (RWED,RWED,RE,RE) MRSTOP.COM 4 (RWED,RWED,RE,RE) MB$LOCATION.COM 7 (RWED,RWED,RE,RE) MB$CONFIG.FDL 3 (RWED,RWED,RE,RE) MB$$DDS_START.COM 22 (RWED,RWED,RE,RE) MB$$DDS_STOP.COM 11 (RWED,RWED,RE,RE) MRSTART.COM 5 (RWED,RWED,RE,RE) MB$$MS_CONFIG.COM 50 (RWED,RWED,RE,RE) MB$CNFTXN.FDL 2 (RWED,RWED,RE,RE) MB$DDS_ADD_TEMPLATE.COM 342 (RWED,RWED,RE,E) MB$DDS_UPDATE_TEMPLATE.COM 10 (RWED,RWED,RE,RE) [MB$.TOOLS] MB$LOCATION_TEMPLATE.COM 6 (RWED,RWED,RE,RE) MB$MRNET.COM 4 (RWED,RWED,RE,RE) MB$DDSNET.COM 4 (RWED,RWED,RE,RE) 5-4 After the Installation Directory, Definition and File Size Protection (S,O,G,W) --------------------------------------------------------------------- MB$CVP.DAT 6 (RWED,RE,RE,RE) MB$ER_UPGRADE.COM 8 (RWED,RWED,RE,RE) MB$MBMANAGER.COM 4 (RWED,RWED,RE,RE) MB$MBWATCH.COM 3 (RWED,RWED,RE,RE) MB$MRMANAGER.COM 4 (RWED,RWED,RE,RE) SYS$COMMON:[SYSHLP] MB$CONFIG.HLB 198 (RWED,RWED,RE,RE) MRMAN.HLB 62 (RWED,RWED,RE,RE) MBMAN.HLB 284 (RWED,RWED,RE,RE) MB$A1_CONFIG.HLB 20 (RWED,RWED,RE,RE) [MB$.MB.MB$COM] MB$INIT.COM 26 (RWED,RWED,RE,RE) MB$MAILER.COM 9 (RWED,RWED,RE,E) MB$ADDREP.COM 14 (RWED,RWED,RE,E) MB$CHECKDEV.COM 15 (RWED,RWED,RE,E) MB$ERRORS.DAT 16 (RWED,RWED,RE,E) MB$TS_ER.COM 50 (RWED,RWED,RE,E) MB$DDS_ER.COM 53 (RWED,RWED,RE,E) MB$NET_ER.COM 56 (RWED,RWED,RE,E) MB$A1_ER.COM 17 (RWED,RWED,RE,E) MB$A1_ERRORS.DAT 2 (RWED,RWED,RE,E) [MB$.MB.MB$WORK] MB$VERSION.DAT 1 (RWED,RWED,RE,RE) MB$MR$CONFIG$CUSTOMIZED.DAT 51 (RWED,RWED,RE,RE) MB$A1$CONFIG$CUSTOMIZED.DAT 2 (RWED,RWED,RE,RE) MB$MR$CONFIG$DEFAULT.DAT 53 (RWED,RWED,RE,RE) MB$A1$CONFIG$DEFAULT.DAT 2 (RWED,RWED,RE,RE) MB$STOP.DAT 0 (RWED,RWED,RE,RE) DDS$CACHE_AIF.FDL 3 (RWED,RWED,RE,RE) DDS$CACHE_DB.FDL 3 (RWED,RWED,RE,RE) DDS$INQUE.FDL 3 (RWED,RWED,RE,RE) DDS$NETQUE.FDL 2 (RWED,RWED,RE,RE) DDS$NIF.FDL 3 (RWED,RWED,RE,RE) DDS$OUTQUE.FDL 2 (RWED,RWED,RE,RE) DDS$PERM_AIF.FDL 3 (RWED,RWED,RE,RE) DDS$PERM_DB.FDL 2 (RWED,RWED,RE,RE) SYS$COMMON:[SYSEXE] MBMAN.EXE 267 (RWED,RWED,RE,RE) MBUTIL.EXE 46 (RWED,RWED,RE,RE) 5-5 After the Installation Table 5-3: Location of the Directory Service Files Directory, Definitions and Files Size Protection (S,O,G,W) --------------------------------------------------------------------- SYS$COMMON:[SYSMGR] DDS$TIDY.COM 79 (RWED,RWED,RE,RE) DDS$DEFER.COM 43 (RWED,RWED,RE,RE) DDS$REFRESH.COM 44 (RWED,RWED,RE,RE) DDS$START.COM 28 (RWED,RWED,RE,RE) DDS$_STOP_55.DAT 0 (RWED,RWED,RE,RE) SYS$COMMON:[SYSEXE] DDS$SERV.EXE 370 (RWED,RWED,RE,RE) DDS$LSTN.EXE 330 (RWED,RWED,RE,RE) DDS$TMPUPD_V30_V31.EXE 374 (RWED,RWED,RE,RE) SYS$COMMON:[SYSLIB] DDS$SHAR.EXE 424 (RWED,RWED,RE,RE) DDS$CALLOUT.EXE 26 (RWED,RWED,RE,RE) SYS$COMMON:[SYSMSG] DDS$MSG.EXE 55 (RWED,RWED,RE,RE) [MB$.TOOLS] DDS$COMPRESS.COM 19 (RWED,RWED,RE,E) DDS$CVP.DAT 1 (RWED,RE,RE,RE) DDS$BACKUP.COM 14 (RWED,RWED,RE,RE) For Version 3.1 re-installations, any existing messages are moved to new message areas, standard files are moved into the new database structure, but the old directories (with any extra files they held) are not deleted. 5.4 After an Installation on a Homogeneous Cluster Message Router creates a file, RIGHTSLIST.DAT, if that file does not already exist. After installing Message Router on a homogeneous cluster, if you have a RIGHTSLIST.DAT file on your system in the SYS$SPECIFIC:[SYSEXE] directory, rename it to SYS$COMMON:[SYSEXE], using the following command: 5-6 After the Installation $ RENAME SYS$SPECIFIC:[SYSEXE]RIGHTLIST.DAT - SYS$COMMON:[SYSEXE]RIGHTSLIST.DAT 5.5 After an Installation on a Heterogeneous Cluster After installing Message Router on a heterogeneous cluster, copy MB$LOCATION from SYS$COMMON:[SYSMGR] to SYS$SPECIFIC:[SYSMGR], using the following command: $ COPY SYS$COMMON:[SYSMGR]MB$LOCATION - SYS$SPECIFIC:[SYSMGR]MB$LOCATION 5.6 After a Message Router Installation on MicroVMS The Object and Shareable Image libraries are needed only during the installation of Message Router. As they are not needed to run Message Router, disk space can be released by removing them from a MicroVMS system. NOTE If you are going to install other MAILbus products, such as the Message Router VMSmail Gateway, this software will be needed. In this case, you should remove the libraries after you have installed all your MAILbus products. The Object and Shareable Image Libraries is sub-option F in option PROG. To remove the libraries from a MicroVMS system, first check that no one is using the software. If it is not being used, log in to the SYSTEM account and use the command procedure REMOVE.COM to remove the MicroVMS options or suboptions that you have installed. Complete the following steps: 1 Log in to the SYSTEM account 2 Invoke the REMOVE.COM command procedure as follows: $ @SYS$UPDATE:REMOVE 5-7 After the Installation The procedure prompts you for the name of the option or suboption that you want to remove. The procedure may take several minutes. You cannot remove a suboption without first specifying the option in which it is contained. When you have removed the software that you do not require you have no further tasks to perform. You can now install other MAILbus components, as described in the relevant installation guides, or you can configure Message Router Version 3.1 as described in the Message Router Configuration Manual. 5.7 After a Message Router Installation on VMS Version 5.0 The Object and Shareable Image libraries are needed only during the installation of Message Router. As they are not needed to run Message Router, you can release some disk space by removing them from your VAX or MicroVAX. If you are using a MicroVAX, releasing disk space might be particularly useful. To remove the libraries from your system, first check that no one is using the software. If it is not being used, log in to the SYSTEM account and use the VMS Tailoring Utility to tailor the software off your system. Complete the following steps: 1 Invoke VMSTAILOR in the following way: a Log in to the SYSTEM account: b Type the following command: $ RUN SYS$UPDATE:VMSTAILOR c The procedure starts and displays: This is the VMS tailoring utility. It lets you customize VMS for your particular system. You do this by identifying classes and subclasses of VMS files that you want to add or delete. VMSTAILOR has three phases: - First, VMSTAILOR asks if you want to tailor your system by adding files ("tailor on") or by deleting files ("tailor off"). 5-8 After the Installation - Second, if you choose the "tailor on" procedure, VMSTAILOR lists each class of VMS files and asks if you want to include them on the system disk. If you choose the "tailor off" procedure, VMSTAILOR lists each class of VMS files and asks if you want to delete them from the system disk. - Third, VMSTAILOR carries out your instructions. NOTE: To cancel VMSTAILOR during the first and second phases, press Control-C, Control-Y, or Control-Z. If you cancel VMSTAILOR during the third phase, you may end up with a partially tailored disk. Do you want to tailor files "ON" or "OFF"? Type OFF and press RETURN. 2 The procedure displays: TAILOR-OFF ---------- You will now be prompted with a list of the classes and subclasses of VMS files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to remove a class or subclass from your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files will only be deleted if you remove the ENTIRE class. If you choose to keep any subclass, this set of files is not deleted. Total size of the system disk is nnnnnnn blocks. Total space used on the system disk is nnnnnnn blocks. Total space left on the system disk is nnnnnnn blocks. CLASS - Network support Size of entire class (with subclasses): 1442 Size of common files required for any subclass: 1221 Do you wish to select the entire class (default = NO)? where nnnnnnn are numbers. Press RETURN to accept the default answer, because you do not want to remove the entire class. 5-9 After the Installation 3 The procedure displays: Do you wish to select any of its subclasses (default NO)? Press RETURN to accept the default answer, because you do not want to remove any of the subclasses. 4 The procedure displays: CLASS - Programming Support Size of entire class (with subclasses): 9749 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Press RETURN to accept the default answer, because you do not want to remove the entire class. The procedure displays: Do you wish to select any of its subclasses (default = NO)? Type YES and press RETURN, because the Object and Shareable Image Libraries are a subclass of this class. 5 The procedure displays: Select the subclasses that you wish to use: For each subclass, press RETURN except for the following subclass: SUBCLASS - Object and Shareable Image Libraries (3480 blocks) [NO]: Type YES and press RETURN. 6 For all the remaining classes and subclasses, accept the default answer NO, because you do not want to remove any of those classes or subclasses. 7 The procedure then asks whether you want to delete all the selected options. Answer YES. The procedure then deletes the libraries, and displays the names of the files that it is deleting. When you have removed the software that you do not require you have no further tasks to perform. You can now install other MAILbus components, as described in the relevant installation guides, or you can configure Message Router Version 3.1 as described in the Message Router Configuration Manual. 5-10 Appendix A Distribution Media This appendix contains a list of the files contained in the seven installation savesets. A-1 The files supplied in installation saveset A are: DDS$PROTN.COM DDS$FILES.DAT DDS$IMAGES.DAT MR$PROTN.COM MR$FILES.DAT MR$IMAGES.DAT MR$POSTPRO.COM MB$PROTN.COM MB$FILES.DAT MB$IMAGES.DAT MB$POSTPRO.COM KITINSTAL.COM MBREPLACE.TPU MR$SYSGEN.DAT MR031.RELEASE_NOTES MB$CVP.COM MB$CVPSETUP.COM MB$CVPFILES.COM MB$DDSCVP.COM MB$MSCVP.COM MB$TSCVP.COM XPORT.OLB XPORTMSG.EXE A-2 The files supplied in installation saveset B are: DDS$LINK.COM DDSSERV.OLB DDSLSTN.OLB DDSCALL.OLB DDSMISC.OLB DDSMUNGE.OLB DDSDB.OLB DDSNET.OLB DDS$MSG.OBJ DDS$SHAR_UNIVERSAL.OPT DDS$START.COM DDS$_STOP_55.DAT DDS$CVP.DAT DDSCOMMON.OLB DDSFACI.OLB DDSTREED.OLB DDSFILESD.OLB A-3 The files supplied in installation saveset C are: MR$LINK.COM MR.OLB MRVMS.OLB MRMIS.OLB MRMAN.OLB MRLOG.OLB MRSTAT.OLB NBS.OLB MRMSG.OLB MRAPPSHAR.OLB MRAPPMSG.OBJ MB$TALK_NOTIFY_TEMPLATE.COM MB$TALK_SCHEDULE_TEMPLATE.COM MB$TALK_RUN_TEMPLATE.COM MB$TALK_NOTIFY_DEF.COM MB$TALK_SCHEDULE_DEF.COM MB$TALK_RUN_DEF.COM MRMWRK.COM MR$TIDY.COM MR$COMPRESS.COM MB$REPOST.COM MR$NODES_DEF.DAT MRSTOP_0.DAT MRINITUTL.COM MRINITHELP.COM MRINITDEF.DAT MRMAN.HLB MRLISTEN.COM MR$CVP.DAT A-4 The files supplied in installation saveset D are: MB$LOCATION_TEMPLATE.COM MB$DDS_ADD_TEMPLATE.COM MB$CONTROL.COM MB$$ER_START.COM MB$$ER_STOP.COM MB$$MS_START.COM MB$$MS_STOP.COM MB$$TS_START.COM MB$$TS_STOP.COM MB$$DDS_START.COM MB$$DDS_STOP.COM MRSTART.COM MRSTOP.COM DDS$TIDY.COM DDS$COMPRESS.COM DDS$BACKUP.COM DDS$DEFER.COM DDS$REFRESH.COM MB$ER_UPGRADE.COM DDS$INQUE.FDL DDS$NETQUE.FDL DDS$NIF.FDL DDS$OUTQUE DDS$PERM_DB.FDL DDS$PERM_AIF.FDL DDS$CACHE_DB.FDL DDS$CACHE_AIF MB$DDS_UPDATE_TEMPLATE.COM A-5 The files supplied in installation saveset E are: MBMAN.OLB MBUTIL.OLB MB$MSG.OBJ MB$MSG_CONFIG.OBJ MB$LINK.COM MBMAN.HLB MB$CONFIG.HLB MB$A1_CONFIG.HLB MRMAILBOX.FDL MRMDIRECT.FDL A-6 The files supplied in installation saveset F are: MB$MRNET.COM MB$DDSNET.COM MB$INIT.COM MB$MAILER.COM MB$ADDREP.COM MB$CHECKDEV.COM MB$ERRORS.DAT MB$VERSION.DAT MB$STOP.DAT MB$TS_ER.COM MB$DDS_ER.COM MB$NET_ER.COM MB$A1_ER.COM MB$MBMANAGER.COM MB$MRMANAGER.COM MB$MBWATCH.COM MB$A1_ERRORS.DAT A-7 The files supplied in installation saveset G are: MB$CONFIG.COM MB$CONFIG.FDL MB$$TS_CONFIG.COM MB$$MS_CONFIG.COM MB$$DDS_CONFIG.COM MB$$ER_CONFIG.COM MB$$A1_CONFIG.COM MB$MR$CONFIG$CUSTOMIZED.DAT MB$A1$CONFIG$CUSTOMIZED.DAT MB$MR$CONFIG$DEFAULT.DAT MB$A1$CONFIG$DEFAULT.DAT DDS_PERM_DB.DAT DDS_PERM_AIF.DAT DDS_CACHE_DB.DAT DDS_CACHE_AIF.DAT DDS_OUTQUE.DAT DDS_NETQUE.DAT DDS_INQUE.DAT DDS_NIF.DAT DDS_CONFIG.DAT MB$CNFDB_IVP.DAT MRINIT_0.DAT MB$CVP.DAT MB$CNFTXN.FDL A-8 Appendix B Sample Installation Procedure Running VMS Version 4.6, 4.7 Or MicroVMS This appendix gives an example of the log of an installation of Message Router on MicroVMS. The installations of Message Router on VMS Versions 4.6 and 4.7 are very similar. For a sample installation of Message Router on VMS Version 5.0, see Appendix C. Welcome to MicroVMS 4.6 Username: system Password: Welcome to MicroVMS 4.6 Last interactive login on Thursday, 08-MAR-1988 18:25 Last non-interactive login on Monday, 07-MAR-1988 09:44 $ @sys$update:vmsinstal mr031 mta0: VAX/VMS Software Product Installation Procedure V4.6 It is 08-MAR-1988 at 18:30. Enter a question mark (?) at any time for help. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on MTA0:. * Are you ready? Y %MOUNT-I-MOUNTED, MR mounted on _MTA0: (ORANGE) The following products will be processed: MR V3.1 Beginning installation of MR V3.1 at 18:32 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. * Do you want help text printed before every question [NO]? * Do you want to purge files replaced by this installation [YES]? B-1 * Do you want to run the IVP after the installation [YES]? * Do you want to keep data from a previous installation of MR V2.* [NO]? * What device is to be used for the MBMANAGER account [USER6:]: You will now be prompted for the password for the Message Router accounts, and then for a confirmation of the password. * What is the password for the Message Router accounts: * Confirm the password for the Message Router accounts: You have answered all the questions for the Message Router installation. Message Router is now being installed. The installation will take approximately 60 minutes depending on system configuration and media type. %MR-I-MODACC, Modifying the MBMANAGER account %MR-I-MODACC, Modifying the MBWATCH account %MR-I-MODACC, Modifying the MRNET account %MR-I-MODACC, Modifying the MRMANAGER account %MR-I-MODACC, Modifying the DDSNET account %MR-I-IGNERR, Ignore the following reports which may occur on NCP object definition: Ignore> %NCP-I-NMLRSP, listener response - Unrecognised component, Object Ignore> %NCP-E-UNRCMP, listener response - Unrecognised component, Object %NCP-I-NMLRSP, listener response - Success Object = MRLISTEN %NML-I-RECDELET, Database entry deleted %NCP-I-NMLRSP, listener response - Success Object = DDSLSTN %NML-I-RECDELET, Database entry deleted %MR-I-CHECDIRS, Checking directories %MR-I-DEVICE, Checking Message Router device USER6: %MR-I-CHECQUOT, Checking quota use on USER6: %VMSINSTAL-I-RESTORE, Restoring product saveset B... %MR-I-LNKDDS, Linking the DDS images %MR-I-LNKDDSMSG, ...Linking the DDS Message file %MR-I-LNKDDSSHAR, ...Linking the DDS shareable image %MR-I-LNKDDSSERV, ...Linking the DDS Server %MR-I-LNKDDSLSTN, ...Linking the DDS Listener B-2 %MR-I-LNKDDSEXTP, ...Linking the DDS external processors %MR-I-LNKDDSTMPUPD, ...Linking the DDS V3.0/V3.1 Template Update Utility %MR-I-SETDDSFILES, Setting DDS file ownership and protection %MR-I-ASGNDDSFILES, Assigning DDS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset C... %MR-I-LNKMR, Linking the TS images %MR-I-LNKMRMSG, ...Linking the TS Message file %MR-I-LNKMRTALK, ...Linking the TS Talker %MR-I-LNKMRLSTN, ...Linking the TS Listener %MR-I-LNKMRMAN, ...Linking the TS Manager %MR-I-LNKMRLOG, ...Linking the TS Logger %MR-I-LNKMRSHAR, ...Linking the TS Shareable image %MR-I-LNKMRNBS, ...Linking the TS NBS Dump utility %MR-I-LNKMRSTATS, ...Linking the TS Statistics utility %MR-I-SETMRFILES, Setting TS file ownership and protection %MR-I-ASGNMRFILES, Assigning TS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %VMSINSTAL-I-RESTORE, Restoring product saveset F... %VMSINSTAL-I-RESTORE, Restoring product saveset G... %MR-I-LNKMBMAN, Linking the MR Management images %MR-I-LNKMBUTIL, ...Linking the MB Utility %MR-I-LNKMBMAN, ...Linking the MB Manager %MR-I-LNKMBMSG, ...Linking the MB Message File %MR-I-CREMRDIR, Creating directory SYS$SYSROOT:[SYSTEST.MB] %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.MB] %MR-I-SETMBFILES, Setting MR Management file ownership and protection %MR-I-ASGNMBFILES, Assigning MR Management files to target directories The generation phase of the Message Router installation is now complete. In order to tailor Message Router to your requirements, you must use the configuration procedure, SYS$MANAGER:MB$CONFIG.COM. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... IVP for Message Router Version V3.1 This is the installation verification procedure (IVP) for Message Router. It checks that the components of Message Router are installed successfully on your system. Starting Management Service B-3 ------------------------------------------------------------------ TRANSFER SERVICE V3.1 IVP This is the installation verification procedure (IVP) for the Transfer Service. It tests whether or not the Transfer Service is successfully installed on your system. The procedure starts by checking that all the files for the Transfer Service exist and are the correct size. It then starts DECnet and MRMAN if necessary. The verification procedure creates a test mailbox, using the MRMAN utility, and sends a test message to the mailbox. The verification procedure fetches the test message from the mailbox and displays it, and then shuts down DECnet and MRMAN. The IVP has not completed successfully until you have received this test message. ------------------------------------------------------------------ Transfer Service V3.1 file check The total number of files is 27. All files exist and are the correct size. End of Transfer Service V3.1 file check. ------------------------------------------------------------------ This is MRMAN Starting Transfer Service This is MRMAN %Added MB$TSIVP, This is MRMAN %Using mailbox MB$TSIVP at node ORANGE % Message from: MB$TSIVP % Subject: TEST ************************************************** Output of this test message indicates that the Transfer Service V3.1 is B-4 installed successfully on your system. ************************************************** %Finished reading from mailbox MB$TSIVP %Directory entry MB$TSIVP deleted Shutting down the Transfer Service The Transfer Service V3.1 IVP was successful END OF TS V3.1 IVP ================================================================== DIRECTORY SERVICE V3.1 IVP This is the installation verification procedure (IVP) for the Directory Service. It tests whether or not the Directory Service is successfully installed on your system. The procedure completes the following steps: 1. Checks that the Directory Service files exist and that they are the correct size 2. Retrieves preset entries from the database ------------------------------------------------------------------ Directory Service V3.1 file check The total number of files is 8. All files exist and are the correct size. End of Directory Service V3.1 file check. ------------------------------------------------------------------ Starting the Directory Service The Directory Service V3.1 IVP was successful END OF DDS V3.1 IVP Shutting down Directory Service B-5 ================================================================== MANAGEMENT SERVICE V3.1 IVP This is the installation verification procedure (IVP) for Management Service. It tests whether or not the Management Service is successfully installed on your system. The procedure checks that the Management Services files exist and that they are the correct size. ------------------------------------------------------------------ Management Service V3.1 file check The total number of files is 73. All files exist and are the correct size. End of Management Service V3.1 file check. ------------------------------------------------------------------ The Management Service V3.1 IVP was successful END OF MS V3.1 IVP ================================================================== Installation verification was successfully performed for all 3 components of Message Router Shutting down Management Service The Message Router V3.1 IVP completed successfully Installation of MR V3.1 completed at 19:26 VMSINSTAL procedure done at 19:34 B-6 Appendix C Sample Installation Procedure Running VMS Version 5.0 This appendix gives an example of a log of an installation of Message Router on VMS Version 5.0. If you are not running VMS Version 5.0, see the sample installation in Appendix B. Welcome to VAX/VMS V5.0 Username: SYSTEM Password: Welcome to VAX/VMS version V5.0 on node ORANGE Last interactive login on Friday, 12-JULY-1988 09:00 Last non-interactive login on Thursday, 19-MAY-1988 20:01 $ @sys$update:vmsinstal mr031 mta0: options n VAX/VMS Software Product Installation Procedure V5.0 It is 12-JULY-1988 at 11:46. Enter a question mark (?) at any time for help. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on MTA0: * Are you ready? YES %MOUNT-I-MOUNTED, MR mounted on _MTA0: (HSC1) The following products will be processed: MR V3.1 Beginning installation of MR V3.1 at 11:47 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... C-1 Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: 4 * Do you want to continue the installation? y %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. Product: MESSAGE-ROUTER Producer: DEC Version: 3.1 Release Date: 1-MAR-1988 * Does this product have an authorization key registered and loaded? YES * Do you want help text printed before every question [NO]? * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? * Do you want to keep data from a previous installation of MR V2.* [NO]? * What device is to be used for the MBMANAGER account: dua0: * What is the UIC for the MBMANAGER account: 352,1 You will now be prompted for the password for the Message Router accounts, and then for a confirmation of the password. * What is the password for the Message Router accounts: * Confirm the password for the Message Router accounts: You have answered all the questions for the Message Router installation. Message Router is now being installed. The installation will take approximately 60 minutes depending on system configuration and media type. %MR-I-CREACC, Creating the MBMANAGER account %MR-I-CREACC, Creating the MBWATCH account %MR-I-CREACC, Creating the MRNET account %MR-I-CREACC, Creating the MRMANAGER account %MR-I-CREACC, Creatiing the DDSNET account %MR-I-IGNERR, Ignore the following reports which may occur on NCP object definition: C-2 Ignore> %NCP-I-NMLRSP, listener response - Unrecognised component, Object Ignore> %NCP-E-UNRCMP, listener response - Unrecognised component, Object %NCP-W-UNRCMP, Unrecognized component , Object %NCP-W-UNRCMP, Unrecognized component , Object %MR-I-CHECDIRS, Checking directories %MR-I-DEVICE, Checking Message Router device DUA0: %MR-I-CHECQUOT, Checking quota use on DUA0: %MR-I-CREMRDIR, Creating directory DUA0:[MB$] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MR] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MR.WRK] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MR.MSG1] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MR.MSG2] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MR.SCR] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MR.DB] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MB] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.TOOLS] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MB.MB$COM] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MB.MB$WORK] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.MB.MB$SCRATCH] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.DDS] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.DDS.WRK] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.DDS.SCR] %MR-I-CREMRDIR, Creating directory DUA0:[MB$.DDS.DB] %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %MR-I-LNKDDS, Linking the DDS images %MR-I-LNKDDSMSG, ...Linking the DDS Message file %MR-I-LNKDDSSHAR, ...Linking the DDS shareable image %MR-I-LNKDDSSERV, ...Linking the DDS Server %MR-I-LNKDDSLSTN, ...Linking the DDS Listener %MR-I-LNKDDSEXTP, ...Linking the DDS external processors %MR-I-LNKDDSTMPUPD, ...Linking the DDS V3.0/V3.1 Template Update Utility %MR-I-SETDDSFILES, Setting DDS file ownership and protection %MR-I-ASGNDDSFILES, Assigning DDS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset C ... %MR-I-LNKMR, Linking the TS images %MR-I-LNKMRMSG, ...Linking the TS Message file %MR-I-LNKMRTALK, ...Linking the TS Talker %MR-I-LNKMRLSTN, ...Linking the TS Listener %MR-I-LNKMRMAN, ...Linking the TS Manager %MR-I-LNKMRLOG, ...Linking the TS Logger %MR-I-LNKMRSHAR, ...Linking the TS Shareable image %MR-I-LNKMRNBS, ...Linking the TS NBS Dump utility %MR-I-LNKMRSTATS, ...Linking the TS Statistics utility %MR-I-SETMRFILES, Setting TS file ownership and protection %MR-I-ASGNMRFILES, Assigning TS files to target directories %VMSINSTAL-I-RESTORE, Restoring product saveset D ... %VMSINSTAL-I-RESTORE, Restoring product saveset E ... C-3 %VMSINSTAL-I-RESTORE, Restoring product saveset F ... %VMSINSTAL-I-RESTORE, Restoring product saveset G ... %MR-I-LNKMBMAN, Linking the MR Management images %MR-I-LNKMBUTIL, ...Linking the MB Utility %MR-I-LNKMBMAN, ...Linking the MB Manager %MR-I-LNKMBMSG, ...Linking the MB Message File %MR-I-CREMRDIR, Creating directory SYS$SYSROOT:[SYSTEST.MB] %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.MB]. %MR-I-SETMBFILES, Setting MR Management file ownership and protection %MR-I-ASGNMBFILES, Assigning MR Management files to target directories The generation phase of the Message Router installation is now complete. In order to tailor Message Router to your requirements, you must use the configuration procedure, SYS$MANAGER:MB$CONFIG.COM. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... IVP for Message Router Version 3.1 This is the installation verification procedure (IVP) for Message Router. It checks that the components of Message Router are installed successfully on your system. Starting Management Service ------------------------------------------------------------------ TRANSFER SERVICE 3.1 IVP This is the installation verification procedure (IVP) for the Transfer Service. It tests whether or not the Transfer Service is successfully installed on your system. The procedure starts by checking that all the files for the Transfer Service exist and are the correct size. It then starts DECnet and MRMAN if necessary. The verification procedure creates a test mailbox, using the MRMAN utility, and sends a test message to the mailbox. The verification procedure fetches the test message from the mailbox and displays it, and then shuts down DECnet and MRMAN. The IVP has not completed successfully until you have received this test message. ------------------------------------------------------------------ Transfer Service 3.1 file check The total number of files is 27. C-4 All files exist and are the correct size. End of Transfer Service 3.1 file check. ------------------------------------------------------------------ This is MRMAN V3.1 (BL8.2) Starting Transfer Service This is MRMAN V3.1 (BL8.2) %Added MB$TSIVP, This is MRMAN V3.1 (BL8.2) %Using mailbox MB$TSIVP at node ORANGE % Message from: MB$TSIVP % Subject: TEST ************************************************** Output of this test message indicates that the Transfer Service 3.1 is installed successfully on your system. ************************************************** %Finished reading from mailbox MB$TSIVP %Directory entry MB$TSIVP deleted Shutting down the Transfer Service The Transfer Service 3.1 IVP was successful END OF TS 3.1 IVP ================================================================== DIRECTORY SERVICE 3.1 IVP This is the installation verification procedure (IVP) for the Directory Service. It tests whether or not the Directory Service is successfully installed on your system. The procedure completes the following steps: 1. Checks that the Directory Service files exist and that they are the correct size 2. Retrieves preset entries from the database ------------------------------------------------------------------ Directory Service 3.1 file check The total number of files is 8. All files exist and are the correct size. End of Directory Service 3.1 file check. ------------------------------------------------------------------ Starting the Directory Service C-5 The Directory Service 3.1 IVP was successful END OF DDS 3.1 IVP Shutting down Directory Service ================================================================== MANAGEMENT SERVICE 3.1 IVP This is the installation verification procedure (IVP) for Management Service. It tests whether or not the Management Service is successfully installed on your system. The procedure checks that the Management Services files exist and that they are the correct size. ------------------------------------------------------------------ Management Service 3.1 file check The total number of files is 73. All files exist and are the correct size. End of Management Service 3.1 file check. ------------------------------------------------------------------ The Management Service 3.1 IVP was successful END OF MS 3.1 IVP ================================================================== Installation verification was successfully performed for all 3 components of Message Router Shutting down Management Service The Message Router 3.1 IVP completed successfully Installation of MR V3.1 completed at 12:42 VMSINSTAL procedure done at 12:43 C-6 INDEX Account Quotas, 2-19 starting, 3-1 Audience time, 1-3 intended, i upgrade, 2-23 VAXcluster, 2-23 Backup, 2-20, 3-3 installation verification procedure Configuration, 1-3 see IVP Message Router, 1-1 IVP, 1-3, 1-4, 3-5 passing on information, 5-2 overview, 4-1 procedure, 1-3 question, 3-5 Conventions, x running, 4-1 setting VERIFY, 4-6 DECnet restarting, 5-1 License Management Utility, 3-4 shutdown, 2-21 Licensing software version, 2-1 Message Router, 1-1 DIGITAL how to contact, 1-4 Magnetic tape, 2-1 Directory Service, 1-1 Management Service, 1-1 Distribution kit MBMAN utility, 1-1 checking, 2-1 MBMANAGER Distribution Medium password, 2-22 list of files, A-1 UIC, 2-22 Documents Message Router related to this book, vii components, 1-1 re-installation, 3-5 Errors shutting down, 2-26, 2-29 installation, 1-4 Message traffic, 2-21 reporting, 1-4 MicroVAX preparing MicroVMS, 2-3 Free blocks required, 2-2, 2-20 preparing VMS V5.0, 2-8 MicroVAX running VMS V5.0 Help, 3-1, 3-5 removing software, 5-8 Homogeneous Cluster MicroVMS post installation task, 5-6 limitation on processes, 2-7 post installation check, 5-7 Installation removing software, 5-7 time software version, 2-1 after, 5-1 MRMAN utility, 1-1 help, 3-1 Message Router, 1-1 Organization overview, 1-3 of this book, i preparing for, 2-1, 2-19 procedure, 3-4 Password re-installation, 2-23, 2-26 MBMANAGER account, 2-22 sample, B-1, C-1 Message Router accounts, 3-7 Index-1 Preparing see SPD for installation, 2-1 Software versions MicroVMS, 2-3 MicroVMS, 2-1 VAXcluster, 2-23 VMS, 2-1 VMS V5.0, 2-8 SPD, 2-1 Prerequisite software and Starting installation, 3-1 hardware, 2-1 Support Center, 1-4 Prerequisites SYSGEN parameters, 2-15 MicroVAX software, 2-2 SYSUAF.DAT, 2-24, 2-25 VAX software, 2-2 Purging, 3-5 Tailoring Utility, 2-8, 5-8 Time for installation, 1-3 Quota Transfer Service, 1-1 SYSGEN parameters, 2-15 Quotas account, 2-19 UIC, 3-7 MBMANAGER account, 2-22 Related documents, vii User authorization file, 2-24, Removing software from a MicroVMS 2-25 system, 5-7 Using this book, vii Removing software from VMS VAXcluster Version 5.0, 5-8 heterogeneous, 2-23 Reporting errors, 1-4 homogeneous, 2-23 Restarting Message Router limitations, DECnet, 5-1 2-23 Running the IVP, 4-1 preparing, 2-23 VMS Sample Installation, B-1, C-1 software version, 2-1 Shutting down VMSINSTAL, 1-3, 3-1 Message Router, 2-26, 2-29 invoking, 3-1 Software Product Description VMSTAILOR, 2-8, 5-8 Index-2 Message Router Installation Guide AA-KR16B-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