MailWorks_for_OpenVMS_______________________________ Installation Part Number: AA-ME54E-TE This guide provides the information you need to install MailWorks for OpenVMS software. Revision Update Information: This is a revised manual. Operating System and Version: OpenVMS Version 5.5-2 or higher OpenVMS AXP Version 6.1 Software Version: MailWorks for OpenVMS Version 1.3A ________________________________________________________________ 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 or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1991, 1993, 1995. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, AXP, CDA, DECdx, DEC MAILworks, DECnet, DECwindows, DEC TCP/IP Services for OpenVMS, DECTPU, Digital, EDT, MAILbus, MicroVAX, OpenVMS, PATHWORKS, TeamLinks, ULTRIX, VAX, VAX DOCUMENT, VAXmail, VAXmate, VT, WPS-PLUS, and the DIGITAL logo. The following are third-party trademarks: CEO is a registered trademark of Data General Corporation. DisplayWrite, IBM, and PROFS are registered trademarks of International Business Machines Corporation. Intel is a trademark of Intel Corporation. KEYpak is a registered trademark of Keyword Office Technologies, Ltd. Lotus and 1-2-3 are registered trademarks of Lotus Development Corporation. Macintosh and AppleTalk are registered trademarks of Apple Computer, Inc. Microsoft and MS-DOS are registered trademarks of and Windows is a trademark of Microsoft Corporation. MultiMate is a registered trademark of Borland International, Inc. MultiNet is a registered trademark of TGV, Inc. PostScript is a registered trademark of Adobe Systems, Incorporated. Samna Word II and Samna Word III are registered trademarks of Samna Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. WordPerfect is a trademark of WordPerfect Corporation. WordStar is a registered trademark of MicroPro International Corporation. This manual is also available on CD-ROM. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Preinstallation Requirements 1.1 Prerequisite and Optional Software............... 1-2 1.2 Prerequisite Hardware............................ 1-4 1.3 Product Restrictions in MailWorks Version 1.3A AXP.............................................. 1-4 1.4 OpenVMS License Management Facility.............. 1-4 1.4.1 Installing a Personal Use License for the Server......................................... 1-6 1.5 Preparing to Install MailWorks for OpenVMS for the First Time................................... 1-6 1.6 Installation Procedure Requirements.............. 1-9 1.6.1 Time .......................................... 1-9 1.6.2 Privileges .................................... 1-10 1.6.3 BYTLM and ENQLM Quotas ....................... 1-10 1.6.4 Disk Space .................................... 1-10 1.6.4.1 Calculating the Values for GBLPAGES and GBLSECTIONS................................. 1-11 1.6.4.2 Changing System Parameter Values with AUTOGEN..................................... 1-11 1.6.5 VMSINSTAL Requirements ........................ 1-12 1.6.6 Backing Up Your System Area ................... 1-12 1.7 MailWorks for OpenVMS and Message Router......... 1-13 1.7.1 Remote Message Router Information Gathering ... 1-13 1.7.2 New Installation of Remote Message Router ..... 1-15 1.7.3 Converting an Existing Installation of MailWorks...................................... 1-16 1.7.4 Creating a Message Router Mailbox ............. 1-17 1.7.5 Copying Message Router Image to Local Node .... 1-18 1.7.6 Modifying the Startup Script for Remote Message Router Configuration........................... 1-18 iii 2 Installing MailWorks 2.1 Accessing the Online Release Notes Before Installing....................................... 2-1 2.1.1 Running the Installation Verification Procedure ............................................... 2-2 2.1.2 Aborting the Installation ..................... 2-4 2.2 The Installation Procedure....................... 2-5 2.2.1 Invoking VMSINSTAL ............................ 2-5 2.2.2 Installation Questions and Choices ............ 2-6 2.2.3 Informational Messages ........................ 2-17 2.2.4 Output from the Installation Verification Procedure...................................... 2-19 2.2.5 Completing the Installation Procedure ......... 2-20 2.3 Error Recovery................................... 2-20 3 After Installing MailWorks 3.1 Editing System Startup........................... 3-1 3.2 Setting User Account Requirements................ 3-2 3.3 Renaming Files................................... 3-3 3.4 Modifying Files.................................. 3-4 3.5 Adding More Servers.............................. 3-4 3.6 Accessing Directory Service Addresses............ 3-5 3.7 Changing the System Configuration................ 3-5 3.7.1 Glossary of Terms for Configuration Information.................................... 3-5 3.8 Configuring MailWorks for OpenVMS and TS......... 3-7 3.8.1 Configuring MailWorks for OpenVMS and No TS ... 3-7 3.8.2 Configuring MailWorks for OpenVMS and Local TS............................................. 3-7 3.8.3 Configuring MailWorks for OpenVMS and Remote TS............................................. 3-8 3.9 Configuring MailWorks for OpenVMS and DDS........ 3-10 3.9.1 Configuring MailWorks for OpenVMS and No DDS .. 3-10 3.9.2 Configuring MailWorks for OpenVMS VAX and Local DDS............................................ 3-10 3.9.3 Configuring MailWorks for OpenVMS and DDS Concentrator................................... 3-11 3.9.4 Configuring MailWorks for OpenVMS and DDS Distributor.................................... 3-12 3.10 Files Required for Different Configurations...... 3-14 3.11 Setting up the TCP/IP Transport Service on OpenVMS.......................................... 3-14 iv A Sample MailWorks Installations A.1 Sample New Installation.......................... A-1 A.2 Sample Upgrade Installation...................... A-7 A.3 Sample Installation for an AXP System............ A-12 B Files, Logical Names, and Processes Installed on Your System B.1 File Names....................................... B-1 B.2 Logical Names.................................... B-7 Tables 1-1 Disk Space Requirements ....................... 1-11 3-1 User Account Quotas ........................... 3-2 B-1 Files Installed During Installation ........... B-1 B-2 System-Wide Logical Names ..................... B-7 B-3 Command Files Used During Startup ............. B-11 B-4 Processes Started During Installation ......... B-12 v _________________________________________________________________ Preface This document contains information about how to install MailWorks for OpenVMS. Associated Documentation The following documentation is also available for MailWorks, supporting the OpenVMS[TM], DECwindows[TM], Video Terminal (VT[TM]), and MS-DOS[R] clients: o MailWorks for OpenVMS System Manager's Guide o MailWorks for OpenVMS Video Terminals Use o DEC MAILworks for Video Terminals Quick Reference Card o DEC MAILworks for OpenVMS DECwindows Use o DEC MAILworks for DOS Use The following documentation may also be helpful to you: o OpenVMS Version 5.0 documentation set o Message Router Installation Guide and Message Router Configuration Guide Conventions The following conventions are used in this guide: Ctrl/x Ctrl/x indicates that you hold down the Ctrl key while you press another key, which is indicated here by x. DEC MAILworks, DEC MAILworks and MailWorks refer to the MailWorks same product. vii 1 _________________________________________________________________ Preinstallation Requirements This chapter discusses the preparations and requirements necessary for installing MailWorks for OpenVMS Version 1.3A on VAX[TM] and AXP[TM] systems. If you are installing clients that will be accessing MailWorks, see the appropriate product installation documentation. MailWorks provides online Release Notes. At the beginning of the VMSINSTAL procedure before you install MailWorks, you are asked if you want to display or print the MailWorks release notes. See Section 2.2.1 for the VMINSTAL command that includes Options N so that you are prompted for release notes. Digital[TM] recommends that you read the Release Notes before proceeding with the installation for changes to installation information. After the installation, you can find the release notes in: SYS$HELP:A1MAIL013.RELEASE_NOTES Preinstallation Requirements 1-1 1.1 Prerequisite and Optional Software This section lists the software that you must have installed on your system before you install MailWorks Version 1.3A: o OpenVMS VAX - Required Software: OpenVMS VAX Operating System, Version 5.5-2 or higher DECnet for OpenVMS VAX Version 5.5 or higher or DECnet/OSI for OpenVMS VAX Version 5.6B or higher - Optional Software: VAX Message Router Version 3.3 or higher DEC TCP/IP Services for OpenVMS VAX, Version 3.2 or higher TCP/IP MultiNet[R] Version 3.3 Revision A or higher Wollongong Pathway Runtime Version 1.1 and Wollongong Pathway Access Version 1.0 CDA[TM] Converter Library for OpenVMS Version 2.2 KEYpak[R] for OpenVMS Version 3.2 PATHWORKS for OpenVMS, Version 4.2 or higher (Needed only if using MailWorks for DOS new mail notification) o OpenVMS AXP - Required Software: OpenVMS AXP Operating System, Version 6.1 DECnet for OpenVMS AXP Version 6.1 DECnet/OSI for OpenVMS AXP Version 5.8 - Optional Software: VAX Message Router Version 3.3A (Note: Message Router runs only on a VAX system and must be accessed remotely from the AXP system.) DEC TCP/IP Services for OpenVMS AXP Version 3.2 PATHWORKS for OpenVMS, Version 4.2 or higher (Needed only if using MailWorks for DOS new mail notification) 1-2 Preinstallation Requirements The following optional components should all be installed on your system before you install MailWorks. The components must be installed on the same node on which you will be installing the server: o KEYpak KEYpak is an optional library of converters that MailWorks will automatically use if it is installed. You can install KEYpak after you install MailWorks, but if you do, you must restart all mail servers configured for your system. __________________ VAX Systems Only __________________ There is a potential problem if you have KEYpak installed and you use it to convert WordPerfect[TM] to some other format. ALL-IN-1[TM] WordPerfect may send different versions of WordPerfect (V4.n, V5.n) without distinguishing between them (because WordPerfect itself can handle either). However, the KEYpak software needs to distinguish between WordPerfect V4 or V5; it will fail if the version has not been properly identified. ______________________________________________________ o DECwindows The DECwindows component of OpenVMS must be installed before Digital Document Interchange Format (DDIF) documents can be supported by the mail system. The DECwindows component distributed with OpenVMS Version 5.5-2 or higher must be installed before installing DEC MAILworks for OpenVMS DECwindows. o TCP/IP If you wish to run the TCP/IP with the MailWorks product, you will need to install the DEC TCP/IP Services for OpenVMS software on your system. See the TCP/IP installation guide for more information. Message Router must be configured Local or Remote if you want to send messages beyond your node or beyond a VAX or AXP cluster, or if you want to send messages to any other messaging system. The messaging system may be on your own node or a VAX or an AXP cluster. If you are using Preinstallation Requirements 1-3 Local Message Router, it must be installed, configured, and started before MailWorks for OpenVMS can be installed. 1.2 Prerequisite Hardware DEC MAILworks for OpenVMS DECwindows requires a DECwindows display device to run, including the Installation Verification Procedure (IVP) associated with that portion of the installation. 1.3 Product Restrictions in MailWorks Version 1.3A AXP The following restrictions apply to MailWorks Version 1.3A OpenVMS AXP systems: o Support is provided for homogeneous VAX or homogeneous AXP clusters only. A cluster of VAX and AXP systems (mixed cluster) is not supported. o No local Message Router (TS or DDS). o No support for DECwindows. o ALL-IN-1 MAIL for Windows and ALL-IN-1 MAIL for Macintosh[R] are not supported. o Conversions to and from WPSPLUS and DX to DX and TEXT are not available on AXP systems. To use WPSPLUS and DX, you must install KEYpak or CDA. 1.4 OpenVMS License Management Facility The license registration information that you need is contained in the Product Authorization Key (PAK) that is shipped with MailWorks for OpenVMS. The PAK is a paper certificate that contains information about the license you need to run a particular piece of software. There are three licenses available: o MailWorks for OpenVMS Server This license must be registered. The MailWorks for OpenVMS Server is required before any other component can be installed (Video Terminals or DECwindows). o DEC MAILworks for OpenVMS DECwindows If you do not wish to install the DECwindows interface, you do not need to register this license. 1-4 Preinstallation Requirements o MailWorks for OpenVMS Video Terminals If you do not wish to install the Video Terminal interface, you do not need to register this license. Registering a MailWorks License It is best to register all the MailWorks licenses you need before you perform the installation. During the installation, you are asked if you have registered the license and loaded the appropriate authorization key. If you have not registered the license, you can complete the installation; however, you cannot run either the MailWorks software or its Installation Verification Procedure (IVP). Registering an OpenVMS License To register a license under OpenVMS Version 5.5-2, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key (PAK). o Issue the LICENSE REGISTER DCL command with the appropriate qualifiers that correspond to information on the PAK, as in the following example: $ LICENSE REGISTER "ALLIN1-MAIL-SERVER" - /ISSUER="DEC" - /AUTHORIZATION=xxx000000 - /PRODUCER=DEC - /UNITS=0 - /TERMINATION="31-JAN-1995" - /VERSION=1.1 - /CHECKSUM=1-AAAA-BBBB-CCCC-DDDD Note that this example is not a valid license. For complete information about using LMF, see the License Management Utility guide in the OpenVMS Version 5.0 documentation set. Preinstallation Requirements 1-5 1.4.1 Installing a Personal Use License for the Server If you are installing a personal use license for a server with a mix of OpenVMS and PC clients, make sure you register the following users for the server license: o SYSTEM o MUAS$SERVER o MUASNET If you are installing a personal use license for a server with OpenVMS clients only, make sure you register the following users for the server license: o SYSTEM o MUAS$SERVER 1.5 Preparing to Install MailWorks for OpenVMS for the First Time The following are some general considerations for the first time installation of MailWorks for OpenVMS: o Should you install Message Router? Message Router allows you to send mail to other nodes and to other mail systems such as OpenVMS Mail, ALL-IN-1 Integrated Office System, and IBM[R] systems such as PROFS[R]. If you choose to install Message Router, refer to the Message Router Installation Guide and Message Router Configuration Guide for more detailed information. However, Digital recommends that when you configure Message Router, you choose the Customized configuration and select "default answers" from the menu. This allows you to modify the configuration later, if necessary, and also allows you to override any defaults that do not pertain to your individual system. Note that if you choose not to use Message Router, you cannot send mail to users on another node (cluster), to OpenVMS Mail users, or through any other gateways to other vendors' products. If your users will be sending local mail only, such as within a bounded PC-LAN system, then you would normally choose not to install Message Router. 1-6 Preinstallation Requirements Message Router uses mailboxes as conduits to pass messages to different mail agents. If you install MailWorks and choose to use Message Router, the mailbox created is called AM. This default name may be overridden at installation time. o On which nodes of your system do you want to run the server processes? These server processes are: - MUAS$SERVER_nnn, which handles all sending and delivering of mail - A1MAIL$CONNECT, which handles PC connections from the MailWorks clients - A1MAIL$DIRECT_nnnn, which handles multiple concurrent DDS lookups - A1MAIL$PRINT, which handles printing from the MailWorks DOS client These processes always run together on the same node. It is not possible to run them on separate nodes. Some considerations are CPU size of the machines in your cluster, projected volume of mail, and number of users of each machine. If you are planning to run MailWorks with Local Message Router, then MUAS$SERVER_nnn must be running on the same node as Message Router. In a Local Area VAX Cluster (LAVC) configuration, it should be the boot node. In a cluster, more than one node may be running servers. If you need to change the configuration after the installation, you may change the configuration using the system management utility X4MANAGER, as described in the MailWorks for OpenVMS System Manager's Guide. o Which user interfaces do you want to run? Choose from the DECwindows user interface and the Video Terminal interface (command line). During installation you will be asked to select which of these interfaces you want to install. Any combination may be selected. Preinstallation Requirements 1-7 If, in the future, you want to add a component that was not installed previously, you may do so by running VMSINSTAL again and choosing the additional component or components from the menu. o Which disks on your system would be most available for use as work areas? Although the installation defaults the work areas to the device SYS$SYSDEVICE, Digital recommends that you spread out the input and output intensive work among other user disks. All the MUAS servers use a common work area for tools, data, and work files that are common to all servers. You will be prompted for a disk on which to put the MUAS common area. All the clients require a single work or library area of about 3,500 blocks in which to store miscellaneous files. You will be prompted for a disk on which to put the MailWorks library. Each MUAS$SERVER_nnn may use a different disk for a work area. For each MUAS$SERVER_nnn, you will be prompted for which disk to use. o Which UIC should you use for the MUAS$SERVER account? This account will be automatically created by the installation procedure as it will be a captive account. The GROUP number should, preferably, be unique but should not match any user account. The GROUP number must be greater than the SYSGEN parameter MAXSYSGROUP (in other words, not a SYSTEM account). The UIC must be unique or the installation will fail. The installation procedure will prompt you for the UIC during installation. To check the value of MAXSYSGROUP, enter the following command at the DCL prompt to invoke the SYSGEN utility: SYSGEN> SHOW MAXSYSGROUP SYSGEN> EXIT 1-8 Preinstallation Requirements The installation procedure automatically creates a second account, MUASNET. The MUASNET account has the same GROUP number as MUAS$SERVER, but a different USER number. The account UIC must also be unique. The MUASNET account is used for communication with the A1M$DIRECT_nnnn processes. The MUASNET account has NETMBX and TMPMBX privileges and can be used only for network access. o When should you add a DECwindows local language variant? If you are upgrading MailWorks Version 1.2, and you want to add a DECwindows local language variant, you should do so before installing MailWorks Version 1.3A. __________________ VAX Systems Only __________________ If you install a Local Language Variant (LLV) of DEC MAILworks for OpenVMS DECwindows VAX after you install DEC MAILworks for OpenVMS DECwindows VAX V1.3A, then you must reinstall the English language version of DEC MAILworks for OpenVMS DECwindows VAX V1.3A. ______________________________________________________ 1.6 Installation Procedure Requirements The following sections discuss various other requirements for installing MailWorks. 1.6.1 Time The installation will take approximately 50 minutes on a MicroVAX[TM] II. This time may differ, depending on your type of media and your system configuration. Of this time, only 5 minutes are required to answer all the questions for a new installation; the rest is used for creating files and setting up the configuration. The installation will take approximately 15 minutes on an AXP system. Preinstallation Requirements 1-9 1.6.2 Privileges To install MailWorks for OpenVMS Version 1.3A, you must log in to an account that has at least the following privileges authorized: o WORLD o CMKRNL o SYSPRV o SYSNAM o OPER Note that generally VMSINSTAL turns off the BYPASS privilege at the start of the installation. For an upgrade installation, if the files in the A1MAIL$LIBRARY area are not owned by MUAS$SERVER, then the BYPASS privilege will be set to modify the ownership of the files in the A1MAIL$LIBRARY area. 1.6.3 BYTLM and ENQLM Quotas The end user BYTLM should be set to a minimum of 20,000 blocks on the system. BYTLM should be set to 60,000 for users connecting from TeamLinks[TM] clients using an asynchronous connection. Refer to the TeamLinks client documentation for more details on setting this quota. The end user ENQLM quota should be set to a minimum of 100. 1.6.4 Disk Space Installing the full MailWorks for OpenVMS Version 1.3A kit requires 22,000 blocks of free storage disk space during the installation. Once MailWorks is installed, less storage space is required. Table 1-1 summarizes the storage requirements for MailWorks. Note that all block counts are approximate. 1-10 Preinstallation Requirements Table_1-1_Disk_Space_Requirements__________________________ Blocks During Blocks After Description_________Installation___Installation____________ All components 22,000+ 15,000 +Includes_installation_overhead____________________________ ___________________________________________________________ 1.6.4.1 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run MailWorks, you must set the correct values for the GBLPAGES and GBLSECTIONS system parameters. The values for GBLPAGES and GBLSECTIONS are as follows: you must have at least 7,550 unused pages and 75 unused sections available on your system for the installation to process successfully. __________________ AXP Systems Only __________________ If you are installing MailWorks on an AXP system, you must have 121,000 pagelets (not pages). There are 16 pagelets to a page. ______________________________________________________ To calculate how many unused global pages and global sections your system has, perform the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") If either of these values are less than the recommended value, increase that value. 1.6.4.2 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the ones that you reset manually. To change system parameters with AUTOGEN, you must edit the following file: SYS$SYSTEM:MODPARAMS.DAT Preinstallation Requirements 1-11 For example, to increment the global pages SYSGEN parameter, use the following: ADD_GBLPAGES = 2000 Now, run the AUTOGEN procedure to recalculate the system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT AUTOGEN performs an automatic system shutdown and reboots when it has finished. Reboot your system to make the new parameter values effective. Also on OpenVMS systems, you may want to add the [NO]FEEDBACK parameter to the AUTOGEN command line. For more information about using AUTOGEN, see the instructions on modifying system parameters in the OpenVMS documentation on System Management and Operations. 1.6.5 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you of the problem and asks if you want to continue the installation. In some cases, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press Return. Correct the problem and restart the installation. 1.6.6 Backing Up Your System Area At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software on top of the operating system. It is also important that you back up the MUAS and A1MAIL$LIBRARY common areas. You should also consider backing up every area where a server is configured. Use the backup procedures that have been established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS documentation set. 1-12 Preinstallation Requirements 1.7 MailWorks for OpenVMS and Message Router Prior to the Version 1.3A release, the configuration required to access DDS consisted of MailWorks for OpenVMS and Message Router with the DDS component installed on the MailWorks Target Node. This required that DDS be managed on every system that was running a MailWorks Server, resulting in many DDS nodes. In a large network with many DDS nodes, updating DDS becomes time consuming, resource intensive, and difficult to manage. This release lifts the restriction that DDS be installed and configured on the MailWorks Target Node. Depending on the system and the configuration you have, there are three possible MailWorks for OpenVMS and Transfer Service (TS) configurations, and four possible MailWorks for OpenVMS and DDS configurations. All of these except the DDS Concentrator and the DDS Distributor are identical to Version 1.2 configurations. o MailWorks for OpenVMS and No TS o MailWorks for OpenVMS and local TS o MailWorks for OpenVMS and remote TS o MailWorks for OpenVMS and no DDS o MailWorks for OpenVMS and local DDS o MailWorks for OpenVMS and DDS Concentrator o MailWorks for OpenVMS and DDS Distributor These configurations are described in Chapter 3, After Installing MailWorks. Also, see the MailWorks for OpenVMS System Manager's Guide for general information about the different configurations. 1.7.1 Remote Message Router Information Gathering In this section, the following terms are used: LOCAL The local cluster running MailWorks. REMOTE The remote cluster where the Message Router is running. Preinstallation Requirements 1-13 AM_LOCAL The Message Router Mailbox (mbx) for the LOCAL MailWorks server. This mailbox is located on cluster REMOTE. ________________________ Note ________________________ Digital recommends that you create the Message Router Mailbox (mbx) on the cluster sorter node of the REMOTE cluster. ______________________________________________________ You will need to gather specific information about Remote Message Router if you are planning to use MailWorks with a Remote Message Router configuration. You need this information before you start - it does not matter if this is a new installation or if you are converting an existing version of MailWorks to a Remote Message Router configuration. 1. Determine what the mailbox name will be. In the example in the installation, the mailbox name is AM_LOCAL. See the MailWorks for OpenVMS System Manager's Guide for more details about MR_MAILBOX_NAME. 2. Determine the node or cluster name where Remote Message Router is located. In the example in the installation, the node name is REMOTE. See the MailWorks for OpenVMS System Manager's Guide for more details about MR_NODE. 3. Determine what the Remote Message Router password will be. This password is set in X4MANAGER for node LOCAL and in MRMAN for node REMOTE. See MailWorks for OpenVMS System Manager's Guide for more details about MR_PASSWORD. 4. Determine what your local routing address will be. Do you use an area route or not? In the installation example, the local routing address would look like: AM_ LOCAL@REMOTE. See MailWorks for OpenVMS System Manager's Guide for more details about LOCAL_ROUTING_ADDRESS. 1-14 Preinstallation Requirements __________________ AXP Systems Only __________________ Version 1.3A does not support local Message Router TS or DDS on AXP systems. ______________________________________________________ 5. Determine what the time offset is. See MailWorks for OpenVMS System Manager's Guide for more details about TIME_OFFSET. 1.7.2 New Installation of Remote Message Router After you have completed information gathering, do the following: 1. Invoke the VMSINSTAL utility to install the product. During the installation procedure, the following prompts will be displayed. These prompts are related to Remote Message Router configuration. Answer these prompts according to the information gathered. Refer to the installation log in Appendix A to see where these prompts are displayed: * Configure Message Router Transfer Service option [1]: * Message Router mailbox name [AM_NODEA]: * Node where Remote Message Router is located [ ]: * Remote Message Router Password: * Local routing address [AM_NODEA@NODEB]: * Time offset [-0500]: 2. Create the Message Router Mailbox on the remote node. Section 1.7.4 for information on creating the mailbox. 3. Make sure SYS$STARTUP:A1MAIL$STARTUP.COM has been run on all nodes and satellites in the local cluster. 4. Invoke a client on the node where MailWorks was installed and send mail through Message Router. If there any problems, see MailWorks for OpenVMS System Manager's Guide for information on how to perform troubleshooting on Message Router. Preinstallation Requirements 1-15 1.7.3 Converting an Existing Installation of MailWorks To convert an existing installation to use Message Router, do the following: 1. Stop all MailWorks servers on all nodes. Execute the following sequence of commands on each node that has a MailWorks server configured. $ X4MANAGER X4MAN.MAIL> MANAGE REMOTE_SERVER X4MAN.REMOTE> STOP CONNECT X4MAN.REMOTE> STOP PRINT X4MAN.REMOTE> MANAGE MAIL_SERVER X4MAN.MAIL> STOP 2. Edit the startup script to modify the attributes to use the information you have gathered. a. Modify the common startup script: $ X4MAN X4MAN.MAIL> EDIT This invokes the editor with the common server startup script. See Section 1.7.6 for details on which attribute to add and modify in the file. When the file has been modified, exit the editor. b. For each server that uses a server specific startup script, execute the following sequence of commands to modify the server specific startup script for a Remote Message Router configuration: $ X4MAN X4MAN.MAIL> EDIT/SPECIFIC This invokes the editor with the server specific startup script. See Section 1.7.6 for details on which attributes to add or modify in the file. When the file has been modified, exit the editor. 3. Invoke the startup procedure on all the nodes that use MailWorks in the system. You must set the profile with privileges required to execute the startup. This will restart the servers with the Remote Message Router configuration on the server nodes and will define the appropriate logical names, such as the local routing 1-16 Preinstallation Requirements address, that are used by the clients on the client nodes. To do this, use the SYSMAN utility in the following manner: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SET PROFILE/PRIV=ALL SYSMAN> DO @SYS$STARTUP:A1MAIL$STARTUP SYSMAN> EXIT $ 4. See Section 1.7.4 for details about how to create a Message Router Mailbox. 5. See Section 1.7.5 for details about how to copy the correct image onto the local node. 6. Make sure SYS$STARTUP:A1MAIL$STARTUP.COM has been run on all nodes and satellites in the cluster. 7. Invoke a client on the node where MailWorks was installed and send mail through Message Router. If there are any problems, see MailWorks for OpenVMS System Manager's Guide for troubleshooting information. 1.7.4 Creating a Message Router Mailbox Follow these steps to create a Message Router Mailbox on the node running Message Router: 1. Log into the cluster sorter node of the remote cluster. In the installation example, the node is REMOTE. 2. Make sure you have enough privileges to invoke and use MRMAN. For more details on this utility refer to the Message Router System Management documentation. 3. Invoke the Message Router system management utility. $ MCR MRMAN 4. Create the mailbox. The name of the mailbox must be the same name that was entered during the installation procedure (or modified in the startup command procedure, MR_MAILBOX_NAME). The password must be the same name that was entered during the installation procedure (modified in the startup command procedure, or modified using the X4MANAGER SET MR_PASSWORD command). Preinstallation Requirements 1-17 $ MCR MRMAN MRM> ADD /SUPPRESS_DELIVERY_REPORTS - _MRM> /PROBES_RELAYED /COMPLETE_MESSAGES _MRM> /IGNORE_SENDER /SERVICE_MESSAGES _MRM> /PASSWORD= MRMAN> 1.7.5 Copying Message Router Image to Local Node If you are installing MailWorks on a VAX system, the Message Router Version 3.3 image must exist on the node where MailWorks is installed. If it does not, copy SYS$LIBRARY:MRAPPSHAR.EXE from the node where Message Router is installed to SYS$COMMON:[SYSLIB] on the node where MailWorks is installed. Do not copy the image to SYS$SPECIFIC:[SYSLIB]. This will cause problems. This image does not need to be installed. If you are installing MailWorks on an AXP system, the appropriate file will be provided during the MailWorks installation. 1.7.6 Modifying the Startup Script for Remote Message Router Configuration The following attributes need to be properly set in the startup script so that the Remote Message Router configuration works properly: SET MR_MAILBOX_NAME AM_LOCAL SET MR_NODE REMOTE SET MR_PASSWORD SET LOCAL_ROUTING_ADDR AM_LOCAL@REMOTE SET TIME_OFFSET "" SET USE_MR SET MR_POLL_INTERVAL 150 1-18 Preinstallation Requirements 2 _________________________________________________________________ Installing MailWorks This chapter describes how to install MailWorks for OpenVMS on a VAX and an AXP system. It also includes information about how to access Release Notes, how to run the Installation Verification Procedure (IVP), and how to abort the installation. Appendix B lists the files, logical names, and processes that are installed on your system as a result of this installation. __________________ AXP Systems Only __________________ MailWorks for OpenVMS Version 1.3A supports a homogeneous VAX or homogeneous AXP cluster only. A mixed VAX and AXP cluster is not supported. ______________________________________________________ 2.1 Accessing the Online Release Notes Before Installing MailWorks for OpenVMS provides online Release Notes. If you specify OPTIONS N when you invoke VMSINSTAL, the installation procedure asks if you want to display or print the Release Notes. This question is asked after the media is mounted and before the rest of the installation proceeds. You should review the Release Notes for information about changes in the installation procedure. If you specified OPTIONS N when you invoked VMSINSTAL, you are given four options for reviewing the Release Notes: Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: Installing MailWorks 2-1 1. Display Release Notes 2. Print Release Notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the Release Notes immediately on the console terminal. You can press Ctrl/C to terminate the display at any time. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can enter a queue name or press Return to send the file to the default output print device. If you select option 3, VMSINSTAL displays the Release Notes immediately on the console terminal and then prompts you for a queue name for the printed version. Because the Release Notes for MailWorks for OpenVMS Version 1.3A may be large, Digital recommends that you choose option 2. The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press Return. In either case, the software copies the Release Notes to a file in the SYS$HELP directory, unless you chose option 4. For example: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-REMOVED, The products Release Notes have been successfully moved to SYS$HELP. The Release Notes are located in the following file: SYS$HELP:A1MAIL013.RELEASE_NOTES 2.1.1 Running the Installation Verification Procedure The Installation Verification Procedure (IVP) for MailWorks verifies the installation. During the installation, you are asked if you want to run the IVP as part of the installation. If you respond YES, VMSINSTAL runs the IVP. Digital recommends that you run the IVP to be sure that MailWorks is installed correctly. 2-2 Installing MailWorks After you install MailWorks, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access MailWorks: $ @SYS$TEST:A1MAIL$VMS_IVP The IVP prompts you for the International Standards Organization (ISO) code for the language to be used for the IVP. By default, the ISO code for the language that is configured for MailWorks is used. A list of valid ISO codes can be found in the file A1MAIL$LIBRARY:A1MAIL$LANGUAGES.DAT. The following is displayed: Please provide the iso code of the language you want to test with the IVP procedure. Enter the Iso code [EN] : The IVP includes several tests, depending on which components have been installed. The following describes the tests: o MailWorks for OpenVMS Server This is completely automatic and does not require interaction with the user. This test is always run as part of the IVP. o Command line interface This test is automatic and does not require user interaction. This test is optional. o DECwindows user interface This test is optional and requires user interaction. IVP information is displayed on the user's terminal and is also available as part of the IVP procedure. This IVP will invoke MailWorks and instructions will be displayed on how to run the IVP. Do the following: 1. Click on the CREATE button. 2. From the CREATE window and the FILE pulldown menu, select INCLUDE .... 3. Include the file A1MAIL$TEST:A1MAIL$DWVMS_IVP.TXT and follow the instructions in that file. Installing MailWorks 2-3 At this point, the DECwindows client will be invoked. The A1MAIL$DWVMS_IVP.TXT file contains the instructions to run the MailWorks for OpenVMS DECwindows IVP. This is an interactive IVP. You should read all the instructions in this file before you start the procedure. If you are a novice DECwindows users, note that if a box appears that requires an acknowledgment, you must click on that button before anything else can continue in that area. The automated section of this IVP will now run. 2.1.2 Aborting the Installation To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files that it has created up to that point and exits. You can then start the installation again. If you stop a new installation before it has successfully completed, do the following before attempting another installation: 1. If the MUAS$SERVER and MUASNET accounts are created, remove the entries from AUTHORIZE and delete the directory [MUAS$SERVER]. 2. If work directories were created for the MUAS servers, delete the MUAS server work directories. 3. If the A1MAIL$LIBRARY directory was created, delete the directory. 4. If the MUAS$PROFILE_UPDATE rights identifier was created, delete this rights identifier. 5. If any files were moved to the following areas: SYS$SYSTEM, SYS$MESSAGE, SYS$SHARE, SYS$TEST, SYS$MANAGER, SYS$STARTUP, SYS$HELP, delete them. Look for files beginning with: A1M, X400, MUAS, and CTI. 2-4 Installing MailWorks 2.2 The Installation Procedure The MailWorks for OpenVMS installation procedure consists of a series of questions and informational messages. The questions will vary depending on what components you are installing and whether you are installing software on a VAX or AXP system. 2.2.1 Invoking VMSINSTAL To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. Use the following syntax to invoke VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL A1MAIL device-name OPTIONS N A1MAIL The installation name for the component. This has the syntax: ProductnameVersion Where "Version" is optional. device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed when the installation is completed. OPTIONS N An optional parameter that indicates you want to be prompted to display or print the Release Notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not prompt you to display or print the Release Notes. Digital recommends that you read the Release Notes before proceeding with this installation. VMSINSTAL has several other options; for information, see the OpenVMS documentation on Software Installation. The following example displays the command to invoke VMSINSTAL to install MailWorks for OpenVMS from tape drive MTA0: and illustrates the system responses. This example uses the OPTIONS N parameter for printing or displaying Release Notes: Installing MailWorks 2-5 $ @SYS$UPDATE:VMSINSTAL A1MAIL013 MUA0: OPTIONS N OpenVMS VAX Software Product Installation Procedure V5.5-2 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. VMSINSTAL does not prompt you for any options. Be sure to include OPTIONS N on the VMSINSTAL command line to access the Release Notes during the installation. 2.2.2 Installation Questions and Choices This section discusses the questions and choices presented to you during the installation. See Appendix A for sample installation procedures. Each question you must answer or choice you must make in the installation is marked with an asterisk (*) at the beginning of the line. Most questions show the default response in brackets, for example [YES]. If you want to enter the default response, press Return. In some cases, default values are automatically assigned to certain system characteristics by MailWorks. If you need to override these values, use the X4MANAGER utility as described in MailWorks for OpenVMS System Manager's Guide. System backup VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. You should also back up common areas: MUAS and A1MAIL$LIBRARY. In addition, as an extra precaution, you should back up common areas on each server you configured. If you are satisfied with the backup of your system disk, press Return. Otherwise, enter NO to discontinue the installation. After you complete backup procedures, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 2-6 Installing MailWorks Choosing to purge files You have the option to purge files from previous versions of MailWorks for OpenVMS that are superseded by this installation. * Do you want to purge files replaced by this installation [YES]? Choosing to run the Installation Verification Procedure The installation procedure now asks if you want to run the Installation Verification Procedure. The IVP for MailWorks for OpenVMS checks to be sure that the installation is successful. * Do you want to run the IVP after the installation [YES]? Selecting the components from this kit to be installed This installation allows you to choose several different components of the MailWorks product set. These choices include: o MailWorks server for OpenVMS This is the backbone of the mail system and must be either previously installed on the system or installed as part of this installation. The server also contains the OpenVMS files required to support MailWorks for PC clients. This component must be installed before the PC clients can work. An OpenVMS license is required to run the server. o DEC MAILworks for OpenVMS DECwindows __________________ AXP Systems Only __________________ Version 1.3A does not support DEC MAILworks for OpenVMS DECwindows on AXP systems. ______________________________________________________ This is the component that provides a DECwindows user interface to the mail functionality. This option requires that the DECwindows product distributed with OpenVMS Version 5.5-2 or higher be installed before DEC MAILworks for OpenVMS DECwindows is installed. Installing MailWorks 2-7 An OpenVMS license is required to run the DECwindows component. ___________________ VAX System Only ___________________ If you are upgrading from MailWorks Version 1.2 and you want to add a DECwindows local language variant, you should do so before installing MailWorks Version 1.3A. If you installed the MailWorks Version 1.3A software and want to add a local language variant at a later time, follow these steps: 1. Install the DECwindows local language variant. 2. Install the English language version of the DECwindows client. ______________________________________________________ o MailWorks for OpenVMS Video Terminals This is the component that provides a command line interface to the mail functionality. An OpenVMS license is required to run the command line component. The following illustrates the procedure for selecting the components to install. The following menu lists all the choices available through this installation. The server must have been installed on the system previously, or you must choose it now. Enter the components that you wish to install. Use a comma-separated list (i.e., "1,2"). The installation guide has more details on these various components. 1) MailWorks Server for OpenVMS 2) DEC MAILworks for OpenVMS DECwindows 3) MailWorks for OpenVMS Video Terminals 4) All of the above CAUTION: If this is an upgrade from a previous version, the clients must be upgraded also. * Choose installation options [4]: 4 2-8 Installing MailWorks The following questions are specific to the MailWorks server installation portion. Installing MailWorks 2-9 ________________________ Note ________________________ If this is the first time you install MailWorks for OpenVMS Version 1.3A, you will see the following sequence of questions. However, if MailWorks has been previously installed, none of these questions are asked. The installation procedure immediately checks to ensure that the proper licenses are registered. ______________________________________________________ MailWorks library disk MailWorks creates a common directory to keep miscellaneous files. This common work directory contains common files, such as the template files and registered editor files. It also contains multiple language subdirectories that contain language-specific files. For example, the English subdirectory contains all of the English template files. Please enter the name of a disk that can be used; the default given is SYS$SYSDEVICE: * MailWorks Library disk [SYS$SYSDEVICE]: License registration for server The installation procedure asks if you have registered and loaded your authorization key for the MailWorks server and displays information specific to the particular license, for example: Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 1.1 Release Date: 19-Apr-1991 The installation procedures asks: * Does this product have an authorization key registered and loaded? [YES]? MUAS common disk This is the disk where the server-common files are stored. There will be a great deal of activity to this disk because this is where the profile database is kept. * MUAS common disk [SYS$SYSDEVICE]: 2-10 Installing MailWorks Server User Identification Code (UIC) You are asked to enter a UIC for the MUAS$SERVER to use. The following is displayed: To ensure that the MailWorks server runs in the proper environment, this installation procedure will create an account for the server. This account, MUAS$SERVER, has no special privileges and it is not possible to log into this account. You must specify a unique UIC that is not a system UIC for this account to ensure proper security of the network. The password for this account will be generated. You do not need to know this password. It has been set as PRE-EXPIRED. If this scenario violates your security policies, you may change it after the installation has finished via the VMS AUTHORIZE utility. * UIC to be used for MUAS$SERVER account in format [ggg,mmm]: User Number The MailWorks server creates a second account (if it does not already exist) in the same group as the MUAS$SERVER account. Enter a unique user number for this account. * User number to be used for MUASNET account in format: mmm: Use of Message Router-VAX Systems Only This next question asks if you wish to configure MailWorks so that it can use Message Router: The following menu lists all the choices available through this installation. Enter the option that you wish to configure. Only a single value is allowed, (i.e., "1"). The installation guide describes these options. 1)Configure to use Local Message Router Transfer Service 2)Do not configure to use Message Router Transfer Service 3)Configure to use Remote Message Router Transfer Service * Configure Message Router Transfer Service option [2]: o Choosing option 1 allows you to send mail to other mail systems on other networks. For example, you can send mail to OpenVMS Mail and to the ALL-IN-1 Integrated Office System. Installing MailWorks 2-11 o Choosing option 2 allows you to send mail only locally. o Choosing option 3 allows you to send mail to other mail systems or other networks. The Message Router Transfer Service will be located on a remote node. Message Router Mailbox Name If you choose option 1 or 3 at the Use of Message Router question on a VAX system, or are installing MailWorks on an AXP system, you are asked for the name of the Message Router mailbox: * Message Router mailbox name [AM]: If you choose to use a different name for the mailbox, you must tell your users, because AM is used in all the examples within the user documentation. If you choose option 1, Configure to use Local Message Router Transfer Service, the installation checks whether this mailbox has already been created. You will see one of the following, depending on whether the mailbox already exists: This is MRMAN V3.1 %AM - No mailbox found or This is MRMAN V3. 1 AM, Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages * Mailbox exists - use it [YES]? If you choose not to use this existing mailbox, you will be prompted again for a different one. If you select option 3, Configure to use Remote Message Router Transfer Service, on a VAX system or are installing MailWorks on an AXP system, the following additional prompts are displayed: * Node where remote Message Router is located? Enter the name of the node where the Remote Message Router is located. 2-12 Installing MailWorks On an AXP system, when you select option 3 for a VAX system, Remote Message Router, you must create a mailbox on the node where MR is running. If you are installing Message Router on a VAX system, the image must exist on the node where MailWorks is installed. If it does not, copy the image to the system area. See Section 1.7.5 for information on how to copy this image. Remote Message Router password If you are using the Remote Message Router Transfer Service, you must create a password to the node where the Remote Message Router is located. The following is displayed: * Node where Remote Message Router is located : NODEB The password must match the one that is set in the X4MANAGER utility. The password must be between 8 and 31 characters long. If the user wants to check the mailbox using: MRMAN SEND/IDENT, then the combined length of the mailbox and password should be between 8 and 24 characters long. * Remote Message Router Password : Enter the password to be used when the mailbox is created on the Remote node. Local routing address MailWorks uses the local routing address to create the return address on messages sent out and to flag a local recipient to make use of delivery optimizations. For most configurations, the local routing address is: AM@YourNode However, if this installation is on a network that supports area codes, the local routing address is: AM@YourNode@YourArea For clusters, the value of "YourNode" should be the cluster alias, if that has been enabled, otherwise, choose one of the nodes you have configured to run servers: * Local routing address [AM@node]: Installing MailWorks 2-13 Time offset A question about time offset displays if you have chosen option 1 or 3 at the Use of Message Router question on an AXP system. The time offset is the difference between local time and network standard time. Enter the time as five characters, in the form +HHMM. The first character must be + or -. HH is the hour difference, and MM is the minute difference. For example, 5 hours behind network standard time must be specified -0500. * Time offset [+0000]: Remote Message Router DDS If you will be accessing Message Router DDS on a remote system, you should answer yes to the following question: Remote Message Router Distributed Directory Services is a configurable option. An answer of YES indicates that Remote Message Router Distributed Directory Services will be configured. An answer of NO indicates that Remote Message Router Distributed Directory Services will not be configured. * Configure Remote Message Router DDS [NO]? Configuration questions You are asked questions concerning the MUAS system configuration. You are also asked if you want to configure more MUAS servers. See Section 3.5 for information on adding additional servers. You are given a default for the node for the first server. To end the set, press Ctrl/Z when asked for a node for a server. o Node for server 000 [YOURNODE]. The name of the node displays in brackets. Press Return, or type in a node on which you wish to run a server. o Disk for server 000 [SYS$SYSDEVICE]. The default SYS$SYSDEVICE displays in brackets. Either press Return, or specify a different disk. Digital recommends that you not use SYS$SYSDEVICE because of the amount of disk I/O required to this disk. 2-14 Installing MailWorks o Configure more MUAS servers [YES]? Either a YES or NO displays in brackets. If you wish to configure more MUAS servers, type YES and press Return. For more information about configuring servers, see MailWorks for OpenVMS System Manager's Guide. The following is displayed: There will now be a dialogue to determine the MUAS system configuration. You will be asked to specify the MUAS servers to be run on this node (and, for a cluster, other nodes). Servers are uniquely identified by a three-character name, typically composed only of numeric characters. You will be asked after each set if there are more servers to be configured. Use ^Z (CTRL-Z) to cancel an entry for a server node or server disk set. * Node for server 000 [ROBINS]: * Disk for server 000 [SYS$SYSDEVICE]: * Configure more MUAS servers [YES]? NO MailWorks system configuration is now complete. Note that if you want to alter the system configuration after installation, use the X4MANAGER utility as described in the MailWorks System Manager's Guide. Command line user interface questions As part of the installation of the command line user interface, you will be asked the following questions: o License registration The installation procedure asks if you have registered and loaded your authorization key for MailWorks for OpenVMS Video Terminals and prints out information specific to the particular license, for example: Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 1.1 Release Date 19-Apr-1991 Installing MailWorks 2-15 Specifically, the installation inquires: * Does this product have an authorization key registered and loaded? If you have not registered and loaded your authorization key, you must answer NO to this question. A successful installation of MailWorks depends upon an authorization key being registered and loaded. Please be sure that this has been completed before proceeding with the installation. o A warning if no DDIF support With some configurations of the OpenVMS operating system, support for DDIF documents may not have been installed. This support is part of the DECwindows kit, and may be only optionally installed as part of the base operating system. If the installation detects that you have not installed the images for DDIF support, you will get output warning: !! This system does not have support for DDIF !! !! viewers installed. It will not be possible !! !! to READ any messages containing DDIF. !! !! Also, others sending DDIF messages to this !! !! system may get non-delivery notifications. !! !! !! !! DDIF viewer support requires that DECwindows !! !! be installed. !! !! !! !! If you install DECwindows after this installation,!! !! then re-start MailWorks. !! Note this also disables any request made to install the DECwindows User Interface. DECwindows user interface questions As part of the DECwindows user interface installation, you will be asked the following questions: o License Registration The installation procedure asks if you have registered and loaded your authorization key for DEC MAILworks for OpenVMS DECwindows and prints out information specific to the particular license, for example: 2-16 Installing MailWorks Product: ALLIN1-MAIL-DW-CLIENT Producer: DEC Version: 1.1 Release Date: 19-Apr-1991 Specifically, the installation inquires: * Does this product have an authorization key registered and loaded? If you have not registered and loaded your authorization key, you must answer NO to this question. Although installation does not require this license, you must be licensed to run the DECwindows User Interface. o End of questions This is the end of the questions asked by the installation. You will see a notice to this effect followed by informational messages described in the following section. The installation time specified in the informational message reflects an estimate based on the components being installed. If you are installing software on a VAX system, the following is displayed: This is the end of the questions that are asked by this installation. The rest of the installation will take about 55 minutes on a MicroVAX II class machine. If you are installing software on an AXP system, the following is displayed: This is the end of the questions that are asked by this installation. The rest of the installation will take about 13 minutes on a DEC 3000 Model 300 class machine. 2.2.3 Informational Messages The installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. These messages include but are not limited to: Installing MailWorks 2-17 %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUAS$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier MUAS$SERVER value: [000057,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUAS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.COM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.DB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.TOOLS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.WRK]. %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named MUAS$PROFILE_UPDATE. %UAF-I-RDBADDMSG, identifier MUAS$PROFILE_UPDATE value: %X8001000A added to rights data base. %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUASNET. %UAF-I-ADDMSG, user record successfully added %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.DMP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.MSG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.TMP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.WRK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.TEST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.PRINT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.ENGLISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DANISH]. 2-18 Installing MailWorks %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DUTCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.FRENCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.GERMAN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.ITALIAN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.SPANISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.SWEDISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.MUAS]. +--------------------------------------------+ | Create the mailbox on the node running MR. | +--------------------------------------------+ +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM, | | AFTER the network has been started up. | | | | Note that if you are installing on a cluster, this startup procedure | | should, in general, be executed on EVERY node in the cluster. Read | | the release notes for more information. | +----------------------------------------------------------------------+ 2.2.4 Output from the Installation Verification Procedure If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see a display similar to the following (the node and user names will be different): Starting IVP for MailWorks V1.3A. Starting server test. Starting user agent test; VT interface. NOTE: This IVP will change the current user's MailWorks user profile as follows: AUTO_PURGE is set to No CORRELATE is set to Yes Setting profile attributes. Mailing message to self. Installing MailWorks 2-19 Pausing 19 seconds for message delivery. New MailWorks message on node ROBINS from SYSTEM (SYSTEM@AM@ROBINS) (28-DEC-1994 08:09:02.57) New MailWorks delivery/receipt notification on node ROBINS from POSTMASTER (@ROBINS.MUAS) (28-DEC-1994 08:09:12.53) Generating IVP output file. Checking IVP output file. You have 2 unopened MailWorks messages. MailWorks V1.3A IVP completed successfully. 2.2.5 Completing the Installation Procedure The following messages indicate the entire installation procedure is complete: Installation of A1MAIL Version 1.3A completed at hh:mm VMSINSTAL procedure done at hh:mm You can now log out of the privileged account. Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.3 Error Recovery If errors occur during the installation or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message displays: %VMSINSTAL-E-INSFAIL, The installation of MailWorks for OpenVMS Version 1.3A has failed. If the IVP fails, the following messages displays: MailWorks IVP failed. %VMSINSTAL-E-IVPFAIL, The IVP for MailWorks for OpenVMS Version 1.3A has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. 2-20 Installing MailWorks o The product is not properly licensed. o The IVP may fail if MUAS$SERVER_nnn fails to start up. Installing MailWorks 2-21 3 _________________________________________________________________ After Installing MailWorks After installing MailWorks, you may need to perform the following postinstallation procedures: o Edit the system startup to include @SYS$STARTUP:A1MAIL$STARTUP. o Set user account quotas. o Rename or modify files, if applicable. o Add additional servers. o Allow workstation users access to the Directory Service (DDS). o Change the system configuration. Files required for different configurations are listed. o Set up TCP/IP. 3.1 Editing System Startup The order in which you edit various components into the system startup is important. To ensure that MailWorks starts up correctly, you must enter the following components in this order: 1. DECnet[TM]. 2. PATHWORKS and MRGATE. Either of these can be done second or third; the order is interchangeable. 3. MailWorks. Once you modify the system startup file, you must execute SYS$STARTUP:A1MAIL$STARTUP.COM after DECnet has been started and the network is up. After Installing MailWorks 3-1 3.2 Setting User Account Requirements To use MailWorks, user accounts on your system must have certain quotas. Table 3-1 summarizes the required user account quotas. The PRCLM is required if you use the DECwindows interface with alternate editors. Table_3-1_User_Account_Quotas______________________________ Account_Quota____Value_____________________________________ FILLM 100 PRCLM 3 BYTLM 20,000 60,000 for TeamLinks ENQLM____________100_______________________________________ User account quotas are stored in the file SYSUAF.DAT. You use the Authorize Utility to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the AUTHORIZE prompt (UAF>), use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH Modifying a User Account Quota To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name /quota-name=nnnn This example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=100 UAF> EXIT After you exit from the utility, the OpenVMS system displays messages indicating whether changes were made. Once you have finished making the changes, the users must log out and log in again for the new quotas to take effect. 3-2 After Installing MailWorks For more information about modifying account quotas, see the description of the Authorize Utility in the OpenVMS documentation on System Management and Operations. 3.3 Renaming Files If your installation is an upgrade installation, MailWorks looks for the following files in the language-specific directories on your current system: o A1MADDR.DAT o A1MDIST.TXT o A1MDWRH.TXT o A1MIOSRH.TXT o A1MKEYWD.DAT o A1MREAD.TXT o A1MSHOW.TXT o A1MAIL$PROFILE_TEMPLATE_ALL-IN-1.DAT o A1MAIL$PROFILE_TEMPLATE_DEFAULT.DAT o A1MAIL$PROFILE_TEMPLATE_VMSMAIL.DAT If MailWorks finds the files with .TXT extensions in the language-specific directories on your current system, the installation process renames these files with .NEW extension. If MailWorks does not find the files with .TXT extensions in the language-specific directories, the installation process names these files from the kit to .TXT extensions. For this reason, you must rename any files with the .NEW extension to .TXT extensions only if you want to use the file version and not the version from the new installation (if any) on your existing system. If MailWorks finds files with .DAT extensions in the language-specific directories on your current system, the installation process renames the files to .OLD extensions. If MailWorks does not find the files with .DAT extensions in the language-specific directories on your current system, the installation process names the files to .DAT extensions. For this reason, you must rename any files with the .OLD extension to .DAT extensions only if you want to After Installing MailWorks 3-3 use the file versions from the new installation and not the versions (if any) on your current system. If you allow the system template files to remain the current template files, you do not need to rename any customized template files after the upgrade installation. You will need to rename a template file only if you wish to use a template file that was supplied with the installation. 3.4 Modifying Files If SYS$STARTUP:A1MAIL$STARTUP.COM exists on the system, it will be renamed to SYS$STARTUP:A1MAIL$STARTUP.OLD. Digital has supplied a new startup command procedure with Version 1.3A. If you have added any special customizations in the old startup command procedure, you must modify the new startup command procedure. If this is an upgrade, the install procedure will not overwrite the existing datatype and conversions table, MUAS$TABLE_SHARE.MAR. The new datatype and conversions table file will be named MUAS$TABLE_SHARE.NEW. 3.5 Adding More Servers During the installation, you are asked if you want to configure more MUAS servers. In previous versions, you could have only one mail server per node in a cluster. This was required to avoid a bottleneck between MailWorks and Message Router when you had a substantial amount of mail beyond your node or beyond a VAX or AXP cluster. You can now add and configure additional servers to fetch messages and deliver them. However, these additional servers do not accept connections from clients. You should consider using multiple servers only if you are experiencing throughput problems caused by the interface between MailWorks and Message Router. For example, you may have throughput problems if you have long message queues in mail servers and if you have a large proportion of off-node mail, not local. See the MailWorks for OpenVMS System Manager's Guide for information on how to configure additional servers. 3-4 After Installing MailWorks 3.6 Accessing Directory Service Addresses To ensure that DECwindows workstation users can access the Directory Service (DDS), you must enter the following command in the SYSTEM startup file (A1MAIL$STARTUP.COM): $ @SYS$MANAGER:MB$CONTROL START=MS 3.7 Changing the System Configuration At this point, you may also want to change configurations. This section describes the different MailWorks and Transfer Service (TS) configurations, and MailWorks and DDS configurations available with this release. The following configurations are discussed: o MailWorks and No TS o MailWorks and local TS o MailWorks and remote TS o MailWorks and no DDS o MailWorks and local DDS o MailWorks and DDS Concentrator o MailWorks and DDS Distributor The MailWorks for OpenVMS System Manager's Guide contains information that will help you decide which configuration meets your requirements. 3.7.1 Glossary of Terms for Configuration Information Version 1.3A offers new configurations for installing DDS. These configurations are discussed in this section. The following terms are used to explain the various configurations. o MailWorks Target Node-The node where MailWorks for OpenVMS is installed and configured. o Distributed Directory Services (DDS)- Maintains a list of subscribers on the mail network. It contains a current record of the names and addresses of subscribers on the network. The Directory Service provides a distributed replicated database of information. DDS is a component of Message Router. After Installing MailWorks 3-5 o Remote DDS-Indicates that the DDS is installed and configured on the DDS Target Node. The MailWorks Target Node and the DDS Target Node are not the same node or in the same cluster. o Local DDS-Indicates that the DDS is installed and configured on the same node that MailWorks for OpenVMS is installed and configured. o No DDS-Indicates that MailWorks for OpenVMS is configured such that DDS access is not available. Addresses cannot be retrieved from DDS or verified using DDS. o DDS Concentrator-The Remote DDS Access configuration where the MailWorks for OpenVMS DS Server for the MailWorks Target Node and DDS are installed and configured on the DDS Target Node. In addition, MailWorks needs to be configured on the DDS Target Node. o DDS Distributor-The Remote DDS Access configuration where the MailWorks for OpenVMS DS Server is installed and configured on the MailWorks Target Node, and DDS is installed and configured on the DDS Target Node. The MailWorks Target Node and the DDS Target Node are not the same node or in the same cluster. o DDS Target Node-The node where DDS is installed and configured. o Local TS-Indicates that the TS is installed and configured on the same node that MailWorks is installed and configured. o No TS-Indicates that MailWorks for OpenVMS is configured such that the TS is not available. Messages can only be sent and delivered locally. o Remote TS-Indicates that the TS is installed and configured on the TS Target Node. The MailWorks Target Node and the TS Target Node are not the same node or in the same cluster. o Transfer Service (TS)-Transfer Service is a component of Message Router. o TS Target Node-The node where TS is installed and configured. 3-6 After Installing MailWorks 3.8 Configuring MailWorks for OpenVMS and TS This section details how to configure MailWorks for OpenVMS to use the various TS configurations. 3.8.1 Configuring MailWorks for OpenVMS and No TS Requirements If TS is not configured, there are no requirements. The following describes how to configure the MailWorks for OpenVMS system with No TS. 1. Verify the following server attributes are properly set. Refer to the MailWorks for OpenVMS System Manager's Guide on how to modify the attributes. o Clear MR_MAILBOX. o Set LOCAL_ROUTING_ADDRESS so that it does not include a mailbox. o Set USE_MR to NOUSE_MR. o Set TIME_OFFSET to "+0000". 2. Stop and restart the MUAS server. Refer to the MailWorks for OpenVMS System Manager's Guide on how to stop and restart the server. 3.8.2 Configuring MailWorks for OpenVMS and Local TS Requirements As a minimum, Message Router Version 3.3 is required to be installed and configured on the MailWorks Target Node. Local TS is not a valid configuration for MailWorks for OpenVMS AXP. See Section 3.8.1 or Section 3.8.3 for valid configuration options. The following describes how to configure the MailWorks for OpenVMS VAX system for Local TS. 1. Verify that Message Router is installed and configured on the MailWorks Target Node. 2. If a mailbox does not exist, it needs to be created. Use the command procedure, A1MAIL$LIBRARY:X400MAN$CREATE_ MAILBOX.COM to create the mailbox. This command procedure needs the mailbox name passed in. If it is After Installing MailWorks 3-7 not passed in and a value is not supplied at the prompt, the mailbox name, AM, will be used. 3. Verify the following server attributes are properly set. Refer to the MailWorks for OpenVMS System Manager's Guide on how to modify the attributes. o Set MR_MAILBOX. o Set LOCAL_ROUTING_ADDRESS. o Set USE_MR to BASIC or ALWAYS. o Set TIME_OFFSET. 4. Stop and restart the MUAS server. Refer to the MailWorks for OpenVMS System Manager's Guide on how to stop and restart the server. 3.8.3 Configuring MailWorks for OpenVMS and Remote TS Requirements As a minimum, Message Router Version 3.3A is required to be installed and configured on the TS Target Node for MailWorks for OpenVMS VAX. The following describes how to configure the MailWorks for OpenVMS system for Remote TS. 1. Verify that the correct version of Message Router is installed and configured on the TS Target Node. For MailWorks for OpenVMS AXP, verify that as a minimum Message Router Version 3.3A is installed and configured on the TS Target Node. 2. For MailWorks for OpenVMS VAX, verify that the file MRAPPSHAR.EXE that is in SYS$COMMON:[SYSLIB] on the MailWorks Target Node is the same image that is installed on the TS Target Node. For MailWorks for OpenVMS AXP, verify that the file MRAXPSHAR.EXE is in SYS$COMMON:[SYSLIB] on the MailWorks Target Node. If the file does not exist, copy the correct file from MUAS$TOOLS to the specified directory location. See Section 3.10 for complete details. 3-8 After Installing MailWorks 3. For MailWorks for OpenVMS AXP, verify that the file MRAXPMSG.EXE is in SYS$COMMON:[SYSMSG] on the MailWorks Target Node. If the file does not exist, copy the correct file from MUAS$TOOLS to the specified directory location. 4. If a mailbox does not exist on the TS Target Node, it needs to be created. The following example illustrates how to create a mailbox on the TS Target Node. $ MCR MRMAN MRM> ADD mbox /SUPPRESS_DELIVERY_REPORTS - _MRM> /PROBES_RELAYED /COMPLETE_MESSAGES - _MRM> /IGNORE_SENDER /SERVICE_MESSAGES - _MRM> /PASSWORD=password ________________________ Note ________________________ The password must match the one that you set using X4MANAGER. The password must be between 8 and 31 characters. If you want to check the mailbox password, use MRMAN SEND/IDENT. The combined length of the mailbox and password must not exceed 24 characters. ______________________________________________________ For more details on this command, refer to the Message Router System Management documentation. 5. Verify the following server attributes are properly set. Refer to the MailWorks for OpenVMS System Manager's Guide on how to modify the attributes. o Set MR_MAILBOX (Set to mbox use in previous step.). o Set LOCAL_ROUTING_ADDRESS. o Set USE_MR to BASIC or ALWAYS. o Set TIME_OFFSET. o Set MR_NODE (set to TS Target Node). o Set MR_PASSWORD (set to password used in previous step). o Set MR_POLL_INTERVAL (150 is recommended). After Installing MailWorks 3-9 6. Stop and restart the MUAS server. Refer to the MailWorks for OpenVMS System Manager's Guide on how to stop and restart the server. 3.9 Configuring MailWorks for OpenVMS and DDS This section details how to configure MailWorks for OpenVMS to use the various DDS configurations. 3.9.1 Configuring MailWorks for OpenVMS and No DDS Requirements If DDS is not configured, there are no requirements. As long as DDS is not configured and enabled on the local system, DDS will not be available to any of the clients. If Remote DDS was configured, the following describes how to configure the MailWorks for OpenVMS system for No DDS. 1. Verify that the DDS startup command procedure, DDS$STARTUP.COM, has not been run. If it has been, the logical names will need to be deassigned. 2. Verify the following DS Server attributes are properly set. See the MailWorks for OpenVMS System Manager's Guide on how to modify attributes. o DISABLE DS 3. Stop and restart the Connect Server or stop the DS Servers. Refer to the MailWorks for OpenVMS System Manager's Guide for further details about the Connect Server. 3.9.2 Configuring MailWorks for OpenVMS VAX and Local DDS Requirements As a minimum, Message Router Version 3.3 is required to be installed and configured on the MailWorks Target Node. Local DDS is not a valid configuration for MailWorks for OpenVMS AXP. See Section 3.9.1, 3.9.3, or 3.9.4 for valid configuration options. 3-10 After Installing MailWorks The following describes how to configure the MailWorks for OpenVMS VAX system for Local DDS. 1. Verify that the DDS startup command procedure, DDS$STARTUP.COM, has not been run. If it has been, the logical names will need to be deassigned. 2. Verify the following DS Server attributes are properly set. See MailWorks for OpenVMS System Manager's Guide. o Set NODS_NODE o Set DS_SERVERS to 1 or more o Set DS_TIMEOUT 3. Stop and restart the Connect Server or stop and restart the DS Servers. Refer to the MailWorks for OpenVMS System Manager's Guide for further details about the Connect Server. 3.9.3 Configuring MailWorks for OpenVMS and DDS Concentrator Requirements As a minimum, Message Router Version 3.3 is required to be installed and configured on the DDS Target Node for MailWorks for OpenVMS VAX. As a minimum, Message Router Version 3.3A is required to be installed and configured on the DDS Target Node for MailWorks for OpenVMS AXP. The same version of MailWorks for OpenVMS needs to be installed and configured on the DDS Target Node as is installed and configured on the MailWorks Target Node. The following describes how to configure the MailWorks for OpenVMS system for DDS Concentrator. 1. Verify the following DS Server attributes are properly set on the MailWorks Target Node. See the MailWorks for OpenVMS System Manager's Guide for more information. o Set DS_NODE to the DDS Target Node o Set DS_PASSWORD o Set DS_SERVERS to 1 or more o Set DS_TIMEOUT After Installing MailWorks 3-11 2. Verify the following DS Server attributes are properly set on the DDS Target Node. See the MailWorks for OpenVMS System Manager's Guide for more information. o ADD REGISTERED_NODE using the MailWorks Target Node and the DS_PASSWORD set on the MailWorks Target Node o Set DS_SERVERS to 1 or more o Set DS_TIMEOUT 3. Stop and restart the Connect Server on the DDS Target Node. Refer to the MailWorks for OpenVMS System Manager's Guide for further details about the Connect Server. 4. Stop and restart the Connect Server on the MailWorks Target Node after the Connect Server on the DDS Target Node has successfully started. 3.9.4 Configuring MailWorks for OpenVMS and DDS Distributor Requirements As a minimum, Message Router Version 3.3A is required to be installed and configured on the DDS Target Node for both MailWorks for OpenVMS VAX and MailWorks for OpenVMS AXP. The following describes how to configure MailWorks for OpenVMS and the DDS Distributor. 1. Verify that, as a minimum, Message Router Version 3.3A is installed and configured on the DDS Target Node. 2. Configure Message Router on the DDS Target Node per the Message Router Configuration Guide for Version 3.3A to allow remote client access. Configuration questions that are of particular significance to remote DDS access support are: Do you want to allow remote Directory Service access? How many query servers do you want? What is the maximum number of network links you want to permit per listener? Digital recommends 2 query servers and 10 DECnet links as a starting point. 3-12 After Installing MailWorks 3. For MailWorks for OpenVMS VAX, verify that the file DDS$RMT_VAX.EXE is in SYS$COMMON:[SYSLIB] on the MailWorks Target Node. For MailWorks for OpenVMS AXP, verify that the file DDS$RMT_ALPHA.EXE is in SYS$COMMON:[SYSLIB] on the MailWorks Target Node. If the file does not exist, copy the correct file from MUAS$TOOLS to the specified directory location. 4. For MailWorks for OpenVMS VAX, verify that the file DDS$MSG_VAX.EXE is in SYS$COMMON:[SYSMSG] on the MailWorks Target Node. For MailWorks for OpenVMS AXP, verify that the file DDS$MSG_ALPHA.EXE is in SYS$COMMON:[SYSMSG] on the MailWorks Target Node. If the file does not exist, copy the correct file from MUAS$TOOLS to the specified directory location. 5. Verify that the file DDS$STARTUP.COM is in SYS$COMMON:[SYS$STARTUP] on the MailWorks Target Node. If the file does not exist, copy the file from A1MAIL013.D in saveset D to the specified directory location. 6. Verify that the DDS Target Node is registered in DECnet on the MailWorks Target Node. 7. Verify that the MailWorks Target Node is registered in DECnet on the DDS Target Node. 8. Verify that the DDS startup command procedure DDS$STARTUP.COM has been run on MailWorks Target Node. This command procedure requires two parameters, "DDS Server Node" and "DDS Server System Node Number". "DDS Server Node" is the node name where DDS is located. "DDS Server System Node Number" can be determined by executing the following command on the DDS Target Node: $ MCR MBMAN SHOW DDS CONFIG /ALL Look for the following line: System node number : 1234 9. Verify that the following are set: o NODS_NODE o DS_SERVERS o DS_TIMEOUT After Installing MailWorks 3-13 10.Stop and restart the Connect Server or stop and restart the DS Servers. Refer to the MailWorks for OpenVMS System Manager's Guide for further details about the Connect Server. 3.10 Files Required for Different Configurations If you are going to configure MailWorks for OpenVMS VAX with remote TS, you need the following files on the MailWorks for OpenVMS VAX Target Node: SYS$COMMON:[SYSLIB]MRAPPSHAR.EXE SYS$COMMON:[SYSMSG]MRAPPMSG.EXE If you are going to configure MailWorks for OpenVMS AXP with remote TS, you need the following files on the MailWorks for OpenVMS AXP Target Node: SYS$COMMON:[SYSLIB]MRAXPSHAR.EXE SYS$COMMON:[SYSMSG]MRAXPMSG.EXE If you are going to configure MailWorks for OpenVMS VAX with remote DDS, you need the following files on the MailWorks for OpenVMS VAX Target Node: SYS$COMMON:[SYSLIB]DDS$RMT_VAX.EXE SYS$COMMON:[SYSMSG]DDS$MSG_VAX.EXE If you are going to configure MailWorks for OpenVMS AXP with remote DDS, you need the following files on the MailWorks for OpenVMS AXP Target Node: SYS$COMMON:[SYSLIB]DDS$RMT_ALPHA.EXE SYS$COMMON:[SYSMSG]DDS$MSG_ALPHA.EXE If the files are not located in the system area, copy them from the MUAS$TOOLS area to the appropriate system area. 3.11 Setting up the TCP/IP Transport Service on OpenVMS Two ports are necessary to run MailWorks using TCP/IP. One port is used by the Connect server and the other port is used by the MUAS server. To set up the TCP/IP transport for the MailWorks, do the following from a privileged account: 3-14 After Installing MailWorks 1. Edit the MailWorks startup file. o For OpenVMS VAX, edit SYS$STARTUP:A1MAIL$STARTUP.COM and modify the ELSE portion of the line: IF FILE .NES. "" THEN DEFINE/SYSTEM/SUPERVISOR_MODE A1MAIL$CONNECT_TRANSPORTS - "DECNET:[0,TASKNAME=A1M$CONNECT]","DSL:[61]" Change it to: THEN DEFINE/SYSTEM/SUPERVISOR_MODE A1MAIL$CONNECT_TRANSPORTS - "DECNET:[0,TASKNAME=A1M$CONNECT]","DSL:[61]","TCPIP:[6161]" o For OpenVMS AXP, edit SYS$STARTUP:A1MAIL$STARTUP.COM and modify the ELSE portion of the line: ELSE DEFINE/SYSTEM/SUPERVISOR_MODE A1MAIL$CONNECT_TRANSPORTS - "DECNET:[0,TASKNAME=A1M$CONNECT]" Change it to: ELSE DEFINE/SYSTEM/SUPERVISOR_MODE A1MAIL$CONNECT_TRANSPORTS - "DECNET:[0,TASKNAME=A1M$CONNECT]","TCPIP:[6161]" Exit the editor, and proceed to the next step. 2. Edit your MAIL_SERVER configuration file using the X4MANAGER utility: X4MAN.MAIL> MANAGE MAIL_SERVER X4MAN.MAIL> EDIT Modify the line that looks like this: SET TRANSPORT_LIST "DECNET:[0,TASKNAME=A1M$MUAS]" Change it to: SET TRANSPORT_LIST "DECNET:[0,TASKNAME=A1M$MUAS]","TCPIP:[8484]" Exit the editor to save the file. Stop and restart the MUAS server. X4MAN.MAIL> STOP/RESTART X4MAN.MAIL> EXIT X4MAN> EXIT After Installing MailWorks 3-15 If you have any node-specific startup files, they must be edited as described in this step. 3. Stop the Connect server using the X4MANAGER utility: X4MAN.MAIL> MANAGE REMOTE X4MAN.REMOTE> STOP 4. Restart MailWorks: $ @SYS$STARTUP:A1MAIL$STARTUP.COM 3-16 After Installing MailWorks A _________________________________________________________________ Sample MailWorks Installations This appendix contains sample installations of MailWorks for OpenVMS. The first sample installation is on a VAX system that had no previous version of MailWorks installed. The second installation is on a VAX system that had a previous version of MailWorks for OpenVMS installed. The third sample installation is of MailWorks on an AXP system. A.1 Sample New Installation The following is an example of an installation on a VAX system that did not have MailWorks installed on it before: $ @SYS$UPDATE:VMSINSTAL A1MAIL013 SYS$LOGIN OpenVMS VAX Software Product Installation Procedure V6.0 It is 28-DEC-1994 at 07:44. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: A1MAIL V1.3 Beginning installation of A1MAIL V1.3 at 07:44 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. +---------------------------------------------+ | Installing MailWorks for OpenVMS V1.3A | | X.400 MAIL product | +---------------------------------------------+ * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? Sample MailWorks Installations A-1 The following menu lists all the choices available through this installation. The server must have been installed on the system previously, or you must choose it now. At this time, enter the components that you wish to install. Use a comma-separated list (i.e., "1,2"). The installation guide has more details on these various components. 1) MailWorks Server for OpenVMS 2) MailWorks for OpenVMS DECwindows 3) MailWorks for OpenVMS Video Terminals 4) All of the above CAUTION: If this is an upgrade from a previous version, the clients must be upgraded also. * Choose installation options [4]: 1,3 * MailWorks Library disk [SYS$SYSDEVICE]: Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 1.1 Release Date: 19-APR-1991 * Does this product have an authorization key registered and loaded? YES * MUAS common disk [SYS$SYSDEVICE]: To ensure that the MailWorks server runs in the proper environment, this installation procedure will create an account for the server. This account, MUAS$SERVER, has no special privileges and it is not possible to log into this account. You must specify a unique UIC that is not a system UIC for this account to ensure proper security of the network. The password for this account will be generated. You do not need to know this password. It has been set as PRE-EXPIRED. If this scenario violates your security policies, you may change it after the installation has finished via the VMS AUTHORIZE utility. * UIC to be used for MUAS$SERVER account in format [ggg,mmm]: [57,1] A-2 Sample MailWorks Installations To ensure that the MailWorks server runs in the proper environment, this installation procedure will create an account for the server. This account, MUASNET, has the privileges TMPMBX and NETMBX. Only network logins are allowed in the MUASNET account. You must specify a unique user number for this account in order to ensure proper security of the network. The password for this account will be generated. You do not need to know this password. If this scenario violates your security policies, you may change it after the installation has finished via the VMS AUTHORIZE utility. * User number to be used for MUASNET account in format, mmm: 2 The following menu lists all the choices available through this installation. At this time, enter the option that you wish to configure. Only a single value is allowed, (i.e., "1"). The installation guide describes these options. 1) Configure to use Local Message Router Transfer Service 2) Do not configure to use Message Router Transfer Service 3) Configure to use Remote Message Router Transfer Service * Configure Message Router Transfer Service option [2]: * Local routing address [AM@ROBINS]: Remote Message Router Distributed Directory Services is a configurable option. An answer of YES indicates that Remote Message Router Distributed Directory Services will be configured. An answer of NO indicates that Remote Message Router Distributed Directory Services will not be configured. * Configure Remote Message Router DDS [NO]? There will now be a dialogue to determine the MUAS system configuration. You will be asked to specify the MUAS servers to be run on this node (and, for a cluster, other nodes). Sample MailWorks Installations A-3 Servers are uniquely identified by a three-character name, typically composed only of numeric characters. You will be asked after each set if there are more servers to be configured. Use ^Z (CTRL-Z) to cancel an entry for a server node or server disk set. * Node for server 000 [ROBINS]: * Disk for server 000 [SYS$SYSDEVICE]: * Configure more MUAS servers [YES]? NO MailWorks system configuration is now complete. Note that if you want to alter the system configuration after installation, use the X4MANAGER utility as described in the MailWorks System Manager's Guide. Checking license for command line interface Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 1.1 Release Date: 19-Apr-1991 * Does this product have an authorization key registered and loaded? YES This is the end of the questions that are asked by this installation. The rest of the installation will take about 55 minutes on a MicroVax II class machine. A-4 Sample MailWorks Installations %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUAS$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier MUAS$SERVER value: [000057,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUAS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.COM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.DB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.TOOLS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.WRK]. %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named MUAS$PROFILE_UPDATE. %UAF-I-RDBADDMSG, identifier MUAS$PROFILE_UPDATE value: %X8001000A added to rights data base %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUASNET. %UAF-I-ADDMSG, user record successfully added %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.DMP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.MSG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.TMP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.WRK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory Sample MailWorks Installations A-5 SYS$SYSDEVICE:[A1MAIL$LIBRARY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.TEST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.PRINT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.ENGLISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DANISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DUTCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.FRENCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.GERMAN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.ITALIAN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.SPANISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.SWEDISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.MUAS]. +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM, | | AFTER the network has been started up. | | | | Note that if you are installing on a cluster, this startup procedure | | should, in general, be executed on EVERY node in the cluster. Read | | the release notes for more information. | +----------------------------------------------------------------------+ Starting MailWorks for OpenVMS Job MUAS$NODE_CHECK (queue MUAS$BATCH_ROBINS, entry 399) started on MUAS$BATCH_ROBINS Job MUAS$TIDY (queue MUAS$BATCH, entry 400) started on MUAS$BATCH %RUN-S-PROC_ID, identification of created process is 2020024A Preparing to start MailWorks IVP A-6 Sample MailWorks Installations Local user distribution list needs to be updated. Starting IVP for MailWorks V1.3A. Starting server test. Starting user agent test; VT interface. NOTE: This IVP will change the current user's MailWorks user profile as follows: AUTO_PURGE is set to No CORRELATE is set to Yes Setting profile attributes. Mailing message to self. Pausing 19 seconds for message delivery. New MailWorks message on node ROBINS from SYSTEM (SYSTEM@AM@ROBINS) (28-DEC-1994 08:09:02.57) New MailWorks delivery/receipt notification on node ROBINS from POSTMASTER (@ROBINS.MUAS) (28-DEC-1994 08:09:12.53) Generating IVP output file. Checking IVP output file. You have 2 unopened MailWorks messages. MailWorks V1.3A IVP completed successfully. Installation of A1MAIL V1.3 completed at 08:09 VMSINSTAL procedure done at 08:09 $ A.2 Sample Upgrade Installation This section contains a sample installation for MailWorks for OpenVMS on a VAX system that had a previous installation of MailWorks for OpenVMS. This upgrade installation is on a system that has support for DDIF and DECwindows: Sample MailWorks Installations A-7 $ @SYS$UPDATE:VMSINSTAL A1MAIL013 SYS$SYSROOT:[SYSMGR.KITS] VAX/VMS Software Product Installation Procedure V5.5-2 It is 20-DEC-1994 at 14:06. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER MR$T_N_1 MRX$GATEWAY MRLISTEN_8194 * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: A1MAIL V1.3 Beginning installation of A1MAIL V1.3 at 14:06 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. +---------------------------------------------+ | Installing MailWorks for OpenVMS V1.3A | | X.400 MAIL product | +---------------------------------------------+ * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES The following menu lists all the choices available through this installation. The server must have been installed on the system previously, or you must choose it now. At this time, enter the components that you wish to install. Use a comma-separated list (i.e., "1,2"). The installation guide has more details on these various components. 1) MailWorks Server for OpenVMS 2) MailWorks for OpenVMS DECwindows 3) MailWorks for OpenVMS Video Terminals 4) All of the above CAUTION: If this is an upgrade from a previous version, the clients must be upgraded also. A-8 Sample MailWorks Installations * Choose installation options [4]: 4 Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 1.1 Release Date: 19-APR-1991 * Does this product have an authorization key registered and loaded? YES To ensure that the MailWorks server runs in the proper environment, this installation procedure will create an account for the server. This account, MUASNET, has the privileges TMPMBX and NETMBX. Only network logins are allowed into the MUASNET account. You must specify a unique user number for this account in order to ensure proper security of the network. The password for this account will be generated. You do not need to know this password. If this scenario violates your security policies, you may change it after the installation has finished via the VMS AUTHORIZE utility. * User number to be used for MUASNET account in format, mmm: 401 Checking license for command line interface Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 1.1 Release Date: 19-Apr-1991 * Does this product have an authorization key registered and loaded? YES Checking license for MailWorks for OpenVMS DECwindows Product: ALLIN1-MAIL-DW-CLIENT Producer: DEC Version: 1.1 Release Date: 19-APR-1991 * Does this product have an authorization key registered and loaded? YES Sample MailWorks Installations A-9 This is the end of the questions that are asked by this installation. The rest of the installation will take about 63 minutes on a MicroVax II class machine. %VMSINSTAL-I-RESTORE, Restoring product save set B ... +------------------------------------------------------------+ | A new SYS$STARTUP:A1MAIL$STARTUP.COM will be supplied with | | this installation. If there is anything specific that was | | in the old startup command procedure, you will need to | | manually add that information into the new startup command | | procedure. The old startup command procedure has been | | renamed to SYS$STARTUP:A1MAIL$STARTUP.OLD. | +------------------------------------------------------------+ %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... Shutting down any MailWorks servers on FINCHS. Job A1MAIL$STOP_SERVER (queue MUAS$BATCH_FINCHS, entry 731) holding until 20-DEC-1994 14:18 Checking for queued MailWorks server-restart jobs. Deleting restart-job #70 in queue MUAS$BATCH_FINCHS %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUASNET. %UAF-I-ADDMSG, user record successfully added %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated +--------------------------------------------------------------+ | A new A1MAIL$CONNECT_STARTUP.COM file has been created. The | | existing file has been renamed to .OLD. Please merge in any | | customizations previously made. | +--------------------------------------------------------------+ %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.PRINT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DANISH]. A-10 Sample MailWorks Installations +---------------------------------------------------------------+ | A new MUAS startup file has been created. The existing file | | has been renamed to .OLD. Please merge in any customizations | | previously made. | +---------------------------------------------------------------+ Renaming SYS$SYSDEVICE:[A1MAIL$LIBRARY]A1MAIL$SSI_MESSAGES.MSG to .OLD; Creating a new SSI message file. %VMSINSTAL-I-RESTORE, Restoring product save set G ... SYS$SYSDEVICE:[A1MAIL$LIBRARY]A1MAIL$INSTALL_DW.COM;3 81 lines Starting MailWorks for OpenVMS V1.3A Preparing to start MailWorks IVP V1.3A Starting IVP for MailWorks V1.3A. Starting server test. Starting user agent test; VT interface. NOTE: This IVP will change the current user's MailWorks user profile as follows: AUTO_PURGE is set to NO CORRELATE is set to YES Setting profile attributes. Mailing message to self. Pausing 19 seconds for message delivery. New MailWorks message on node FINCHS from SYSTEM (SYSTEM@AM@FINCHS@ADD) (20-DEC-1994 15:00:26.20) New MailWorks delivery/receipt notification on node FINCHS from POSTMASTER (@FINCHS.MUAS) (20-DEC-1994 15:00:37.01) Generating IVP output file. Checking IVP output file. You have 2 unopened MailWorks messages. Starting IVP for MailWorks for OpenVMS DECwindows Window output to which node? (Press RETURN to cancel): IVP for MailWorks for OpenVMS DECwindows cancelled Sample MailWorks Installations A-11 MailWorks V1.3A IVP completed successfully. Installation of A1MAIL V1.3 completed at 15:06 VMSINSTAL procedure done at 15:07 $ A.3 Sample Installation for an AXP System The following is an example of a new installation on an OpenVMS AXP system. $ @SYS$UPDATE:VMSINSTAL A1MAIL013 SYS$SYSROOT:[SYSMGR.KITS] OpenVMS AXP Software Product Installation Procedure V6.1 It is 22-DEC-1994 at 14:13. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: SYS$SYSDEVICE:[V13KIT] The following products will be processed: A1MAIL V1.3 Beginning installation of A1MAIL V1.3 at 14:14 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. +---------------------------------------------+ | Installing MailWorks for OpenVMS V1.3A | | X.400 MAIL product | +---------------------------------------------+ * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES The following menu lists all the choices available through this installation. The server must have been installed on the system previously, or you must choose it now. At this time, enter the components that you wish to install. Use a comma-separated list (i.e., "1,2"). A-12 Sample MailWorks Installations The installation guide has more details on these various components. 1) MailWorks Server for OpenVMS 2) MailWorks for OpenVMS Video Terminals 3) All of the above CAUTION: If this is an upgrade from a previous version, the clients must be upgraded also. * Choose installation options [3]: 3 * MailWorks Library disk [SYS$SYSDEVICE]: Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 1.1 Release Date: 19-APR-1991 * Does this product have an authorization key registered and loaded? YES * MUAS common disk [SYS$SYSDEVICE]: To ensure that the MailWorks server runs in the proper environment, this installation procedure will create an account for the server. This account, MUAS$SERVER, has no special privileges and it is not possible to log into this account. You must specify a unique UIC that is not a system UIC for this account to ensure proper security of the network. The password for this account will be generated. You do not need to know this password. It has been set as PRE-EXPIRED. If this scenario violates your security policies, you may change it after the installation has finished via the VMS AUTHORIZE utility. * UIC to be used for MUAS$SERVER account in format [ggg,mmm]: [600,600] To ensure that the MailWorks server runs in the proper environment, this installation procedure will create an account for the server. This account, MUASNET, has the privileges TMPMBX and NETMBX. Only network logins are allowed into the MUASNET account. Sample MailWorks Installations A-13 You must specify a unique user number for this account in order to ensure proper security of the network. The password for this account will be generated. You do not need to know this password. If this scenario violates your security policies, you may change it after the installation has finished via the VMS AUTHORIZE utility. * User number to be used for MUASNET account in format, mmm: 601 * Message Router mailbox name [AM_NODEA]: * Node where Remote Message Router is located : NODEB The password must match the one that is set in the X4MANAGER utility. The password must be between 8 and 31 characters long. If the user wants to check the mailbox using: MRMAN SEND/IDENT, then the combined length of the mailbox and password should be between 8 and 24 characters long. * Remote Message Router Password : RemoteMessRoutrPW * Local routing address [AM_NODEA@NODEB]: * Time offset: -0500 There will now be a dialogue to determine the MUAS system configuration. You will be asked to specify the MUAS servers to be run on this node (and, for a cluster, other nodes). Servers are uniquely identified by a three-character name, typically composed only of numeric characters. You will be asked after each set if there are more servers to be configured. Use ^Z (CTRL-Z) to cancel an entry for a server node or server disk set. * Node for server 000 [NODEA ]: * Disk for server 000 [SYS$SYSDEVICE]: MailWorks system configuration is now complete. Note that if you want to alter the system configuration after installation, use the X4MANAGER utility as described in the MailWorks System Manager's Guide. Checking license for command line interface A-14 Sample MailWorks Installations Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 1.1 Release Date: 19-Apr-1991 * Does this product have an authorization key registered and loaded? YES This is the end of the questions that are asked by this installation. The rest of the installation will take about 13 minutes on a DEC 3000 Model 300 class machine. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUAS$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier MUAS$SERVER value [000600,000600] added to rights database %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUAS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.COM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.DB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.TOOLS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER.WRK]. %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named MUAS$PROFILE_UPDATE. %UAF-I-RDBADDMSG, identifier MUAS$PROFILE_UPDATE value %X80010002 added to rights database %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named MUASNET. %UAF-I-ADDMSG, user record successfully added %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUASNET. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory Sample MailWorks Installations A-15 SYS$SYSDEVICE:[MUAS$SERVER_000]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.DMP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.MSG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.TMP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MUAS$SERVER_000.WRK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.TEST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.PRINT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.ENGLISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DANISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.DUTCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.FRENCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.GERMAN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.ITALIAN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.SPANISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1MAIL$LIBRARY.SWEDISH]. +--------------------------------------------+ | Create the mailbox on the node running MR. | +--------------------------------------------+ A-16 Sample MailWorks Installations +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM, | | AFTER the network has been started up. | | | | Note that if you are installing on a cluster, this startup procedure | | should, in general, be executed on EVERY node in the cluster. Read | | the release notes for more information. | +----------------------------------------------------------------------+ Starting MailWorks for OpenVMS Job MUAS$NODE_CHECK (queue MUAS$BATCH_NODEA, entry 279) started on MUAS$BATCH_NODEA Job MUAS$TIDY (queue MUAS$BATCH, entry 280) started on MUAS$BATCH %RUN-S-PROC_ID, identification of created process is 0000012A Preparing to start MailWorks IVP Local user distribution list needs to be updated. Starting IVP for MailWorks V1.3A. Starting server test. Starting user agent test; VT interface. NOTE: This IVP will change the current user's MailWorks user profile as follows: AUTO_PURGE is set to NO CORRELATE is set to YES Setting profile attributes. Mailing message to self. Pausing 19 seconds for message delivery. New MailWorks message on node NODEA from SYSTEM (SYSTEM@AM_NODEA@NODEB) (22-DEC-1994 14:21:47.95) New MailWorks delivery/receipt notification on node NODEA from POSTMASTER (@NODEA.MUAS) (22-DEC-1994 14:21:48.59) Generating IVP output file. Checking IVP output file. You have 2 unopened MailWorks messages. Sample MailWorks Installations A-17 MailWorks V1.3A IVP completed successfully. Installation of A1MAIL V1.3 completed at 14:22 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]A1MAIL013.VMI_DATA VMSINSTAL procedure done at 14:22 $ A-18 Sample MailWorks Installations B _________________________________________________________________ Files, Logical Names, and Processes Installed on Your System The MailWorks installation procedure installs a number of files on your system. The procedure also defines some logical names and starts specific processes. This appendix lists the file installed, describes the logical names, lists the command files used during startup, and lists the processes started during installation. B.1 File Names Table B-1 contains the names of files that are always installed on your system when you install MailWorks. Table_B-1_Files_Installed_During_Installation______________ Directory______________File_Name___________________________ Common_Files_______________________________________________ SYS$HELP A1MAIL013_iso_code.RELEASE_NOTES SYS$TEST A1MAIL$VMS_IVP.COM SYS$MESSAGE A1MAIL$MESSAGES.EXE SYS$MESSAGE A1MAIL$SSI_MESSAGES.EXE SYS$MESSAGE A1MAIL$MESSAGES_EN.EXE A1MAIL$LIBRARY A1MAIL$CCT_KEYDEF.INI for Video Terminals A1MAIL$DEFINE_LANGUAGES.COM A1MAIL$INSTALL_IMAGES.COM A1MAIL$INSTALL_CCT.COM for Video Terminals A1MAIL$INSTALL_MAC.COM (continued on next page) Files, Logical Names, and Processes Installed on Your System B-1 Table_B-1_(Cont.)_Files_Installed_During_Installation______ Directory______________File_Name___________________________ Common_Files_______________________________________________ A1MAIL$INSTALL_MSDOS.COM A1MAIL$COMMON_STARTUP.TEMPLATE A1MAIL$CONNECT_STARTUP.TEMPLATE A1MAIL$SERVER_STARTUP.COM A1MAIL$LANGUAGES.DAT A1MAIL$LANGUAGES_DEFAULT.DAT A1MAIL$PURGE.COM A1MAIL$STARTUP.TEMPLATE A1MAIL$STOP_PRINT_SERVER.COM DMW$COLLECT_INFO.COM DMW$FORCE_DUMP.COM DMW$FORCE_DUMP.EXE MUAS$SERVER_SYSTEM_STARTUP.TEMPLATE X400MAN$CREATE_DEFAULT_PROFILE.COM X400MAN$CREATE_MAILBOX.COM X400MAN$GET_PRINT_SERVER.COM A1MAIL$REGISTERED_EDITORS.TXT A1MAIL$COMPRESS.COM A1MAIL$SET_CUSTOMIZE_LOGICAL.COM A1MAIL$SET_LOCAL_ROUTING_ADDRESS.COM A1MAIL$SET_SERVER_LIST.COM A1MAIL$SET_TIME_OFFSET.COM A1MAIL$SHOW_UNOPENED.EXE A1MAIL$SSI_MESSAGES.MSG X400MAN$SM_KEYDEF.INI for Server A1MAIL$LIBRARY:[.languaFiles for all languages on your system are installed when MailWorks is installed. (continued on next page) B-2 Files, Logical Names, and Processes Installed on Your System Table_B-1_(Cont.)_Files_Installed_During_Installation______ Directory______________File_Name___________________________ Common_Files_______________________________________________ A1MADDR.DAT A1MDIST.TXT A1MDWRH.TXT A1MIOSRH.TXT A1MKEYWD.DAT A1MSHOW.TXT A1MAIL$PROFILE_TEMPLATE_ALL-IN-1.DAT A1MAIL$PROFILE_TEMPLATE_DEFAULT.DAT A1MAIL$PROFILE_TEMPLATE_VMSMAIL.DAT ___________________________________________________________ MailWorks_for_OpenVMS_Video_Terminals_Files________________ SYS$SYSTEM A1MAIL$CCT_MAIL.EXE SYS$HELP A1MAIL$CCT_HELP.HLB SYS$TEST A1MAIL$VTVMS_IVP.COM ___________________________________________________________ MailWorks_Server_Basic_Components__________________________ SYS$STARTUP A1MAIL$STARTUP.COM A1MAIL$CONNECT_STARTUP.COM MUAS$STARTUP.COM SYS$SYSTEM A1MAIL$PRINT_SERVER.EXE A1MAIL$CONNECT.EXE A1MAIL$DIRECTORY.COM A1MAIL$CTI_BROKER.EXE A1MAIL$DDS_SERVER.EXE MUAS$SVRCHK_MAIN.EXE MUAS$SERVER.EXE MUAS$SERVER_LOGIN.COM MUAS$SUBPROC.EXE (continued on next page) Files, Logical Names, and Processes Installed on Your System B-3 Table_B-1_(Cont.)_Files_Installed_During_Installation______ Directory______________File_Name___________________________ MailWorks_Server_Basic_Components__________________________ TLNK$REMOTE.EXE X400MAN.EXE SYS$SHARE A1MAIL$SHARE.EXE DSL$SHR.EXE A1MAILDOSSHR.EXE A1MAILMACSHR.EXE CTISHR$DECNET.EXE CTISHR$TCPIP.EXE CTISHR$DSL.EXE-VAX systems only MUAS$SHARE.EXE MUAS$CLIENT_SHARE.EXE MUAS$SERVER_SHARE.EXE MUAS$MRIF_SHR.EXE MUAS$SM_SHARE.EXE MUAS$TRANSLATOR_SHARE.EXE MUAS$TABLE_SHARE.EXE X400$SSI_SHARE.EXE SYS$MESSAGE A1MAIL$MESSAGES.EXE A1MAIL$SSI_MESSAGES.EXE A1MAIL$MESSAGE_EN.EXE A1MAIL$CONV_MSG.DAT MUAS$CLIENT_MSG.EXE MUAS$SERVER_MSG.EXE A1MAIL$LIBRARY A1MAIL$PRINT_PS_HDR.EPS A1MMACTT.TXT A1MDIST.TXT A1MAIL$INSTALL_MSDOS.COM A1MAIL$INSTALL_MAC.COM (continued on next page) B-4 Files, Logical Names, and Processes Installed on Your System Table_B-1_(Cont.)_Files_Installed_During_Installation______ Directory______________File_Name___________________________ MailWorks_Server_Basic_Components__________________________ X400MAN$CREATE_ALL-IN-1_PROFILE.COM X400MAN$CREATE_VMSMAIL_PROFILE.COM X400MAN$CREATE_BATCH_QUEUE.COM X400MAN$GET_LIST_OF_TEMP_SERVERS.COM X400MAN$RELEASE_NODE_CHECK.COM X400MAN$REM_SRV_SHUTDOWN.COM X400MAN$REM_SRV_STARTUP.COM X400MAN$GET_REMOTE_SERVER.COM [MUAS$SERVER.COM] A1MAIL$COMMON_STARTUP.COM MUAS$CREATE_DIRECTORY.COM MUAS$CREATE_SEMANTIC_TABLES.COM MUAS$SET_SYMBOLS.COM MUAS$UPDATE_QUOTA.COM MUAS$DELETE_DIRECTORY.COM MUAS$KEYPAK_CONVERT.COM MUAS$NODE_CHECK.COM MUAS$SERVER_INPUT.COM MUAS$SERVER_SYSTEM_STARTUP.COM MUAS$TABLE_SHARE.COM MUAS$TIDY.COM [MUAS$SERVER.DB] COUNTER_FILENAME_nnn.DAT MUAS$SERVER_SYSTEM_STARTUP.COM MUAS$PROFILE.DAT MUAS$PROFILE.FDL MUAS$SYSTEM_CONFIG.DAT MUAS$SYSTEM_CONFIG.FDL MUAS$SUBSTITUTE_BODY.DDIF MUAS$SUBSTITUTE_BODY.TEXT (continued on next page) Files, Logical Names, and Processes Installed on Your System B-5 Table_B-1_(Cont.)_Files_Installed_During_Installation______ Directory______________File_Name___________________________ MailWorks_Server_Basic_Components__________________________ MUAS$TABLE_SHARE.MAR DMW$SYSTEM_CONFIG.DAT DMW$SYSTEM_CONFIG.FDL MUAS$WPLDEF.FDL [MUAS$SERVER.TOOLS] MUAS$CLIENT_MSG.OBJ DDS$MSG_ALPHA.EXE DDS$MSG_VAX.EXE DDS$RMT_ALPHA.EXE DDS$RMT_VAX.EXE MRAPPMSG.EXE MRAPPSHAR.EXE MRAXPMSG.EXE MRAXPSHAR.EXE MUAS$EVL_DEFINITIONS.H MUAS$SERVER_EXEID_CUSTOMER.OPT MUAS$MDL_MAIN.EXE MUAS$SERVER_MSG.OBJ MUAS$TABLE_SHARE.OPT MUAS$TBL_ACCESS.OBJ ___________________________________________________________ DEC_MAILworks_for_OpenVMS_DECwindows_Files_________________ SYS$SYSTEM A1MAIL$DW_MAIL.EXE SYS$LIBRARY A1MAIL$DW_MAILSHR.EXE A1MAIL$DEFAULTS.DAT A1MAIL$DW_DATETIME.UID A1MAIL$DW_MAIN.UID A1MAIL$DW_MISC.UID A1MAIL$DW_PAB.UID (continued on next page) B-6 Files, Logical Names, and Processes Installed on Your System Table_B-1_(Cont.)_Files_Installed_During_Installation______ Directory______________File_Name___________________________ DEC_MAILworks_for_OpenVMS_DECwindows_Files_________________ A1MAIL$DW_READ.UID A1MAIL$DW_SEND.UID A1MAIL$DW_WASTE.UID DWFC$FSW.UID SYS$TEST A1MAIL$DWVMS_IVP.COM SYS$HELP A1MAIL$DW_HELP.HLB A1MAIL$LIBRARY_________A1MAIL$INSTALL_DW.COM_______________ B.2 Logical Names The logical names in Table B-2 are entered into the system logical name tables when MailWorks is installed. These names are stored in the product's startup file. They are automatically entered into the system logical name table whenever the system reboots or whenever the software is invoked. Table_B-2_System-Wide_Logical_Names________________________ Logical_Name____________Translation_____Description________ A1MAIL$BROADCAST variable List of clients (other than OpenVMS) that support new mail broadcasting. A1MAIL$BROADCAST_STATE variable Used to debug problems with new mail notification. A1MAIL$CONNECT_ variable List of types TRANSPORT of transport available. (continued on next page) Files, Logical Names, and Processes Installed on Your System B-7 Table_B-2_(Cont.)_System-Wide_Logical_Names________________ Logical_Name____________Translation_____Description________ A1MAIL$DEFAULT_ English Used in LANGUAGE multilingual installations as the system default language. A1MAIL$DDS_AVAILABLE variable A1MAIL$DDS_MIN_SURNAME variable Minimum number of characters that must be entered in the surname field when doing DDS lookup. A1MAIL$DISTRIBUTION_ (disk_entered):[A1MAIL$LIBRARY.DL ] LISTS Points to the Distribution List subdirectory. A1MAIL$INTERNAL_TRACE not defined Used as a debugging aid. A1MAIL$LANGUAGE_xx variable Used in multilingual installations for processing error messages. A1MAIL$LIBRARY (disk_ entered):[A1MAIL$LIBRARY] Library of common utilities and management data. A1MAIL$LIBRARY_ROOT (disk_ entered):[A1MAIL$LIBRARY.] (continued on next page) B-8 Files, Logical Names, and Processes Installed on Your System Table_B-2_(Cont.)_System-Wide_Logical_Names________________ Logical_Name____________Translation_____Description________ Rooted logical name used to access subdirectories of A1MAIL$LIBRARY. A1MAIL$LOCAL_ROUTING_ Local routing Used during address ADDRESS address verification as the completion value for the local address and from fields. A1MAIL$PRINT_SERVER_ variable MBX A1MAIL$SERVER_LIST List of nodes Used when running connecting to send enabled mail and to update MUAS$SERVERs. profile. A1MAIL$TEST (disk_ entered):[A1MAIL$LIBRARY.TEST] Used during IVP and also when A1MAIL$INTERNAL_ TRACE is set. The directory where the Connect server logs are stored. A1MAIL$TIME_OFFSET variable Local offset from Network Standard Time. A1MAIL$CONNECT_ variable Used as a debugging INTERNAL_TRACE aid. A1MAIL$CONNECT_ variable Used as a debugging PROCESS_DUMP aid. A1MAIL$CONNECT_ERROR_ variable Used as a debugging DUMP aid. (continued on next page) Files, Logical Names, and Processes Installed on Your System B-9 Table_B-2_(Cont.)_System-Wide_Logical_Names________________ Logical_Name____________Translation_____Description________ MUAS$_ERROR_DUMP variable Used as a debugging aid. MUAS$TOOLS (disk_entered):[MUAS$SERVER.TOOLS] Used by MUAS server to store common utilities. MUAS$CMDS (disk_entered):[MUAS$SERVER.CMDS] MUAS$COMMON (disk_entered):[MUAS$SERVER] Top level directory used by MUAS server where profile and configuration are stored. MUAS$DB (disk_entered):[MUAS$SERVER.DB] MUAS$DEFAULT_SERVER MUAS$EXAMPLE MUAS$NOTIF_FETCH_MBX MUAS$SERVER_OBJECT 84 DECnet Object ID used for network operations. MUAS$SUBSTITUTE_BODY_ DDIF MUAS$SUBSTITUTE_BODY_ TEXT MUAS$WPLDEF________________________________________________ Table B-3 shows the command files used during startup. B-10 Files, Logical Names, and Processes Installed on Your System Table_B-3_Command_Files_Used_During_Startup________________ Directory_______Command_File___________Description_________ A1MAIL$LIBRARY: A1MAIL$SET_SERVER_ Defines logical name LIST A1MAIL$SERVER_LIST. A1MAIL$DEFINE_ Defines logical LANGUAGES name A1MAIL$DEFINE_ LANGUAGES. A1MAIL$SET_LOCAL_ROUTING_ADDRESS Defines logical name A1MAIL$LOCAL_ ROUTING_ADDRESS. A1MAIL$SET_CUSTOMIZE_LOGICAL Defines logical name A1MAIL$SET_ CUSTOMIZE_LOGICAL. A1MAIL$SET_TIME_ Defines logical name OFFSET A1MAIL$SET_TIME_ OFFSET. A1MAIL$INSTALL_IMAGES Installs all images required to run ALL-IN-1 Mail for OpenVMS. [MUAS$SERVER.COMA1MAIL$COMMON_ STARTUP.COM Used as input to start MUAS$SERVER. MUAS$CREATE_SEMANTIC_TABLE Defines logical name MUAS$CREATE_ SEMANTIC_TABLE. MUAS$NODE_CHECK Defines logical name MUAS$NODE_CHECK. (continued on next page) Files, Logical Names, and Processes Installed on Your System B-11 Table_B-3_(Cont.)_Command_Files_Used_During_Startup________ Directory_______Command_File___________Description_________ ___________________________________________________________ Used by X4MANAGER__________________________________________________ A1MAIL$LIBRARY X400MAN$CREATE_ALL-IN-1_PROFILE.COM Used to create the profile template for ALL-IN-1, IOS mode. X400MAN$CREATE_VMSMAIL_PROFILE.COM Used to create the profile template for VMS Mail mode. X400MAN$CREATE_BATCH_QUEUE.COM Used by X4MANAGER. X400MAN$GET_LIST_OF_TEMP_SERVERS.COM Used by X4MANAGER. X400MAN$RELEASE_NODE_CHECK.COM Used by X4MANAGER. X400MAN$REM_SRV_SHUTDOWN.COM Used by X4MANAGER. X400MAN$REM_SRV_STARTUP.COM Used by X4MANAGER. X400MAN$GET_REMOTE_SERVER.COM _______________________________________Used_by_X4MANAGER.__ Table B-4 shows the processes started during installation. Table_B-4_Processes_Started_During_Installation____________ Process_______________System_______________________________ A1MAIL$PRINT Allows PCs to format and print from the MailWorks server. (continued on next page) B-12 Files, Logical Names, and Processes Installed on Your System Table_B-4_(Cont.)_Processes_Started_During_Installation____ Process_______________System_______________________________ A1MAIL$CONNECT Provides PCs a connection to services on the OpenVMS system. MUAS$SERVER_nnn Provides the MailWorks server. A1MAIL$DIRECT_nnn Provides multiple concurrent DDS ______________________lookups._____________________________ Files, Logical Names, and Processes Installed on Your System B-13