Example 2-1 shows a PMDF-MTA installation dialogue using the VMSINSTAL
utility. In this example, the PMDF V6.0 product kit has been copied to
the directory D0:[000000] from the
[pmdf060.openvms] directory on the PMDF distribution
CD-ROM prior to installation.
Whenever appropriate, each prompt also supplies a default answer which is enclosed within square brackets. Simply pressing return, RETURN, selects the default answer.
Remember that the values entered in this sample are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual installation.
Example 2-1 Example PMDF V6.0 installation
$ @SYS$UPDATE:VMSINSTAL.COM
OpenVMS AXP Software Product Installation Procedure V7.2-1
It is 9-FEB-2000 at 13:59.
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: D0:[000000]
Enter the products to be processed from the first distribution volume set.
* Products: PMDF060
* Enter installation options you wish to use (none): RETURN
The following products will be processed:
PMDF V6.0
Beginning installation of PMDF V6.0 at 14:00
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
*-------------------------------*
| |
| Installing PMDF Version 6.0 |
| |
*-------------------------------*
Copyright © 1987-2000, Innosoft International, Inc.
Copyright © 1996, AP Coates
Unpublished --- all rights reserved under
the copyright laws of the United States
Innosoft International, Inc. is the sole owner of PMDF V6.0 Software
Products including all software and associated documentation. Use of
PMDF, PMDF-MTA, PMDF-ACCESS, PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN,
PMDF-MB400, PMDF-MR, PMDF-MSGSTORE, PMDF-POPSTORE, PMDF-TLS,
PMDF-X400, and/or PMDF-XGS software and associated documentation is
authorized only by a Software License Agreement. Such license
agreements specify the number of systems on which the software is
authorized for use, and, among other things, specifically prohibit use
or duplication of software or documentation, in whole or in part,
except as authorized by the Software License Agreement.
Restricted Rights Legend
Use, duplication, or disclosure by the 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 or as set forth in the
Commercial Computer Software --- Restricted Rights
clause at FAR 52.227-19.
Product: PMDF-MTA, PMDF-ACCESS, or PMDF
Producer: INNOSOFT
Version: 6.0
Release Date: 1-FEB-2000
* Does this product have an authorization key registered and loaded? YES
*************************************************************
*** ***
*** I M P O R T A N T O p e n V M S P A T C H E S ***
*** ***
*************************************************************
There are several important OpenVMS patches which you should obtain and
apply if you have not done so already. These patches fix bugs which
exist regardless of whether or not you run PMDF.
(1) Sites using the cluster I/O cache with an OpenVMS VAX or AXP V6.1
or V6.2 system ANYWHERE in the cluster may see corruption of shared
files anywhere in the cluster. For AXP V6.2 systems, obtain and
apply CSCPAT ALPSYS02_062; for AXP V6.1 systems, CSCPAT
AXPSYS13_061; for VAX V6.2 systems, CSCPAT VAXSYS01_062; for VAX
6.1 systems, CSCPAT VAXSYS14_061.
(2) Sites running OpenVMS VAX or AXP V6.1 should obtain and apply
apply CSCPAT ALPRMS04_061 and ALPSYS17_061 for AXP systems and
CSCPAT VAXRMS04_061 for VAX systems. This patch fixes a bug in
the DEC callable CONVERT utility.
(3) Sites using the cluster I/O cache and HSCs or HSJs may see
corruption of files. Make sure that you have the latest HSC and
HSJ software.
(4) Sites using any multithreaded applications (like the Dispatcher and
POP server) should apply ALPLIBR02_061 for OpenVMS Alpha V6.1; and
ALPY2K01_062 for OpenVMS Alpha V6.2; ALPLIBR05_070 for OpenVMS Alpha
V7.0 and ALPBASE02_071 for OpenVMS Alpha V7.1. OpenVMS VAX V6.2 to
V7.0 sites should apply VAXLIBR06_070.
(5) OpenVMS AXP V6.1 sites should obtain and apply CSCPAT ALPRMS04_061
and ALPSYS17_061. These patches fix bugs in OpenVMS which can lead
to POP or IMAP servers hanging.
(6) Sites running OpenVMS V7.0 should obtain and apply ALPMAIL02_070.
This and other MAIL patches (for different VMS versions) fix problems
with accvio's and non-fatal SSRVEXCEPTION bugchecks.
Contact DEC to obtain these patches or patches which may have superceded
them since this list was compiled. You can also ask DEC for a list of
the recommended patches to apply to your version of the operating system.
* Do you want to purge files replaced by this installation [YES]? YES
Alpha VMS executables will be provided automatically by this installation.
The installation of VAX VMS executables is optional. Having both sets
of executables on the same system causes no conflicts in PMDF.
* Install VAX 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], DUA0:[UTILS.MAILSTUFF.PMDF044]
or if the logical name UTIL_DIR: is a rooted logical pointing to
DUA0:[UTIL.PMDF.] you can use something like UTIL_DIR:[V44]
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]]: D4:[PMDF]
This is a new installation of PMDF.
If you plan to use channel or system level mail filtering or
use PMDF-X400, 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 may 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 [[377,1]]: [377,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: [000377,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 may 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 [[376,1]]? [376,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: [000376,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 may 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 may 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 requires the timezone for the site in order to fill in date-time
lines in message headers. The timezone you enter here will be equivalenced
to the system logical name PMDF_TIMEZONE for use by PMDF.
* Current timezone for this site [PST]: PST
PMDF provides an online HELP file that describes the PMDF command.
You may 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 D4:[PMDF].
* Do you wish to install PMDF-MR [YES]? YES
Product: PMDF-MR
Producer: INNOSOFT
Version: 6.0
Release Date: 1-FEB-2000
* Does this product have an authorization key registered and loaded? YES
* Do you wish to install PMDF-FAX [YES]? NO
* Do you wish to install PMDF-LAN [YES]? YES
Product: PMDF-LAN or PMDF
Producer: INNOSOFT
Version: 6.0
Release Date: 1-FEB-2000
* Does this product have an authorization key registered and loaded? YES
* Do you wish to install PMDF-XGS [YES]? NO
* Do you wish to install PMDF-X400 [YES]? NO
* Do you wish to install PMDF-MB400 [YES]? NO
* 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.0
Release Date: 12-JAN-2000
* Does this product have an authorization key registered and loaded? YES
The mail RFC files will require 29504 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 ...
%BACKUP-W-NOFILES, no files selected from PMDF$INSTALL_ROOT:[ALPHA_EXE]PAS$RTL.EXE
;*
%VMSINSTAL-W-NOFILE, New file PAS$RTL.EXE does not exist.
* * * * * * * * * * * * * * * * * * * * * * * * * * *
Upon completion of this installation, please do the following:
- 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 MAIL$BATCH queue and resubmit them by executing the command
@SYS$STARTUP:PMDF_SUBMIT_JOBS
- The "Post Installation Tasks" section in the PMDF Installation Guide
describes a number of additional tasks you may need to perform.
* * * * * * * * * * * * * * * * * * * * * * * * * * *
%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,SYS
LCK)
$ 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.0 completed at 14:19
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]PMDF060.VMI_DATA
Enter the products to be processed from the next distribution volume set.
* Products: RETURN
VMSINSTAL procedure done at 14:20
$