Previous | Next | Contents | Index |
Example 2-1 is a sample PMDF-MTA installation dialogue (using the
VMSINSTAL utility). Before the installation started, the PMDF V6.7
product kit was copied from the PMDF distribution CD-ROM directory
([pmdf066.openvms]
) to the DKA100:[000000]
directory.
Remember that the values in this sample installation are for purposes of example only. Make sure you use values that are appropriate for your system when you perform the actual installation.
Whenever possible, the installation supplies a default (which is enclosed in square brackets). If you want to accept the default value, press [RETURN]. Otherwise, enter the correct value. |
Example 2-1 Example PMDF V6.7 Installation |
---|
$ @SYS$UPDATE:VMSINSTAL.COM OpenVMS Alpha Software Product Installation Procedure V7.1 It is 5-JAN-2015 at 10:58. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: DKA100:[000000] Enter the products to be processed from the first distribution volume set. * Products: PMDF066 * Enter installation options you wish to use (none): [RETURN] The following products will be processed: PMDF V6.7 Beginning installation of PMDF V6.7 at 10:59 %VMSINSTAL-I-RESTORE, Restoring product save set A ... *---------------------------------* | | | Installing PMDF Version 6.7 | | | *---------------------------------* Copyright (c) 2015 Process Software. All rights reserved. The PMDF mark and all PMDF based trademarks and logos are trademarks of Sun Microsystems, Inc. in the U.S. and other countries and are used under license. ALL RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES This licensed material is the valuable property of Process Software. Its use, duplication, or disclosure is subject to the restrictions set forth in the License Agreement. Other use, duplication or disclosure, unless expressly provided for in the license agreement, is unlawful. Product: PMDF-MTA, PMDF-ACCESS, or PMDF Producer: INNOSOFT Version: 6.7 Release Date: 30-JAN-2015 * Does this product have an authorization key registered and loaded? YES ***************************** *** *** *** I M P O R T A N T *** *** *** ***************************** Make sure you read the PMDF Installation Guide, OpenVMS Edition, before proceeding with this installation. If you do not have a copy of the installation guide, see the Process Software web site at www.process.com, or contact Process Software technical support. * [Press RETURN To Continue]: [RETURN] * Do you want to purge files replaced by this installation [YES]? YES Alpha VMS executables will be provided automatically by this installation. The installations of VAX VMS or I64 VMS executables is optional. Having all sets of executables on the same system causes no conflicts in PMDF. * Install VAX VMS executables as well as Alpha VMS executables [NO]? NO * Install I64 VMS executables as well as Alpha VMS executables [NO]? NO You will now be asked where you want the PMDF files to be installed. The files will be stored in a directory tree of your choice on the device and under the directory which you specify. A system-wide logical name called PMDF_ROOT will be created by the PMDF startup procedure to refer to this directory tree. Enter the device and directory or rooted directory where the top level PMDF tree should be. e.g. DUA3:[PMDF] or DUA0:[UTILS.MAILSTUFF.PMDF040] or if the logical name UTIL_DIR: is a rooted logical pointing to DUA0:[UTIL.PMDF.] you can use something like UTIL_DIR:[V33] Note that you must NOT include the trailing "." as in a rooted directory name here (it will be added when the root is defined). * Enter the device and directory [SYS$SYSDEVICE:[PMDF]]: DKA0:[PMDF] This is a new installation of PMDF. If you plan to use channel or system level mail filtering or use PhoneNet channels, or channels that use DECnet proxied transports (PhoneNet over DECnet or SMTP over DECnet) you will need a PMDF server account. Other channels do not require a special PMDF server account. The server account name is usually PMDF... but you can use another name. NOTE: A disk quota entry must be manually created for the PMDF server account if one is needed. Failure to do so will make it impossible for nonprivileged users to send PMDF mail. * Username for the PMDF server account [PMDF]: PMDF * Does this account already exist [NO]? NO * Password for the PMDF server account: somepassword * Numeric UIC for the PMDF server account [[375,1]]: [375,1] %PMDF-I-CREPMDFSACC, Creating PMDF server account %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PMDF. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PMDF value: [000375,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PMDF. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PMDF. %UAF-I-MDFYMSG, user record(s) updated PMDF channel programs that perform proxied actions on behalf of users need a nonprivileged context to operate in. This context is provided by a special nonprivileged account. This PMDF user account should be in a group by itself to prevent unauthorized file access by group, and the UIC group should be outside of the system UIC group range. The user account name is usually PMDF_USER... but you can use another name. * Username for the PMDF user account [PMDF_USER]? PMDF_USER * Does this account already exist [NO]? NO * Password for the PMDF user account: whateverpassword * Numeric UIC for the PMDF user account [[374,1]]? [374,1] %PMDF-I-MODPMDFUACC, Creating PMDF user account %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PMDF_USER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PMDF_USER value: [000374,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PMDF_USER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PMDF_USER. %UAF-I-MDFYMSG, user record(s) updated PMDF operates by submitting its service jobs to a VMS queue for processing. The queue can either be a standard VMS batch queue or a queue serviced with the PMDF process symbiont. Although the queue used can be controlled on a per-channel basis, in most cases a default queue is used. Enter the name of this default queue here. * Queue PMDF jobs should run in [MAIL$BATCH]: MAIL$BATCH PMDF service jobs need to execute under a privileged username. This is normally SYSTEM. If you would prefer your PMDF service jobs to execute under a different privileged username, you can enter that username now. * Username for PMDF service jobs [SYSTEM]: SYSTEM PMDF's integrated DELIVER subsystem causes PMDF to submit batch jobs on behalf of users with MAIL.DELIVERY files. Enter a default queue for these jobs to run in. Note that MAIL.DELIVERY files can specify the queue the job they create runs in as well as various queue parameters. Also note that the queues handled by the PMDF process symbiont can NOT be used to run the jobs created by nonprivileged users' MAIL.DELIVERY files. * Batch queue DELIVER jobs should run in [SYS$BATCH]: SYS$BATCH PMDF needs to know the timezone for the site in order to fill in date-time lines in message headers. You may enter a timezone here which will be equivalenced to the system logical name PMDF_TIMEZONE for use by PMDF. If you do not specify a timezone, PMDF will use VMS system logicals to get the timezone, if your version of VMS supplies them. * Current timezone for this site [EST]: EST PMDF provides an online HELP file that describes the PMDF command. You can elect to add this help entry to your system help library. The entry is available as the file PMDF_ROOT:[DOC]PMDF.HLP regardless of whether or not you elect to install it. * Do you want a system help entry for the PMDF DCL command [YES]? YES * Do you want to run PMDF_STARTUP.COM after the installation completes [YES]? YES %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[PMDF]. * Do you wish to install PMDF-TLS [YES]?YES Product: PMDF-TLS Producer: INNOSOFT Version: 6.7 Release Date: 15-JAN-2015 * Do you wish to install PMDF-LAN [YES]? YES Product: PMDF-LAN or PMDF Producer: INNOSOFT Version: 6.7 Release Date: 15-JAN-2015 * Does this product have an authorization key registered and loaded? YES * Do you wish to install PMDF-DIRSYNC [YES]? NO * Do you wish to install the PMDF Message Store [YES]? YES Product: PMDF-MSGSTORE Producer: INNOSOFT Version: 6.7 Release Date: 15-JAN-2015 * Does this product have an authorization key registered and loaded? YES The mail RFC files will require 36645 blocks. * Do you wish to install the mail RFC files [YES]? YES You have chosen to install the mail RFC files. The HTML format documentation will require 43296 blocks. * Do you wish to install HTML format documentation [YES]? YES You have chosen to install the HTML format documentation. %PMDF-I-NOMORQST, No further questions will be asked during the installation %PMDF-I-PLEASEIGNORE, (Please ignore %CREATE-I-EXISTS informational messages) %VMSINSTAL-I-SYSDIR, This product creates system disk directory PMDF$INSTALL_RO OT:[DOC.HTML]. %PMDF-I-RESTORE, Restoring product save set B ... %PMDF-I-RESTORE, Restoring product save set C ... %PMDF-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory PMDF$INSTALL_RO OT:[OTHER]. %PMDF-I-RESTORE, Restoring product save set E ... %PMDF-I-RESTORE, Restoring product save set G ... ***************************** *** *** *** I M P O R T A N T *** *** *** ***************************** Upon completion of this installation, make sure you read the PMDF Installation Guide, OpenVMS Edition, and excute the Post-Installation Tasks, including: - If this installation is being done on an OpenVMS cluster, you must do INSTALL REPLACE SYS$LIBRARY:DCLTABLES and then do @SYS$STARTUP:PMDF_STARTUP.COM on all nodes where PMDF is going to be used (you may use SYSMAN for these). - Be sure that your system startup procedure includes SYS$STARTUP:PMDF_STARTUP.COM and SYS$STARTUP:PMDF_SUBMIT_JOBS.COM. PMDF_STARTUP should be run prior to starting any networks that PMDF is configured to run over (including DECnet). - The format of compiled configurations changes with each release of PMDF. If this is an upgrade and you use a compiled configuration, you must recompile your compiled configuration: $ PMDF CNBUILD If you elect to start PMDF prior to executing this command you should: $ INSTALL REPLACE PMDF_CONFIG_DATA This command should be executed on every node where PMDF is started. - If you are upgrading from a previous version of PMDF, then note that a new PMDF_SUBMIT_JOBS.COM is provided with this kit, so you should delete the periodic PMDF delivery job and PMDF Message Bouncer job in your PMDF queue and resubmit them by executing the command @SYS$STARTUP:PMDF_SUBMIT_JOBS %PMDF-I-RESTORE, Restoring product save set I ... %PMDF-I-CRTMPSTPRT, Creating temporary directories and setting file protections. .. %VMSINSTAL-I-SYSDIR, This product creates system disk directory PMDF$INSTALL_RO OT:[QUEUE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory PMDF$INSTALL_RO OT:[LOG]. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... $ INSTALL CREATE PMDF_CHARSET_DATA /OPEN/HEADER/SHARED!350!1 $ INSTALL CREATE PMDF_COMMAND_DATA /OPEN/HEADER/SHARED!350!1 $ INSTALL CREATE PMDF_SHARE_LIBRARY /OPEN/HEADER/SHARED!1860!7 $ INSTALL CREATE PMDF_TLS_LIBRARY /OPEN/HEADER/SHARED $ INSTALL CREATE PMDF_LDAPV3_LIBRARY /OPEN/HEADER/SHARED!151!2 $ INSTALL CREATE PMDF_X500_FORM /OPEN/HEADER/SHARED!531!3 $ INSTALL CREATE PMDF_CCSO_FORM /OPEN/HEADER/SHARED!488!3 $ INSTALL CREATE PMDF_USERNAME $ INSTALL CREATE PMDF_PRIV_DISP /OPEN/HEADER/SHARED/PROT!25!4 $ INSTALL CREATE PMDF_EXE:FOLDER.EXE /PRIV=(SYSPRV,SYSLCK)/HEADER $ INSTALL CREATE PMDF_EXE:PMDF.EXE /PRIV=(SYSPRV)/HEADER $ INSTALL CREATE PMDF_EXE:UA.EXE /OPEN/HEADER/SHARED/PRIV=(SYSPRV,CMKRNL) $ INSTALL CREATE PMDF_EXE:QM.EXE /OPEN/HEADER/SHARED/PRIV=(SYSPRV,CMKRNL,SYSLCK) $ INSTALL CREATE PMDF_EXE:PINE.EXE /OPEN/HEADER/SHARED/PRIV=(SYSPRV,CMKRNL)!!1 $ INSTALL CREATE PMDF_EXE:SEND.EXE /PRIV=(SYSPRV,CMKRNL) $ INSTALL CREATE PMDF_EXE:SUBMIT_MASTER.EXE /PRIV=(SYSPRV,CMKRNL) $ INSTALL CREATE PMDF_EXE:IMAPD.EXE /OPEN/HEADER/SHARED $ INSTALL CREATE PMDF_EXE:POP3D.EXE /OPEN/HEADER/SHARED $ INSTALL CREATE PMDF_EXE:POPMGR.EXE /OPEN/HEADER/SHARED/PRIV=(SYSPRV,SYSLCK) $ INSTALL CREATE PMDF_EXE:MRAPPSHAR_EMUL.EXE $ INSTALL CREATE PMDF_EXE:MUAS$MRIF_SHR_EMUL.EXE $ INSTALL CREATE PMDF_EXE:MRAXPSHAR.EXE $ INSTALL REPLACE SYS$LIBRARY:PAS$RTL.EXE /OPEN/SHARED/HEADER!250!1 $ INSTALL REPLACE SYS$MESSAGE:PAS$MSG.EXE /OPEN/HEADER %PMDF-I-LOADED, PMDF-MTA license is loaded Creating PMDF counters detached process %RUN-S-PROC_ID, identification of created process is 00000E19 Installation of PMDF V6.7 completed at 11:16 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PMDF.VMI_DATA Enter the products to be processed from the next distribution volume set. * Products: [RETURN] VMSINSTAL procedure done at 11:17 $ |
Previous | Next | Contents | Index |