MX uses VMSINSTAL for installation. If you do not know how to use VMSINSTAL, you should first read the chapter on installing software in the (VMS System Manager's Manual). For the installation, you should be logged into the SYSTEM account, or another suitably privileged account. MX (must) be installed (multiple times) on a mixed-architecture VMScluster: once per architecture. The first installation will also provide the architecture-independent files. When installing on a mixed VMScluster, be sure to specify a device name for the MX installation directory that is valid for all systems in the cluster, and refers to the same device in all cases. Using a platform-specific logical name, such as SYS$SYSDEVICE, will cause subsequent installations to fail. (Shutting down MX\INSTALL_GUIDE_13)

If any MX processes are currently running, you should stop them before installing a new version of MX. Unprocessed mail should remain queued until you start the new MX processes. (Invoking VMSINSTAL\INSTALL_GUIDE_14)

Invoke VMSINSTAL to install MX. ($ )(@SYS$UPDATE:VMSINSTAL MXvvn ddcu:)

Substitute the appropriate values for (vvn) and (ddcu). OpenVMS Alpha Software Product Installation Procedure V7.2 It is dd-Mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help.

If there are any users logged into the system, you will see the message %VMSINSTAL-W-ACTIVE, The following processes are still active: ...process names...

You can install MX while users are logged in, though it is safer to perform the installation while no one is logged in and while your network links are shut down. (* Do you want to continue anyway [NO]?)

If you wish to continue, answer YES. (* Are you satisfied with the backup of your system disk [YES]?)

If you feel comfortable with your system disk backup, answer YES. Otherwise, answer NO, perform the backup, then restart the installation procedure. (Preliminary Installation Checks\install_prelimchecks)

The installation procedure first checks to make sure that the version of VMS that you are running is compatible with the version of MX being installed, and does some preliminary checks on disk space. It then tries to determine the type of installation and the location of the MX directory tree. (Ensuring that MX is Currently Shut Down\mxupcheck)

If a version of MX is currently installed, the installation procedure will check to see if any MX delivery agents are currently running. If so, it will warn you of this and ask if you wish to continue with the installation: (%MX-I-NOTDOWN, MX delivery agents have not been shut down.) (* Do you wish to continue [NO]?) It is (strongly) recommended that you answer NO to this question, shut down MX, then restart the installation. (Determining the Installation Type\detinsttype)

The installation procedure examines the system to determine if a version of MX is already installed. If there is a version of MX installed, it then determines whether this is an (upgrade) from an upgradable previous version of MX, or a (reinstall) of the current version. In either case, the installation procedure asks you if you wish to update the MX installation it found: (%MX-I-INSTALDET, An installation of MX V(v.u) has been detected at (dev:[dir]).) (* Do you wish to update the existing installation [YES]? ) If you answer YES to this question, the installation procedure will skip the question about selecting a location for the MX directory tree.

If this is a fresh install, or you answer NO when asked about updating an existing installation, you are then asked: (* Where should the MX top directory be located [SYS$SYSDEVICE:[MX]]:)

You may place the MX directories on any disk you like. If MX is already installed on the system and its logical names are defined, the default answer will be the definition of your existing MX root directory. If you are installing MX on a mixed VMScluster where systems of different architectures will share a common directory, be sure you specify a disk that is common to all types of systems. The default device (SYS$SYSDEVICE:) may not be appropriate, especially if you do not cross-mount your system disks between systems of different architectures. (Mixed-Architecture Installation\install_mixed_arch)

MX next determines if the system is part of a VMScluster, and if the version of MX currently being installed has already been installed once on a node in the cluster of a different architecture. If both of these are found to be true the installation procedure then asks: * Do you wish to install only (arch)-specific files [YES]?

You should answer YES to this question unless you really want to re-install the architecture-independent files.

The last of the preliminary questions is (* Do you want to purge files replaced by this installation [YES]?)

If this is the first time you have installed MX, answering NO to this question can save some time when the MX files are moved into their directories. (Component Selection\INSTALL_GUIDE_16)

A menu of MX components appears next, and you are asked to enter your choices from the menu: 1. [ ] Base MX software 2. [ ] NETLIB network support 3. [ ] SMTP interface support 4. [ ] SMTP-over-DECnet support 5. [ ] Site-provided interface support 6. [ ] Mailing List/File Server support 7. [ ] Documentation 8. [ ] Example files and programs 9. Exit * Your choice [9]:

The exact contents of this menu may differ from the above display, depending on the system's architecture. In addition, if this is an architecture-specific-only installation (see (install_mixed_arch)), the last three choices in the menu will not be displayed.

Enter the number corresponding to the component you wish to install; multiple components may be selected by entering the numbers as a comma-separated list. The menu is displayed again after each selection, with asterisks appearing next to the items you have selected; selecting a component twice removes it from the selection list.

When you are upgrading to a new version of MX, the installation procedure will look at your current configuration to automatically determine the components that should be installed. If you wish to omit any of those components that were selected, simply select them again to remove it from the list.

When you have selected the components you want to install, enter (9\BOLD) to exit the menu. Your selections are displayed again and you are asked to confirm your selections: You have selected the following optional components: (selected components listed here) * Is this correct [YES]?

Press RETURN to continue the installation, or enter NO to return to the components menu. (Component Notes\INSTALL_GUIDE_52)

You (must) install the Base software component if this is your first installation of MX, or if you are upgrading from a previous version of MX. The other components are optional and may be installed at any time after the Base component is installed. If you re-install the Base component, you must also re-install all desired optional components as well, except for documentation, examples and contributed files.

If you elect to install SMTP support, NETLIB support will automatically be installed as well. If you have already installed the NETLIB support component, you can disable the NETLIB re-installation by re-selecting it on the menu. (NETLIB Component Installation\INSTALL_GUIDE_20)

If you are installing the NETLIB component (required for SMTP support using TCP/IP), the saveset containing the NETLIB support files will be loaded and you will be asked some questions regarding the configuration of NETLIB.

The NETLIB installation procedure asks where the NETLIB shareable libraries should be placed: (* Where should the NETLIB libraries be placed [(device:[directory])]:)

If this is your first installation of NETLIB, the default answer for this question will be the directory where the MX executables are located. However, you may specify any valid location for these files. (The Installation Completes\optinst)

After the configuration questions and NETLIB component installations, which always require input from the installer, all selected components are installed. Files are copied from the each save set of the installation kit, then all installed files are copied to their destination directories. Informational messages about the individual components are displayed as needed.