________________________________________________________________ Contents About This Guide......................................... vii 1 Preparing to Install ALL-IN-1 MAIL for VMS Required Operating System Components............ 1-1 Prerequisite and Optional Software.............. 1-2 Prerequisite Hardware........................... 1-2 VMS License Management Facility................. 1-2 Preparing to Install ALL-IN-1 MAIL for VMS for the First Time.................................. 1-3 Installation Procedure Requirements............. 1-6 Time ......................................... 1-6 Privileges ................................... 1-6 Disk Space ................................... 1-7 System Parameters ............................ 1-7 Calculating the Values for GBLPAGES and GBLSECTIONS............................. 1-10 Changing System Parameter Values with AUTOGEN................................. 1-11 VMSINSTAL Requirements ....................... 1-12 Backing Up Your System Disk .................. 1-12 iii 2 Installing ALL-IN-1 MAIL for VMS General Information............................. 2-1 Accessing the Online Release Notes Before Installing................................... 2-1 Running the Installation Verification Procedure (IVP).............................. 2-2 Aborting the Installation .................... 2-4 The Installation Procedure...................... 2-5 Invoking VMSINSTAL ........................... 2-5 Installation Questions ....................... 2-6 Informational Messages ....................... 2-18 Output from the Installation Verification Procedure.................................... 2-20 Completing the Installation Procedure ........ 2-21 Error Recovery.................................. 2-21 3 After Installing ALL-IN-1 MAIL for VMS User Account Requirements....................... 3-1 4 Installing ALL-IN-1 MAIL Client for DOS Prerequisite and Optional Software.............. 4-1 Prerequisite Hardware........................... 4-1 Time ......................................... 4-2 Privileges ................................... 4-2 Disk Space ................................... 4-2 Files Added to the System .................... 4-2 Invoking VMSINSTAL ........................... 4-3 Installation Questions ....................... 4-3 Informational Messages ....................... 4-6 Completing the Installation Procedure ........ 4-6 Error Recovery.................................. 4-7 iv A Sample ALL-IN-1 MAIL Installations Full New Installation........................... A-1 Full Upgrade Installation....................... A-6 ALL-IN-1 MAIL for VMS DECwindows Client-only Installation.................................... A-11 Sample Installation of ALL-IN-1 MAIL Client for DOS............................................. A-13 B Files and Logical Names Installed on Your System Logical Names................................... B-8 Examples 1-1 Global Section Summary........................... 1-10 Tables 1-1 Disk Space Requirements.......................... 1-7 1-2 Global Sections and Pages Required............... 1-8 3-1 User Account Quotas.............................. 3-1 B-1 Files Installed During Installation.............. B-1 B-2 System-wide Logical Names........................ B-8 B-3 Command Files Used During Startup................ B-10 v _____________________________________________ ALL-IN-1 MAIL for VMS Installation Guide AA-ME54A-TE digital equipment corporation maynard, massachusetts _____________________________________________ May 1990 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. © by Digital Equipment Corporation May 1990. All Rights Reserved. Printed in U.S.A. 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 Digital UNIBUS CDA LN03 VAX Cluster Wide MAILbus VAXcluster DDIF MASSBUS VAX RMS DEC MicroVAX VAXstation DECdx PrintServer 40 VMS DECnet Q-bus VT DECUS REGIS XUI DECwindows ULTRIX DIGITAL The following are third-party trademarks: PostScript is a registered trademark of Adobe Systems, Inc. PROFS is a registered trademark of IBM Corporation. SNADS is a registered trademark of IBM Corporation. UNIX is a registered trademark of American Telephone & Telegraph Company. ZK5417 ________________________________________________________________ Contents About This Guide......................................... vii 1 Preparing to Install ALL-IN-1 MAIL for VMS Required Operating System Components............ 1-1 Prerequisite and Optional Software.............. 1-2 Prerequisite Hardware........................... 1-2 VMS License Management Facility................. 1-2 Preparing to Install ALL-IN-1 MAIL for VMS for the First Time.................................. 1-3 Installation Procedure Requirements............. 1-6 Time ......................................... 1-6 Privileges ................................... 1-6 Disk Space ................................... 1-7 System Parameters ............................ 1-7 Calculating the Values for GBLPAGES and GBLSECTIONS............................. 1-10 Changing System Parameter Values with AUTOGEN................................. 1-11 VMSINSTAL Requirements ....................... 1-12 Backing Up Your System Disk .................. 1-12 iii 2 Installing ALL-IN-1 MAIL for VMS General Information............................. 2-1 Accessing the Online Release Notes Before Installing................................... 2-1 Running the Installation Verification Procedure (IVP).............................. 2-2 Aborting the Installation .................... 2-4 The Installation Procedure...................... 2-5 Invoking VMSINSTAL ........................... 2-5 Installation Questions ....................... 2-6 Informational Messages ....................... 2-18 Output from the Installation Verification Procedure.................................... 2-20 Completing the Installation Procedure ........ 2-21 Error Recovery.................................. 2-21 3 After Installing ALL-IN-1 MAIL for VMS User Account Requirements....................... 3-1 4 Installing ALL-IN-1 MAIL Client for DOS Prerequisite and Optional Software.............. 4-1 Prerequisite Hardware........................... 4-1 Time ......................................... 4-2 Privileges ................................... 4-2 Disk Space ................................... 4-2 Files Added to the System .................... 4-2 Invoking VMSINSTAL ........................... 4-3 Installation Questions ....................... 4-3 Informational Messages ....................... 4-6 Completing the Installation Procedure ........ 4-6 Error Recovery.................................. 4-7 iv A Sample ALL-IN-1 MAIL Installations Full New Installation........................... A-1 Full Upgrade Installation....................... A-6 ALL-IN-1 MAIL for VMS DECwindows Client-only Installation.................................... A-11 Sample Installation of ALL-IN-1 MAIL Client for DOS............................................. A-13 B Files and Logical Names Installed on Your System Logical Names................................... B-8 Examples 1-1 Global Section Summary........................... 1-10 Tables 1-1 Disk Space Requirements.......................... 1-7 1-2 Global Sections and Pages Required............... 1-8 3-1 User Account Quotas.............................. 3-1 B-1 Files Installed During Installation.............. B-1 B-2 System-wide Logical Names........................ B-8 B-3 Command Files Used During Startup................ B-10 v ________________________________________________________________ About This Guide This document contains information on how to install ALL-IN-1 MAIL for VMS. It also contains information on how to install ALL-IN-1 MAIL Client for DOS as a PCSA disk service. Associated Documentation The following documentation is also available for ALL-IN-1 MAIL, supporting both the VMS DECwindows and Video Terminal products: _ ALL-IN-1 MAIL System Manager's Guide _ ALL-IN-1 MAIL for VMS DECwindows User's Guide _ ALL-IN-1 MAIL for Video Terminals User's Guide _ ALL-IN-1 MAIL for Video Terminals Quick Reference Card vii 1 ________________________________________________________________ Preparing to Install ALL-IN-1 MAIL for VMS This chapter discusses the preparations and requirements necessary for installing ALL-IN-1 MAIL for VMS Version 1.0. ALL-IN-1 MAIL provides online Release Notes. Digital strongly recommends that you read the Release Notes before proceeding with the installation, in case there is any applicable installation information. The release notes can be accessed before installation as described in Accessing the Online Release Notes Before Installing. After the installation, the release notes can be found in: SYS$HELP:A1MAIL.RELEASE_NOTES Required Operating System Components Most of the ALL-IN-1 MAIL for VMS components require VMS Version 5.2 or higher, except that ALL-IN-1 MAIL for VMS DECwindows requires VMS Version 5.3 or higher. Preparing to Install ALL-IN-1 MAIL for VMS 1-1 Prerequisite and Optional Software This section discusses the software you must have installed on your system before installing ALL-IN-1 MAIL. These must all be installed on the same node on which you will be installing the server. 1 Message Router Version 3.1 or greater. Message Router must be installed, configured, and started before ALL-IN-1 MAIL for VMS can be installed. Message Router is available from SSB. 2 DECwindows. The DECwindows component of VMS must be installed before DDIF documents can be supported by the mail system. The DECwindows component distributed with VMS Version 5.3 or higher must be installed before installing ALL-IN-1 MAIL for VMS DECwindows. Prerequisite Hardware ALL-IN-1 MAIL for VMS DECwindows requires a DECwindows display device to run, including the IVP associated with that portion of the installation. VMS License Management Facility The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with ALL-IN-1 MAIL for VMS. 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 required: 1 One for ALL-IN-1 MAIL Server for VMS This license must be registered. ALL-IN-1 MAIL Server for VMS is required before any other component can be installed (VT, DECwindows, or DOS). 2 One for ALL-IN-1 MAIL for VMS DECwindows If you do not wish to install the DECwindows interface, you do not need to register this license. 3 One for ALL-IN-1 MAIL for Video Terminals If you do not wish to install the VT interface, you do not need to register this license. 1-2 Preparing to Install ALL-IN-1 MAIL for VMS It is best to register your ALL-IN-1 MAIL licenses 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 already done so, you can complete the installation; however, you will not be able to run either the ALL-IN-1 MAIL software or its IVP. Once you perform the license registration and have loaded an authorization key, you will be able to run the IVP and use ALL-IN-1 MAIL. To register a license under VMS Version 5.0, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: _ Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key (PAK). _ Issue the LICENSE REGISTER DCL command with the appropri- ate 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-DEC-1990" - /VERSION=1.0 - /CHECKSUM=1-AAAA-BBBB-CCCC-DDDD NOTE: This is not a valid license. For complete information on using LMF, see the manual on the License Management Utility in the VMS Version 5.0 documentation set. Preparing to Install ALL-IN-1 MAIL for VMS for the First Time Below are some general considerations for the first time installation of ALL-IN-1 MAIL for VMS. _ Should you install Message Router? The Message Router allows you to send mail off-node and to other mail systems such as VMS Mail, ALL-IN-1 Integrated Office System, and IBM systems such as PROFS and SNADS. Preparing to Install ALL-IN-1 MAIL for VMS 1-3 If you choose to install Message Router, refer to the Message Router Installation Guide for more detailed information. However, it is suggested that when you are asked to configure Message Router, you NOT choose the default configuration, and then take the configuration defaults. 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 install Message Router, you cannot send mail to users on another node (cluster), to VMS Mail users, or through any other gateways to other vendors' products. If your users will be sending mail only locally, such as within a bounded PC-Lan system, then you would normally choose not to install Message Router. Message Router uses mailboxes as conduits to pass messages to different mail agents. If you install ALL-IN-1 MAIL, and choose to use Message Router, the mailbox created is called AM. This default name may be overridden at installation time. _ On which node(s) of your system do you wish to run the server processes? These server processes are: _ MUAS$SERVER, that handles all sending and delivering of mail. _ A1MAIL$CONNECT, that handles PC connections from ALL- IN-1 MAIL Client for DOS. 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, number of users of each machine, and so on. If you are going to run ALL-IN-1 MAIL with Message Router, then MUAS$SERVER (and implicitly A1MAIL$CONNECT) must be running on the same node as Message Router. In a LAVc configuration, it should be the boot node. In a cluster, more than one node may be running servers. If you change your mind after installation, the configu- ration may be changed using the system management utility X4MAN, described in ALL-IN-1 MAIL System Manager's Guide. _ Which user interface(s) do you wish to run? 1-4 Preparing to Install ALL-IN-1 MAIL for VMS Choose from the DECwindows user interface, support for the DOS interface (as provided by the DOS client), and the Video Terminal interface (command line). During installation you will be asked to select which of these interfaces you wish to install. Any combination may be selected. If you wish to add any other interfaces after the initial installation, this may be done through the installation process. ALL-IN-1 MAIL for VMS DECwindows Client-only Installation has an example of the installation of ALL-IN- 1 MAIL for VMS DECwindows only. _ 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, it is recommended that you spread out the I/O intensive work among other (user) disks. Each MUAS$SERVER may use a different disk for a work area; for each MUAS$SERVER, you will be prompted for which disk to use. No disk scratch areas are required for A1MAIL$CONNECT. All the clients require a single library area of about 700 blocks in which to store miscellaneous files. You will be prompted for a disk on which to put this library. _ Which UIC should you use for the MUAS$SERVER account? This account will be automatically created by the installation procedure; 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. Preparing to Install ALL-IN-1 MAIL for VMS 1-5 (In other words, not a SYSTEM account.) The UIC must be unique; the installation will fail if it is not. 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 Installation Procedure Requirements This following sections discuss various other requirements for installing ALL-IN-1 MAIL for VMS. Time The installation should take approximately 40 minutes on a MicroVAX II. This time may differ, depending on your type of media and your system configuration. Of this time, only 20 minutes are required to answer all the questions; the rest is used for creating files, setting up configuration, and so on. Privileges To install ALL-IN-1 MAIL for VMS Version 1.0, you must be logged in to an account that has at least the following privileges authorized: _ WORLD _ CMKRNL _ SYSPRV _ SYSNAM _ OPER Note that VMSINSTAL turns off BYPASS privilege at the start of installation. 1-6 Preparing to Install ALL-IN-1 MAIL for VMS Disk Space Installing the full ALL-IN-1 MAIL for VMS Version 1.0 kit requires 30,000 blocks of free storage disk space during the installation. Once ALL-IN-1 MAIL is installed, less storage space is required. Table 1-1 summarizes the storage requirements for ALL-IN-1 MAIL. Please note that all block counts are approximate. Table 1-1 Disk Space Requirements _____________________________________________________________ Blocks Blocks after: Blocks During After, on Work Description_________Installation_____SYS$SYSDEVICE____disk___ All components 30,000+ 8,550 18,200 Server components 5,200 3,500 500 Server programming 17,000 0 17,000 kit components DECwindows User 3,000 3,000 700++ Interface Command Line 1,700 1,700 700++ Interface DOS User Interface 350 350 700++ Support _____________________________________________________________ +Includes installation overhead ++Common library between all interfaces; installed once _____________________________________________________________ System Parameters There are no special system parameters required to run this baselevel. Check that your system can accommodate the installed images listed in the following table: Preparing to Install ALL-IN-1 MAIL for VMS 1-7 Table 1-2 Global Sections and Pages Required _____________________________________________________________ Image______________________GLOBAL_SECTIONS_____GLOBAL_PAGES__ A1MAIL$MESSAGES 1 126 A1MAIL$SHARE 3 385 DSL$SHR 3 94 MUAS$CLIENT_MSG 1 21 MUAS$SERVER_MSG 1 54 MUAS$SERVER_SHARE 3 11 MUAS$SHARE 2 243 MUAS$TRANSLATOR_SHARE 3 14 X400$SSI_MESSAGES 1 8 X400$SSI_SHARE 3 104 __________________________________ Total for basic 20 2196 components (continued on next page) 1-8 Preparing to Install ALL-IN-1 MAIL for VMS Table 1-2 (Cont.) Global Sections and Pages Required _____________________________________________________________ _____________________________________________________________ For_each_server______________________________________________ MUAS_NON_DYN 1 20 MUAS_DYN 1 6 MUAS_STATUS 1 15 MUAS_COUNTER 1 3 __________________________________ Total for each MUAS$SERVER 4 44 _____________________________________________________________ For DOS User Interface support______________________________________________________ A1MAILDOSSHR 1 8 _____________________________________________________________ For DDIF support and DECwindows___________________________________________________ DDIF$VIEWSHR 4 210 DECW$AILSHR 2 2 A1MAIL$DW_MAIL 1 1 A1MAIL$DW_MAILSHR 2 851 __________________________________ Total for DDIF support 9 1054 and DECwindows User Interface (continued on next page) Preparing to Install ALL-IN-1 MAIL for VMS 1-9 Table 1-2 (Cont.) Global Sections and Pages Required _____________________________________________________________ Image______________________GLOBAL_SECTIONS_____GLOBAL_PAGES__ For_VT_User_Interface________________________________________ A1MAIL$CCT_MAIL 3 654 Grand_total________________37__________________3956__________ Calculating the Values for GBLPAGES and GBLSECTIONS To install and run ALL-IN-1 MAIL for VMS, you must set the correct values for the GBLPAGES and GBLSECTIONS system parameters. The values for GBLPAGES and GBLSECTIONS in Table 1-2 indicate that you must have at least 3956 unused pages and 37 unused sections available on your system for the installation to process successfully. To calculate how many unused global pages and global sections your system has, perform the following: 1 Run the VMS Install Utility (INSTALL) using the following DCL commands: $ INSTALL LIST /GLOBAL /SUMMARY The INSTALL utility displays a summary of global pages and global sections used by your system, as well as the current number of unused global pages. For example: Example 1-1 Global Section Summary Summary of Local Memory Global Sections 258 Global Sections Used, 22580/3420 Global Pages Used/Unused 2 Determine if the number of unused pages on your system is equal to or greater than the number specified in Table 1-2. If the number of unused pages is less than the number listed in the table, you need to increase the value for GBLPAGES. 3 Note the amount shown for "Global Sections Used" in Example 1-1. 1-10 Preparing to Install ALL-IN-1 MAIL for VMS 4 Run the SYSGEN utility and use the SHOW command to determine the number of global sections that has been allocated: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections 5 Subtract the amount shown in Example 1-1 from the amount in the CURRENT column. If the difference is less than the number required in Table 1-2, you need to increase the value of the GBLSECTIONS parameter. The following section describes the procedures for increasing these values as well as those of other system parameters. Refer to the VMS documentation on System Management and Operations for more information. Changing System Parameter Values with AUTOGEN You use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the ones you reset manually. To change system parameters with AUTOGEN, you must edit the following file: SYS$SYSTEM:MODPARAMS.DAT For example, to increment the global pages SYSGEN parameter use the following: ADD_GBLPAGES = 2000 Now, run the AUTOGEN procedure to recalculate your 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. Rebooting your system makes the new parameter values active. Also on VMS Version 5.x systems, you may wish 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 VMS documentation on System Management and Operations. Preparing to Install ALL-IN-1 MAIL for VMS 1-11 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: _ Whether you are logged in to a privileged account _ Whether you have adequate quotas for installation _ 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 instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press RETURN. Then correct the problem and restart the installation. Backing Up Your System Disk 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. 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 VMS documentation set. 1-12 Preparing to Install ALL-IN-1 MAIL for VMS 2 ________________________________________________________________ Installing ALL-IN-1 MAIL for VMS This chapter describes in detail how to install ALL-IN-1 MAIL for VMS. The first section contains general installation information. The second section contains a step-by-step description of the installation procedure. General Information This section includes information about accessing Release Notes, determining files and logical names added to your system, running the Installation Verification Procedure (IVP), and aborting the installation. Accessing the Online Release Notes Before Installing ALL-IN-1 MAIL for VMS 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 in case they contain any information about changes in the installation procedures. If you specified OPTIONS N when you invoked VMSINSTAL, you are now given four options for reviewing the Release Notes. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options:) 1. Display Release Notes 2. Print Release Notes 3. Both 1 and 2 4. None of the above * Select option [2]: Installing ALL-IN-1 MAIL for VMS 2-1 If you select option 1, VMSINSTAL displays the Release Notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. 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 ALL-IN-1 MAIL for VMS Version 1.0 are quite lengthy, we recommend that you choose option 2. Continuing the installation: The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press RETURN. In either case, the Release Notes are copied to a file in the SYS$HELP directory, unless you chose option 5 above. For example: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The products Release Notes have been successfully moved to SYS$HELP. The Release Notes are located in the following file:. SYS$HELP:A1MAIL010.RELEASE_NOTES Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 MAIL 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. It is recommended that you run the IVP to be sure that ALL-IN-1 MAIL is installed correctly. After ALL-IN-1 MAIL is installed, 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 be sure that users can access ALL-IN-1 MAIL. 2-2 Installing ALL-IN-1 MAIL for VMS $ @SYS$TEST:A1MAIL$VMS_IVP The IVP includes several tests, depending on which components have been installed. The following list describes the tests: _ Always run as part of the IVP: _ ALL-IN-1 MAIL Server for VMS test This is completely automatic, and does not require interaction with the user. _ Chose to install the programmer's kit: _ Callable interface test This is completely automatic, and does not require interaction with the user. _ Chose to install the command line interface: _ Command line interface test This is completely automatic, and does not require interaction with the user. _ Chose to install the DECwindows interface: _ DECwindows user interface test This test requires user interaction in order to complete. The information found in this section is also available as part of the IVP itself; information is displayed on the users terminal. This IVP will invoke ALL-IN-1 MAIL, but then you will have to create a message using the instruction file. To do this: 1 Click the CREATE-SEND button 2 From the CREATE-SEND window and the FILE pulldown menu, select INCLUDE FILE .... 3 Include the file A1MAIL$TEST:A1MAIL$DWVMS_IVP.TXT and follow the instructions in that file. This file, A1MAIL$DWVMS_IVP.TXT, contains the instructions to follow to run the ALL-IN-1 MAIL for VMS DECwindows Installation Verification Procedure (IVP) This is an interactive IVP, and requires you to follow these instructions. Installing ALL-IN-1 MAIL for VMS 2-3 If any of the operations fails, the IVP has failed, although the command file running this program cannot detect that. This message should appear in a CREATE-SEND window. 1 Address this message to yourself, by putting your USERNAME in the TO field. 2 Enter the subject: IVP test 3 Click the SEND button. _ Your username should expand to something similar to: USERNAME @AM @node _ A box should appear saying the message was sent, and asking you to acknowledge it. 4 Watch the A1MAIL Icon box; you should see the unopened count increment when the message arrives in your INBOX. 5 Return to the Index window and close and reopen the INBOX folder. 6 Double-click on the message you just sent, subject "IVP test". 7 This text should appear in the READ window. 8 From the READ window, select the FILE pulldown, EXTRACT.. option. 9 EXTRACT the message, without header, to : SYS$SCRATCH:A1MAIL$DWVMS_IVP.TMP Note that this name is important, as it is used in the automated part of this IVP. 10 Go to the INDEX window, FILE pulldown, and select EXIT. The automated section of this IVP will now run. 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 it has created up to that point and exits. You can then start the installation again. 2-4 Installing ALL-IN-1 MAIL for VMS The Installation Procedure The ALL-IN-1 MAIL for VMS installation process consists of a series of questions and informational messages. 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. You are strongly recommended to read the Release Notes before proceeding with this installation. VMSINSTAL has several other options; for information, see the VMS documentation on Software Installation. The following example displays the command to invoke VMSINSTAL to install ALL-IN-1 MAIL for VMS from tape drive MTA0: and the system responses. This example uses the OPTIONS N parameter for printing or displaying Release Notes. $ @SYS$UPDATE:VMSINSTAL A1MAIL010 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.1 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. Installing ALL-IN-1 MAIL for VMS 2-5 If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later on in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the Release Notes during the installation. Installation Questions This section discusses the questions that appear during the installation. See Appendix A for sample installation procedures. Each question 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 give the default response, press Return. 1 System backup. VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press Return. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 2 Mounting the media. You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing ALL-IN-1 MAIL for VMS has been mounted on the specified device and that the installation has begun. For example: 2-6 Installing ALL-IN-1 MAIL for VMS Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, A1MAIL MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: ALL-IN-1 MAIL for VMS Version 1.0 Beginning installation of ALL-IN-1 MAIL at 20:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press CTRL/Y. 3 Additional media volumes. If your installation kit contains more than one volume, VMSINSTAL prompts you to insert the additional volumes and then asks you to indicate that you are ready for the installation to proceed. %BACKUP-I-READYREAD, mount volume 2 on _MTA0: for reading Enter "YES" when ready: 4 Choosing to purge files. You have the option to purge files from previous versions of ALL-IN-1 MAIL for VMS that are superseded by this installation. * Do you want to purge files replaced by this installation [YES]?) 5 Choosing to run the Installation Verification Procedure (IVP). The installation procedure now asks if you want to run the Installation Verification Procedure. The IVP for ALL-IN-1 MAIL for VMS checks to be sure that the installation is successful. * Do you want to run the IVP after the installation [YES]? 6 Selecting the components from this kit to be installed. This installation allows you to choose several different pieces of the ALL-IN-1 MAIL product set. These choices include: _ ALL-IN-1 MAIL server for VMS Installing ALL-IN-1 MAIL for VMS 2-7 This is the backbone of the mail system, and must be either previously installed on the system, or installed as part of this installation. There is a VMS license required to run the server. _ ALL-IN-1 MAIL for VMS DECwindows This is the client that provides a DECwindows user interface to the mail functionality. This option requires that DECwindows be installed before it can be installed. There is a VMS license required to run the DECwindows client. _ ALL-IN-1 MAIL for DOS support This component provides the VMS files required to sup- port the ALL-IN-1 MAIL for DOS client. This component must be installed before the DOS client can work. _ ALL-IN-1 MAIL for Video Terminals This is the client that provides a command line interface to the mail functionality. There is a VMS license required to run the command line client. The following menu lists all the choices potentially 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 at this time as a comma-separated list (ie, "1,2,3") The installation guide has more details on these various components. 1) ALL-IN-1 MAIL Server for VMS 2) ALL-IN-1 MAIL for VMS DECwindows 3) ALL-IN-1 MAIL for DOS support 4) ALL-IN-1 MAIL for Video Terminals 5) All of the above * Choose installation options [5]: 5 7 The following are specific to the ALL-IN-1 MAIL server installation portion: _ Choosing to install the server programmer's kit. 2-8 Installing ALL-IN-1 MAIL for VMS This installation allows the installer to include the server programmer's kit as part of the server installation. It is not recommended that you install this option without prior arrangements with the development groups. Installing ALL-IN-1 MAIL for VMS 2-9 _ ALL-IN-1 MAIL library disk ALL-IN-1 MAIL creates a user-directory in which to keep miscellaneous files. This user directory contains common files, such as the header template files, registered editor files, and so on. There is also a subdirectory used to store files used by the ALL-IN-1 MAIL IVP. Please enter the name of a disk that can be used; the default given is SYS$SYSDEVICE. If ALL-IN-1 MAIL Server for VMS has previously been installed, this question is not asked. * ALL-IN-1 MAIL Library disk [SYS$SYSDEVICE]? _ License registration for server The installation procedure asks if you have registered and loaded your authorization key for the ALL-IN-1 MAIL for VMS server and prints out information specific to the particular license, for example: Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 1.0 Release Date: 26-FEB-1990 Specifically, the installation inquires: * Does this product have an authorization key registered and loaded? _ MUAS common disk This is the disk where the server-common files are stored. There will be much disk activity to this disk, as this is where the profile database is kept. * MUAS common disk [SYS$SYSDEVICE]: _ Informational message At this point, if ALL-IN-1 MAIL for VMS had not been installed before, you will receive the following informational message: 2-10 Installing ALL-IN-1 MAIL for VMS Please note that if the installation should fail for any reason, the system will not be completely restored to its original state. The server's working directory, the server's DISKQUOTA entry and the server's account, MUAS$SERVER may be left in place, and these must be deleted manually before attempting installation again. Installing ALL-IN-1 MAIL for VMS 2-11 _ Server UIC If ALL-IN-1 MAIL has not previously been installed, then you will be asked to enter a UIC for the MUAS$SERVER to use. *UIC to be used for MUAS$SERVER account in format [ggg,mmm]: _ Use of Message Router This next question asks if you wish to configure ALL- IN-1 MAIL so that it can use Message Router. If you choose not to configure the system so that it uses Message Router, then you cannot send mail off node, you cannot send mail to VMS Mail, and you cannot send mail to ALL-IN-1 Integrated Office System. * Configure to use Message Router [YES]? _ Message Router mailbox name This is the mailbox used for communication with Message Router. The default is AM, although you may use any other unused mailbox name. 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. * Message Router mailbox name [AM]: At this point, the installation checks whether this mailbox has already been created. You will see one of the following, depending on whether or not it is already in existence. This is MRMAN V3.1 %AM - No mailbox found or This is MRMAN V3. 1 X4, 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 reprompted for a different one. _ Configuration questions 2-12 Installing ALL-IN-1 MAIL for VMS There will be a dialog at this point to determine the configuration of your system. You will be asked for the values to describe a server, including its name, the node it will be running on, and the disk to use as its work area. There are some defaults presented to you, specifically for the server's name and the node for the first server. To end the set, press ^Z when asked for a server name. _ Server name. Press Return, or type in a different name. _ Server node. Press Return, or type in a node on which you wish to run a server. _ Disk for the server on this node. The default is SYS$SYSDEVICE. Either press return, or specify a different disk. It is recommended that you not use SYS$SYSDEVICE, because of the amount of disk I/O required to this disk. * Server name [000]: * Server node [node]: * Disk for this server [SYS$SYSDEVICE]: A1MAIL$DISK _ Local routing address The local routing address is used to create the return address on messages sent out, and is also used by the mail system to flag a local recipient, to make use of delivery optimizations. For most configurations, the local routing address will be: AM@YourNode However, if this installation is on a network supporting area codes, the local routing address will be of the form: AM@YourNode@YourArea Installing ALL-IN-1 MAIL for VMS 2-13 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]: _ Network character set If supplied, this attribute specified the conversion (between system character set and network character set) that will be applied to all text bodyparts as they enter or leave MAILbus. If you do specify a network character set name, the name must match a key in your system's national character set database. If you do not wish to supply a character set name press Return to enter a null string here. * Network Character Set (none): 2-14 Installing ALL-IN-1 MAIL for VMS _ Time offset The time offset is the difference between local time and network standard time. It must be entered in five characters, of the form ±HHMM. The first character must be + or -. HH is the hour difference, and MM is the minute difference. * Time offset [+0000]: _ Reporting MTA The Reporting MTA is the string added to reports generated by MUAS, for information only. The form of this string is "mta.MUAS" where "mta" is the cluster name (or node name if not clustered). * Reporting MTA [MYNODE.MUAS]: _ Compatibility with ALL-IN-1 Version 2.2 If your users will be sending messages to ALL-IN-1 Version 2.2 on a regular basis, you should answer YES to this question. The format of the messages is slightly altered, in order for ALL-IN-1 Version 2.2 to be able to read them without difficulty. Answer NO if you intend to send messages back and forth with ALL-IN-1 Version 2.2. * Run in ALL-IN-1 V2.2 compatibility mode [NO]? _ Message and event logging Answer YES if you wish MUAS to log each message transaction, sending or fetching, and each profile update. Answer NO if you do not wish to have all transactions logged. * Log all message and event transactions [NO]? 8 As part of the installation of the command line user interface, you will be asked the following questions: _ License registration The installation procedure asks if you have registered and loaded your authorization key for ALL-IN-1 MAIL for Video Terminals and prints out information specific to the particular license, for example: Installing ALL-IN-1 MAIL for VMS 2-15 Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 1.0 Release Date 26-FEB-1990 Specifically, the installation inquires: * Does this product have an authorization key registered and loaded? If you have not registered and loaded your autho- rization key, you must answer NO to this question. A successful installation of ALL-IN-1 MAIL for VMS depends upon an authorization key being registered and loaded. Please be sure this has been completed before proceeding with the installation. _ A warning if no DDIF support With some configurations of the VMS 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 a warning output now: !! 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 ALL-IN-1 MAIL. !! Note this also disables any request made to install the DECwindows User Interface. 9 As part of the DECwindows user interface installation, you will be asked the following questions: _ License Registration 2-16 Installing ALL-IN-1 MAIL for VMS The installation procedure asks if you have registered and loaded your authorization key for ALL-IN-1 MAIL for VMS DECwindows and prints out information specific to the particular license, for example: Product: ALLIN1-MAIL-DW-CLIENT Producer: DEC Version: 1.0 Release Date: 26-FEB-1990 Specifically, the installation inquires: * Does this product have an authorization key registered and loaded? If you have not registered and loaded your authoriza- tion 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. Installing ALL-IN-1 MAIL for VMS 2-17 10 End of questions This is the end of the questions asked by the installa- tion. You will see a notice to this effect, followed by many informational messages described in the following section. On a MicroVAX II, the rest of the installation takes from 5 to 45 minutes, depending on how many components you requested to install. The number specified in the informational message reflects an estimate based on the components being installed. This is the end of the questions that are asked by this installation The rest of the installation will take about 37 minutes on a MicroVax II class machine Informational Messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. These include, but are not limited to: Checking for running ALL-IN-1 Mail servers ... Checking for queued ALL-IN-1 Mail server-restart jobs... !! Deleting restart-job #844 in queue MUAS$BATCH_BABYLN %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %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: [000006,000002] added to RIGHTSLIST.DAT %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUAS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %A1MAIL-I-DISKQUOTA, This installation creates a DISKQUOTA entry for MUAS$SERVER 2-18 Installing ALL-IN-1 MAIL for VMS %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named MUAS$PROFILE_UPDATE. %UAF-I-RDBADDMSG, identifier MUAS$PROFILE_UPDATE value: %X8001000B added to RIGHTSLIST.DAT This is MRMAN V3.1 AM,Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages This is MRMAN V3.1 %Added AM,Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.MUAS]. Installing ALL-IN-1 MAIL for VMS 2-19 +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM. | | | | 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. | +----------------------------------------------------------------------+ If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you asked for files to be purged, that work is done now. The following messages are displayed: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 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 usernames will be different): Starting IVP for ALL-IN-1 MAIL V1.0 Starting server test. Starting user agent test; VT interface. NOTE: This IVP will change the current user's A1MAIL user profile as follows: CORRELATE is set to Yes AUTO_PURGE is set to No Setting profile attributes. ALL-IN-1 Mailing message to self. Pausing 20 seconds for message delivery. New ALL-IN-1 MAIL message on node MYNODE from SYSTEM@AM@MYNODE "SYSTEM" (14-DEC-1989 12:57:54.28) New ALL-IN-1 MAIL delivery/receipt report on node MYNODE for SYSTEM@AM@MYNODE "SYSTEM" (14-DEC-1989 12:58:07.90) Generating IVP output file. Checking IVP output file. 2-20 Installing ALL-IN-1 MAIL for VMS Starting IVP for ALL-IN-1 MAIL for VMS DECwindows Window output to which node? (Press Return to cancel): IVP for ALL-IN-1 MAIL for VMS DECwindows cancelled ALL-IN-1 MAIL V1.0 IVP completed successfully. Installation of A1MAIL V1.0 completed at 12:59 Completing the Installation Procedure The following messages indicate the entire installation procedure is complete: Installation of A1MAIL V1.0 completed at 13:57 VMSINSTAL procedure done at 13:58 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. Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ALL-IN-1 MAIL for VMS Version 1.0 has failed. If the IVP fails, the following messages are displayed: ALL-IN-1 MAIL IVP failed. %VMSINSTAL-E-IVPFAIL, The IVP for ALL-IN-1 MAIL for VMS Version 1.0 has failed. Errors can occur during the installation if any of the following conditions exist: _ The operating system version is incorrect. _ The product is not properly licensed. _ The IVP may fail if: _ MUAS$SERVER_nnn fails to start up. Installing ALL-IN-1 MAIL for VMS 2-21 3 ________________________________________________________________ After Installing ALL-IN-1 MAIL for VMS After installing ALL-IN-1 MAIL, you need to perform the following tasks: _ Edit the system startup to include @SYS$STARTUP:A1MAIL$STARTUP. _ Set user account quotas. User Account Requirements To use ALL-IN-1 MAIL for VMS, user accounts on your system must have certain quotas. Table 3-1 summarizes the required user account quotas. Table 3-1 User Account Quotas _____________________________________________________________ Account_Quota____Value_______________________________________ FILLM 70 PRCLM____________3___________________________________________ 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> After Installing ALL-IN-1 MAIL for VMS 3-1 At the AUTHORIZE prompt (UAF>), use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH 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=70 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not 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. For more information on modifying account quotas, see the description of the Authorize Utility in the VMS documentation on System Management and Operations. 3-2 After Installing ALL-IN-1 MAIL for VMS 4 ________________________________________________________________ Installing ALL-IN-1 MAIL Client for DOS This chapter describes how to install the ALL-IN-1 MAIL Client for DOS as a disk service under PCSA. It is not necessary to perform this installation if you are not going to be connecting MS-DOS clients to your VAX. It is also not necessary if all of the MS-DOS software is going to be installed on the individual PC hard disks. This procedure creates a PCSA disk service called A1MAIL$DOS_ V10. Users who wish to use the software on their PCs can establish a PCSA connection to this disk service. Prerequisite and Optional Software This section discusses the software you must have installed on your system before installing ALL-IN-1 MAIL Client for DOS. 1 PCSA Disk Server V3.0 2 ALL-IN-1 MAIL for VMS Version 1.0. When ALL-IN-1 MAIL for VMS is installed, the ALL-IN-1 MAIL Client for DOS support installation option must be chosen or ALL-IN-1 MAIL Client for DOS cannot be run. Prerequisite Hardware In order to be able to use ALL-IN-1 MAIL Client for DOS as a disk service, the PC and the VAX must be connected to the same logical Ethernet. Note that there may be one or more Ethernet bridges between the VAX and the PC. Installing ALL-IN-1 MAIL Client for DOS 4-1 Time This procedure should require approximately 10 minutes on a MicroVAX II. The time may differ depending on your system configuration. Of this time, only about five minutes should be required to answer all of the questions. Privileges To install ALL-IN-1 MAIL Client for DOS, you must be logged in to an account that has least the following privileges authorized: _ WORLD _ CMKRNL _ SYSPRV _ OPER Disk Space Installing ALL-IN-1 MAIL Client for DOS requires 4,100 blocks of disk space. Once ALL-IN-1 MAIL Client for DOS is installed, it will require 4,000 blocks of disk space. Please note that disk space requirements are approximate. Files Added to the System The installation procedure for ALL-IN-1 MAIL Client for DOS adds one file to the system: A1MAIL$DOS_V10.DSK. This file is a PCSA disk container file that contains all the files necessary to run ALL-IN-1 MAIL Client for DOS from the PC. By default, this file is placed in LAD$APPLICATION_DISKS. This location may be overridden at installation time. The A1MAIL$DOS_V10 disk service is added as a permanently registered disk service in PCSA. This means that it will not need to be explicitly mounted each time the LAD$KERNEL is started. The A1MAIL$DOS_V10 service will be mounted as part of the installation procedure. Note This disk service is not mounted with the /CLUSTER switch. It must be explicitly added to each node on the cluster where you would like the disk service to be available. 4-2 Installing ALL-IN-1 MAIL Client for DOS 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 A1MDOS device-name A1MDOS 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. VMSINSTAL has several other options; for information, see the VMS documentation on software installation. The following example displays the command to invoke VMSINSTAL to install ALL-IN-1 MAIL Client for DOS from tape drive MTA0: and the system responses. $ @SYS$UPDATE:VMSINSTAL A1MDOS010 MTA0: VAX/VMS Software Product Installation Procedure V5.1 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 on in the installation procedure. Installation Questions This section discusses the questions that appear during the installation. See Sample Installation of ALL-IN-1 MAIL Client for DOS for a sample installation procedure. Each question 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 give the default response, press Return. Installing ALL-IN-1 MAIL Client for DOS 4-3 1 System backup VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press Return.. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 4-4 Installing ALL-IN-1 MAIL Client for DOS 2 Mounting the media You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing ALL-IN-1 MAIL for VMS has been mounted on the specified device and that the installation has begun. For example: Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, A1MDOS MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: ALL-IN-1 MAIL Client for DOS V1.0 Beginning installation of ALL-IN-1 MAIL Client for DOS at 20:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press CTRL/Y. 3 File location The installation procedure will ask where you want to place the PCSA disk service container file. By default, this will be in the location specified by the logical LAD$APPLICATION_DISKS. You may override this with another location if you desire. * Enter the device and directory for A1MAIL$DOS_V10 * [SYS$SYSDEVICE:[PCSA.LAD]]: 4 Choosing to purge files You have the option to purge files from previous versions of ALL-IN-1 MAIL Client for DOS that are superseded by this installation. * Do you want to purge files replaced by this installation [YES]? 5 End of questions Installing ALL-IN-1 MAIL Client for DOS 4-5 This is the end of the questions asked by the instal- lation. You will see a notice to this effect, followed by many informational messages described in the next section. On a MicroVAX II, the rest of the installation takes anywhere from 5 to 10 minutes. This is the end of the questions that are asked by this installation. The rest of the installation will take about 10 minutes on a MicroVax II class machine. Informational Messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. These include, but are not limited to: %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %VMSINSTAL-I-SYSDIR, This installation creates system disk directory SYS$SYSDEVICE:[PCSA.LAD] %CREATE-I-EXISTS, SYS$SYSDEVICE:[PCSA.LAD] already exists %PCSA-I-DISKMOUNTED, SYS$SYSDEVICE:[PCSA.LAD]X400$DOS_V10.DSK;1 mounted %PCSA-I-MOUNTINFO, service name = X400$DOS_V10, server node = MYNODE If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you asked for files to be purged, that work is done now. The following messages are displayed: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... Completing the Installation Procedure The following messages indicate the entire installation procedure is complete: Installation of A1MDOS V1.0 completed at 13:57 VMSINSTAL procedure done at 13:58 You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 19-DEC-1989 13:59:00.01 4-6 Installing ALL-IN-1 MAIL Client for DOS 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. Error Recovery If errors occur during the installation, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ALL-IN-1 MAIL for VMS Version 1.0 has failed. Installing ALL-IN-1 MAIL Client for DOS 4-7 A ________________________________________________________________ Sample ALL-IN-1 MAIL Installations This appendix contains sample installations of ALL-IN-1 MAIL for VMS. The first sample was run on a system that had no previous version of ALL-IN-1 MAIL installed. The second was run on a system that had had a previous version of ALL-IN-1 MAIL for VMS on it. The third sample installation is of the ALL-IN-1 MAIL for VMS DECwindows component only. The fourth sample is of the ALL-IN-1 MAIL Client for DOS installation. Full New Installation The following is an example of an installation on a system that did not have. ALL-IN-1 MAIL installed on it before. $ @SYS$UPDATE:VMSINSTAL A1MAIL DISK1:[GROUP.KITS] VAX/VMS Software Product Installation Procedure V5.2 It is 24-NOV-1989 at 16:06. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER MR$T_N_1 RSM$BKPSCAN * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: A1MAIL V1.0 Beginning installation of A1MAIL V1.0 at 16:07 Sample ALL-IN-1 MAIL Installations A-1 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. +----------------------------------------------+ | Installing ALL-IN-1 Mail for VMS V1.0 | | X400 MAIL product | +----------------------------------------------+ * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? The following menu lists all the choices potentially 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 at this time as a comma-separated list (ie, "1,2,3") The installation guide has more details on these various components. 1) ALL-IN-1 MAIL Server for VMS 2) ALL-IN-1 MAIL for VMS DECwindows 3) ALL-IN-1 MAIL for DOS support 4) ALL-IN-1 MAIL for Video Terminals 5) All of the above * Choose installation options [5]: 5 * Install the server programmer's kit [NO]? n Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 010 Release Date: 26-FEB-1990 * Does this product have an authorization key registered and loaded? y * MUAS common disk [SYS$SYSDEVICE]: DISK$USER1 Please note that if the installation should fail for any reason, the system will not be completely restored to its original state. The server's working directory, the server's DISKQUOTA entry and the server's account, MUAS$SERVER may be left in place, and these must be deleted manually before attempting installation again. A-2 Sample ALL-IN-1 MAIL Installations * UIC to be used for MUAS$SERVER account in format [ggg,mmm]: [275,1] * Configure MUAS to use Message Router [YES]? * Message Router mailbox name [AM]: 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]? 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. Terminate the list of servers by entering a ^Z (CTRL-Z). * Server name [000]: * Server node [MYNODE]: * Disk for this server [SYS$SYSDEVICE]: disk$user1 * Server name [001]: ^Z Cluster configuration is now complete. Note that if you want to alter the MUAS system configuration after installation, use the interactive CONfiguration MANagement command file MUAS$CONMAN.COM, as described in the release notes. * Local routing address [AM@MYNODE]: * Network Character Set (none): * Time offset [+0000]: * Reporting MTA [MYNODE.MUAS]: * Run in ALL-IN-1 V2.2 compatibility mode [NO]? y * Log all message and event transactions [NO]? Checking license for command line interface Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 010 Release Date: 26-FEB-1990 * Does this product have an authorization key registered and loaded? y Checking license for DECwindows interface Product: ALLIN1-MAIL-DW-CLIENT Producer: DEC Version: 010 Release Date: 26-FEB-1990 Sample ALL-IN-1 MAIL Installations A-3 * Does this product have an authorization key registered and loaded? y This is the end of the questions that are asked by this installation The rest of the installation will take about 36 minutes on a MicroVax II class machine %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %VMSINSTAL-I-RESTORE, Restoring product saveset C ... %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: [000275,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named MUAS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %A1MAIL-I-DISKQUOTA, This installation creates a DISKQUOTA entry for MUAS$SERVER %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named MUAS$PROFILE_UPDATE. %UAF-I-RDBADDMSG, identifier MUAS$PROFILE_UPDATE value: %X80010009 added to rights data base This is MRMAN V3.1 AM, Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages This is MRMAN V3.1 %Added AM, Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages %VMSINSTAL-I-RESTORE, Restoring product saveset D ... +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM. | | | | 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. | +----------------------------------------------------------------------+ %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting ALL-IN-1 MAIL A-4 Sample ALL-IN-1 MAIL Installations Job MUAS$NODE_CHECK (queue MUAS$BATCH_MYNODE, entry 470) started on MUAS$BATCH_MYNODE Starting IVP for ALL-IN-1 MAIL V1.0 Starting server test. Starting the MUAS V1.0 Installation Verification Procedure IVP for MUAS V1.0 callable interface completed successfully Input now being taken from muas$svr_ivp_temp.dat PRFUPD (We have update access to the profile) = ON OWNPRF (We don't have a profile entry but may create one) = ON SUBMIT (We may submit messages) = OFF Local route is X4@MYNODE@AD Time offset is -0500 MDL successful completion IVP for MUAS V1.0 server completed successfully MUAS V1.0 Installation Verification Procedure completed The MUAS V1.0 Installation Verification Procedure (IVP) has been provided in SYS$COMMON:[SYSTEST]. The MUAS V1.0 IVP may be invoked at any time by using the following command: @SYS$TEST:MUAS$IVP. Starting user agent test; VT interface. NOTE: This IVP will change the current user's A1MAIL user profile as follows: CORRELATE is set to Yes AUTO_PURGE is set to No Setting profile attributes. Mailing message to self. Pausing 20 seconds for message delivery. New ALL-IN-1 MAIL message on node MYNODE from SYSTEM@AM@MYNODE "SYSTEM" (14-DEC-1989 12:57:54.28) New ALL-IN-1 MAIL delivery/receipt report on node MYNODE for SYSTEM@AM@MYNODE "SYSTEM" (14-DEC-1989 12:58:07.90) Generating IVP output file. Checking IVP output file. Starting IVP for ALL-IN-1 MAIL for VMS DECwindows Sample ALL-IN-1 MAIL Installations A-5 Window output to which node? (Press Return to cancel): IVP for ALL-IN-1 MAIL for VMS DECwindows cancelled ALL-IN-1 MAIL V1.0 IVP completed successfully. VMSINSTAL procedure done at 16:24 Full Upgrade Installation This section contains a sample installation for ALL-IN-1 MAIL for VMS Version 1.0 on a system that did have a previous in- stallation of ALL-IN-1 MAIL. This upgrade installation is on a system that has suppport for DDIF and DECwindows. VAX/VMS Software Product Installation Procedure V5.3 It is 14-DEC-1989 at 12:48. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER MR$T_N_4 MRLISTEN_16389 FAL_36155 * Do you want to continue anyway [NO]? Y * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: GROUP$KITS: Enter the products to be processed from the first distribution volume set. * Products: A1MAIL * Enter installation options you wish to use (none): The following products will be processed: A1MAIL V1.0 Beginning installation of A1MAIL V1.0 at 12:49 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. +----------------------------------------------+ | Installing ALL-IN-1 Mail for VMS V1.0 | | X400 MAIL product | +----------------------------------------------+ A-6 Sample ALL-IN-1 MAIL Installations * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? The following menu lists all the choices potentially 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 at this time as a comma-separated list (ie, "1,2,3") The installation guide has more details on these various components. 1) ALL-IN-1 MAIL Server for VMS 2) ALL-IN-1 MAIL for VMS DECwindows 3) ALL-IN-1 MAIL for DOS support 4) ALL-IN-1 MAIL for Video Terminals 5) All of the above * Choose installation options [5]: * Install the server programmer's kit [NO]? No Checking license for server Product: ALLIN1-MAIL-SERVER Producer: DEC Version: 010 Release Date: 26-FEB-1990 * Does this product have an authorization key registered and loaded? Y * MUAS common disk [DISK6$]: * Configure to use Message Router [YES]? * Message Router mailbox name [AM]: 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]? 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. Terminate the list of servers by entering a ^Z (CTRL-Z). Sample ALL-IN-1 MAIL Installations A-7 * Server name [000]: * Server node [NODEC]: * Disk for this server [SYS$SYSDEVICE]: USER6$ * Server name [001]: * Server node: URNODE * Disk for this server [SYS$SYSDEVICE]: USER6$ * Server name [002]: ^Z ALL-IN-1 MAIL system configuration is now complete. Note that if you want to alter the system configuration after installation, use the X4MAN utility as described in the System Manager's Guide to the ALL-IN-1 MAIL server. * Local routing address [AM@NODEC]: AM@NODEC@USA * Network Character Set (none): * Time offset [+0000]: -0500 * Reporting MTA [NODEC.MUAS]: * Run in ALL-IN-1 V2.2 compatibility mode [NO]? * Log all message and event transactions [NO]? YES Checking license for command line interface Product: ALLIN1-MAIL-VT-CLIENT Producer: DEC Version: 010 Release Date: 26-FEB-1990 * Does this product have an authorization key registered and loaded? Y Checking license for DECwindows interface Product: ALLIN1-MAIL-DW-CLIENT Producer: DEC Version: 010 Release Date: 26-FEB-1990 * Does this product have an authorization key registered and loaded? Y This is the end of the questions that are asked by this installation The rest of the installation will take about 34 minutes on a MicroVax II class machine A-8 Sample ALL-IN-1 MAIL Installations %VMSINSTAL-I-RESTORE, Restoring product save set B ... Checking for running ALL-IN-1 MAIL servers on NODEA... Checking for queued ALL-IN-1 Mail server-restart jobs... !! Deleting restart-job #239 in queue MUAS$BATCH_NODEA Checking for running ALL-IN-1 MAIL servers on NODEC ... Checking for queued ALL-IN-1 Mail server-restart jobs... Checking for running ALL-IN-1 MAIL servers on NODEB... Checking for queued ALL-IN-1 Mail server-restart jobs... This is MRMAN V3.1 AM, Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages This is MRMAN V3.1 %Added AM, Owner=SYSTEM Notify=MUAS$NOTIF_FETCH_MBX Suppress_Delivery_Reports Probes_Relayed Complete_Messages Ignore_Sender Service_Messages %VMSINSTAL-I-RESTORE, Restoring product save set D ... +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM. | | | | 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. | +----------------------------------------------------------------------+ Creating profile templates ... Starting ALL-IN-1 MAIL Job MUAS$NODE_CHECK (queue MUAS$BATCH_NODEC, entry 272) started on MUAS$BATCH_NODEC %RUN-S-PROC_ID, identification of created process is 43A0044B Starting IVP for ALL-IN-1 MAIL V1.0 Starting server test. Starting the MUAS V1.0 Installation Verification Procedure IVP for MUAS V1.0 callable interface completed successfully Input now being taken from muas$svr_ivp_temp.dat Sample ALL-IN-1 MAIL Installations A-9 PRFUPD (We have update access to the profile) = ON OWNPRF (We don't have a profile entry but may create one) = ON SUBMIT (We may submit messages) = OFF Local route is AM@MYNODE@AD Time offset is -0500 MDL successful completion IVP for MUAS V1.0 server completed successfully MUAS V1.0 Installation Verification Procedure completed The MUAS V1.0 Installation Verification Procedure (IVP) has been provided in SYS$COMMON:[SYSTEST]. The MUAS V1.0 IVP may be invoked at any time by using the following command: @SYS$TEST:MUAS$IVP. Starting user agent test; VT interface. NOTE: This IVP will change the current user's A1MAIL user profile as follows: CORRELATE is set to Yes AUTO_PURGE is set to No Setting profile attributes. Mailing message to self. Pausing 20 seconds for message delivery. New ALL-IN-1 MAIL message on node MYNODE from SYSTEM@AM@MYNODE "SYSTEM" (14-DEC-1989 12:57:54.28) New ALL-IN-1 MAIL delivery/receipt report on node MYNODE for SYSTEM@AM@MYNODE "SYSTEM" (14-DEC-1989 12:58:07.90) Generating IVP output file. Checking IVP output file. Starting IVP for ALL-IN-1 MAIL for VMS DECwindows Window output to which node? (Press Return to cancel): IVP for ALL-IN-1 MAIL for VMS DECwindows cancelled ALL-IN-1 MAIL V1.0 IVP completed successfully. Installation of A1MAIL V1.0 completed at 13:31 A-10 Sample ALL-IN-1 MAIL Installations Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 13:32 ALL-IN-1 MAIL for VMS DECwindows Client-only Installation This section illustrates an installation of only the ALL-IN-1 MAIL for VMS DECwindows component. ALL-IN-1 MAIL Server for VMS has been previously installed. VAX/VMS Software Product Installation Procedure V5.3 It is 14-DEC-1989 at 12:48. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER MR$T_N_4 MRLISTEN_16389 FAL_36155 * Do you want to continue anyway [NO]? Y * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: GROUP$KITS: Enter the products to be processed from the first distribution volume set. * Products: A1MAIL * Enter installation options you wish to use (none): The following products will be processed: A1MAIL V1.0 Beginning installation of A1MAIL V1.0 at 12:49 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. +----------------------------------------------+ | Installing ALL-IN-1 Mail for VMS V1.0 | | X400 MAIL product | +----------------------------------------------+ * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? The following menu lists all the choices potentially available through this installation. The server must have been installed on the system previously, or you must choose it now. Sample ALL-IN-1 MAIL Installations A-11 Enter the components that you wish to install at this time as a comma-separated list (ie, "1,2,3") The installation guide has more details on these various components. 1) ALL-IN-1 MAIL Server for VMS 2) ALL-IN-1 MAIL for VMS DECwindows 3) ALL-IN-1 MAIL for DOS support 4) ALL-IN-1 MAIL for Video Terminals 5) All of the above * Choose installation options [5]: 2 Checking license for DECwindows interface Product: ALLIN1-MAIL-DW-CLIENT Producer: DEC Version: 010 Release Date: 26-FEB-1990 * Does this product have an authorization key registered and loaded? Y This is the end of the questions that are asked by this installation The rest of the installation will take about 7 minutes on a MicroVax II class machine %VMSINSTAL-I-RESTORE, Restoring product save set D ... +----------------------------------------------------------------------+ | When the installation completes, remember to modify your system | | startup procedure to execute SYS$STARTUP:A1MAIL$STARTUP.COM. | | | | 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 IVP for ALL-IN-1 MAIL V1.0 Starting server test. Starting the MUAS V1.0 Installation Verification Procedure IVP for MUAS V1.0 callable interface completed successfully Input now being taken from muas$svr_ivp_temp.dat A-12 Sample ALL-IN-1 MAIL Installations PRFUPD (We have update access to the profile) = ON OWNPRF (We don't have a profile entry but may create one) = ON SUBMIT (We may submit messages) = OFF Local route is AM@MYNODE@AD Time offset is -0500 MDL successful completion IVP for MUAS V1.0 server completed successfully MUAS V1.0 Installation Verification Procedure completed The MUAS V1.0 Installation Verification Procedure (IVP) has been provided in SYS$COMMON:[SYSTEST]. The MUAS V1.0 IVP may be invoked at any time by using the following command: @SYS$TEST:MUAS$IVP. Starting IVP for ALL-IN-1 MAIL for VMS DECwindows Window output to which node? (Hit RETURN to cancel): MYVSII Checking IVP output file ALL-IN-1 MAIL V1.0 IVP completed successfully. Installation of A1MAIL V1.0 completed at 13:31 Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 13:32 Sample Installation of ALL-IN-1 MAIL Client for DOS This section contains a sample installation of ALL-IN-1 MAIL Client for DOS on a system that did not have ALL-IN-1 MAIL Client for DOS installed on it before. $ @sys$update:vmsinstal a1mdos010 dua1:[kit] VAX/VMS Software Product Installation Procedure V5.3 It is 25-JAN-1990 at 18:50. Enter a question mark (?) at any time for help. Sample ALL-IN-1 MAIL Installations A-13 %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER MR$T_N_1 MUAS$SERVER_000 * 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: A1MDOS V1.0 Beginning installation of A1MDOS V1.0 at 18:50 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... * Enter the device and directory for A1MAIL$DOS_V10 * [SYS$SYSDEVICE:[PCSA.LAD]]: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PCSA.LAD]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[PCSA.LAD] already exists Installing A1MAIL$DOS_V10 to SYS$SYSDEVICE:[PCSA.LAD]. It will take approximately 5 minutes. Installation may continue unattended. %PCSA-I-DISKMOUNTED, SYS$SYSDEVICE:[PCSA.LAD]A1MAIL$DOS_V10.DSK;1 mounted %PCSA-I-MOUNTINFO, service name = A1MAIL$DOS_V10, server node = MYNODE The VMSINSTAL procedure is complete. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of A1MDOS V1.0 completed at 18:53 VMSINSTAL procedure done at 18:54 A-14 Sample ALL-IN-1 MAIL Installations B ________________________________________________________________ Files and Logical Names Installed on Your System The ALL-IN-1 MAIL for VMS Version 1.0 installation procedure installs a number of files on your system and defines some logical names. Table B-1 lists the files installed, and Logical Names lists the logical names that are added to the system logical name table. The following table contains the names of files that are always installed on your system when ALL-IN-1 MAIL for VMS Version 1.0 is installed. Table B-1 Files Installed During Installation ________________________________________________________________ Directory_____________File_Names________________________________ Common_Files____________________________________________________ SYS$HELP A1MAIL010.RELEASE_NOTES SYS$TEST A1MAIL$VMS_IVP.COM SYS$MESSAGE A1MAIL$MESSAGES.EXE A1MAIL$LIBRARY A1MAIL$INSTALL_IMAGES.COM A1MAIL$LANGUAGES.DAT A1MAIL$SET_LOCAL_ROUTING_ADDRESS.COM A1MAIL$SET_SERVER_LIST.COM (continued on next page) Files and Logical Names Installed on Your System B-1 Table B-1 (Cont.) Files Installed During Installation ________________________________________________________________ Directory_____________File_Names________________________________ Common_Files____________________________________________________ A1MAIL$SET_TIME_OFFSET.COM A1MAIL$SHOW_UNOPENED.EXE A1MAIL$SSI_MESSAGES.MSG A1MAIL$LIBRARY:[.ENGLIA1MAIL$READ_HEADER.TXT A1MAIL$REGISTERED_EDITORS.TXT A1MAIL$SHOW_HEADER.TXT A1MAIL$ALL-IN-1_HEADER.TXT A1MAIL$ADDRESS_TEMPLATE.DAT A1MAIL$KEYWORDS.DAT ________________________________________________________________ ALL-IN-1 MAIL for VT files___________________________________________________________ SYS$SYSTEM A1MAIL$CCT_MAIL.EXE SYS$HELP A1MAIL$CCT_HELP.HLB SYS$TEST A1MAIL$VTVMS_IVP.COM (continued on next page) B-2 Files and Logical Names Installed on Your System Table B-1 (Cont.) Files Installed During Installation ________________________________________________________________ ________________________________________________________________ ALL-IN-1_MAIL_Server_basic_components___________________________ SYS$STARTUP A1MAIL$STARTUP.COM MUAS$STARTUP.COM SYS$SYSTEM MUAS$SERVER.EXE MUAS$SERVER_LOGIN.COM MUAS$SUBPROC.EXE X400MAN.EXE SYS$SHARE A1MAIL$SHARE.EXE DSL$SHR.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 MUAS$CLIENT_MSG.EXE MUAS$SERVER_MSG.EXE (continued on next page) Files and Logical Names Installed on Your System B-3 Table B-1 (Cont.) Files Installed During Installation ________________________________________________________________ Directory_____________File_Names________________________________ ALL-IN-1_MAIL_Server_basic_components___________________________ SYS$TEST MUAS$IVP.COM SYS$TEST:[.MUAS] MUAS$CIV_IVP_TEMPLATE.DAT MUAS$CIV_IVP_TEMPLATE.DUMP MUAS$CIV_IVP_TEMPLATE.TXT A1MAIL$LIBRARY 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 (continued on next page) B-4 Files and Logical Names Installed on Your System Table B-1 (Cont.) Files Installed During Installation ________________________________________________________________ Directory_____________File_Names________________________________ ALL-IN-1_MAIL_Server_basic_components___________________________ [MUAS$SERVER.COM] MUAS$CREATE_DIRECTORY.COM MUAS$DELETE_DIRECTORY.COM MUAS$CREATE_SEMANTIC_TABLES.COM MUAS$NODE_CHECK.COM MUAS$SERVER_INPUT.INP MUAS$STARTUP_SERVER_nnn.DAT MUAS$TIDY.COM [MUAS$SERVER.DB] COUNTER_FILENAME_nnn.DAT MUAS$PROFILE.DAT MUAS$PROFILE.FDL MUAS$SYSTEM_CONFIG.DAT MUAS$SYSTEM_CONFIG.FDL MUAS$SUBSTITUTE_BODY.DDIF MUAS$SUBSTITUTE_BODY.TEXT MUAS$WPLDEF.FDL (continued on next page) Files and Logical Names Installed on Your System B-5 Table B-1 (Cont.) Files Installed During Installation ________________________________________________________________ ________________________________________________________________ ALL-IN-1_MAIL_Server_Programmers_kit_components_________________ SYS$LIBRARY MUAS$DEFINITIONS.H MUAS$SSI_DEFNIITIONS.H MUAS$SERVER_MSG.H SYS$MESSAGE MUAS$CLIENT_MSG.OBJ MUAS$SERVER_MSG.OBJ [MUAS$SERVER.COM] MUAS$CONMAN.COM [MUAS$SERVER.TOOLS] MUAS$EXAMPLE_PRF MUAS$MF_CONNECT.EXE MUAS$MF_LOAD.EXE MUAS$MF_DUMP.EXE MUAS$MF_SUBMIT.EXE MUAS$MF_TAIL.EXE MUAS$SERVER_DEBUG.EXE MUAS$TOOLSLIB.OLB MUAS$UA0.EXE MUAS$USEFUL_DEFINES.COM [MUAS$SERVER.COM] MUAS$COMMON_STARTUP.DAT MUAS$SERVER_SYSTEM_STARTUP.COM (continued on next page) B-6 Files and Logical Names Installed on Your System Table B-1 (Cont.) Files Installed During Installation ________________________________________________________________ Directory_____________File_Names________________________________ ALL-IN-1_MAIL_for_VMS_DECwindows_files__________________________ SYS$SYSTEM A1MAIL$DW_MAIL.EXE A1MAIL$DW_CREATEDECTERM.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 A1MAIL$DW_READ.UID A1MAIL$DW_SEND.UID A1MAIL$DW_WASTE.UID SYS$TEST A1MAIL$DWVMS_IVP.COM SYS$HELP A1MAIL$DW_HELP.HLB ________________________________________________________________ ALL-IN-1_MAIL_for_DOS_support___________________________________ SYS$STARTUP A1MAIL$CONNECT_STARTUP.COM SYS$SYSTEM A1MAIL$CONNECT.EXE SYS$LIBRARY___________A1MAILDOSSHR.EXE__________________________ Files and Logical Names Installed on Your System B-7 Logical Names The following logical names are entered into the system logical name tables when ALL-IN-1 MAIL for VMS 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_______________Translation________Description____________ A1MAIL$BROADCAST variable List of clients (other than VMS) that support new mail broadcasting. A1MAIL$DEFAULT_ English Used in multi-lingual LANGUAGE installations as the system default language. A1MAIL$INTERNAL_ not defined Used as a debugging TRACE aid. A1MAIL$LANGUAGE_xx variable Used in multi-lingual installations for processing error messages. (continued on next page) B-8 Files and Logical Names Installed on Your System Table B-2 (Cont.) System-wide Logical Names ________________________________________________________________ Logical_______________Translation________Description____________ A1MAIL$LIBRARY (disk_entered):[A1MAIL$LIBRARY] Library of common utilities, management data, and so on. A1MAIL$LOCAL_ Local Routing Used during address ROUTING_ADDRESS Address verification. A1MAIL$SERVER_LIST List of nodes Used when connecting running enabled to send mail, update MUAS$SERVERs. profile. A1MAIL$TEST (disk_entered):[A1MAIL$LIBRARY.TEST] Used during IVP, and also when A1MAIL$INTERNAL_TRACE is set. A1MAIL$TIME_OFFSET variable Local offset from Network Standard Time. MUAS$TOOLS (disk_entered):[MUAS$SERVER.TOOLS] Used by MUAS$SERVER to store its common utilities, and so on. MUAS$COMMON (disk_entered):[MUAS$SERVER] Top level directory used by MUAS$SERVER, where profile, configuration, and so on are stored. (continued on next page) Files and Logical Names Installed on Your System B-9 Table B-2 (Cont.) System-wide Logical Names ________________________________________________________________ Logical_______________Translation________Description____________ MUAS$SERVER_OBJECT 84 DECnet Object ID used _________________________________________for_network_operations. Table B-3 Command Files Used During Startup ________________________________________________________________ Directory_______Command_file___________Description______________ A1MAIL$LIBRARY: A1MAIL$SET_SERVER_ Defines logical LIST A1MAIL$SERVER_LIST. A1MAIL$SET_LOCAL_ROUTING_ADDRESS Defines logical A1MAIL$LOCAL_ROUTING_ ADDRESS. A1MAIL$INSTALL_IMAGES Installs all images required to run ALL- IN-MAIL for VMS. A1MAIL$DW_EDIT Used to invoke spawnable editors from ALL-IN-1 MAIL for VMS DECwindows. [MUAS$SERVER.COMA1MAIL$COMMON_ Used as input to start up STARTUP.DAT MUAS$SERVER. (continued on next page) B-10 Files and Logical Names Installed on Your System Table B-3 (Cont.) Command Files Used During Startup ________________________________________________________________ ________________________________________________________________ Used_by_X4MAN___________________________________________________ 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 X4MAN. X400MAN$GET_LIST_OF_TEMP_SERVERS.COM Used by X4MAN. X400MAN$RELEASE_NODE_CHECK.COM Used by X4MAN. X400MAN$REM_SRV_SHUTDOWN.COM Used by X4MAN. X400MAN$REM_SRV_STARTUP.COM Used by X4MAN. X400MAN$GET_REMOTE_SERVER.COM _______________________________________Used_by_X4MAN.___________ [element-or-template]... Files and Logical Names Installed on Your System B-11