Prior to performing an installation or upgrade you should have received a PMDF distribution package containing the distribution media and any necessary license Product Authorization Keys (PAKs). You can install one of the PMDF layered products even if you do not currently have a PAK for it; you just won't be able to use that layered product until you have registered and loaded the proper PAK. If you are upgrading PMDF, then you may continue to use your old PAKs. Upgrading sites are only sent new PAKs when they renew their maintenance contracts.²
1.1.1 Supported OpenVMS and other software versions
This version of PMDF will only operate under OpenVMS VAX or Alpha AXP
V6.1 and later.
PMDF requires that the DEC Pascal RTL V5.0-15 (VAX) or V5.0-18 (Alpha) or later be installed. Innosoft has received permission from DEC to include this DEC Pascal RTL in the PMDF distribution. The PMDF installation procedure will automatically install this RTL, if it or a later version is not already present on the system.
If you will be using TCP/IP based components of PMDF, for instance, the PMDF Service Dispatcher and all its services including the PMDF POP and IMAP servers, TCP/IP channels, PMDF-LAN's Lotus Notes channel, PMDF-DIRSYNC's Lotus Notes or LDAP directory agents, or PMDF-XGS, etc., then you must have a TCP/IP package installed and configured. And that TCP/IP package must be one of the following:
There are also several important OpenVMS patches which you should obtain and apply if you have not done so already. The first three patches listed below all relate to conditions which can lead to the corruption of files in your cluster. These OpenVMS patches fix bugs which exist regardless of whether or not you run PMDF.
mail.log_current
and PMDF queue cache database files.
mail.mai files when they use VMS MAIL's PURGE/RECLAIM
command, or when users exit from VMS MAIL and have their wastebasket
folder "auto-purged". It also impacts PMDF's queue cache
database.
Contact DEC to obtain these patches, and to check whether there are even more recent patches superseding those listed above. You can also ask DEC for a list of the recommended patches to apply to your version of the operating system.
1.1.2 Distribution media
PMDF is distributed on a single CD-ROM containing a single VMSINSTAL
installation kit for the PMDF product family: PMDF-MTA, PMDF-ACCESS,
PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MB400, PMDF-MR, PMDF-MSGSTORE,
PMDF-POPSTORE, PMDF-X400, and PMDF-XGS. (PMDF-TLS is distributed
separately, see Chapter 3 .)
CD-ROM distributions contain a standard OpenVMS filesystem with PMDF
product save sets residing in the [pmdf060.openvms]
directory.
Prior to installation or upgrade with VMSINSTAL, the CD-ROM should be inserted into a CD-ROM drive accessible to the system and mounted as follows:
$ MOUNT device volume-label
where device is the OpenVMS device name of your
CD-ROM drive. The volume-label you specify must
be that written on the CD-ROM media itself.
Once mounted, use the VMSINSTAL installation procedure as documented below. For the location of the distribution volume in step 4 of Section 1.6 , use the format
device:[pmdf060.openvms]
Please note that PMDF distributions are not compatible with the VMSINSTAL option G, which is sometimes used to move product save sets from distribution media to disk. If you choose to move PMDF product save sets from the distribution CD-ROM to disk, simply mount the CD-ROM and use the COPY command. For example:
$ MOUNT dka500: IIIFEB00
$ COPY/LOG dka500:*.* disk:[vmsinstal]
If you move PMDF product save sets to disk you can install from the
on-disk copy by providing VMSINSTAL with the disk and directory
(e.g., disk:[vmsinstal]) rather than a
device name.
Note:
While you may copy PMDF product save sets to disk, this is not required. As with any VMSINSTAL compatible product, PMDF may be installed directly from the distribution media.
You should read through this guide before beginning the installation of or upgrade to PMDF V6.0. Release notes (bug fixes and new features) for PMDF V6.0 can be found in the PMDF V6.0 Release Notes , visible at the Innosoft web site.
1.1.3 Disk space required
Table 1-1 lists the disk space requirements for PMDF.
| Kbytes Required | ||||
|---|---|---|---|---|
| Product | Common | VAX | ALPHA | Total |
| PMDF | 97848 | 174800 | 136400 | 409048 |
| PMDF-MR | 0 | 3488 | 1648 | 5136 |
| PMDF-FAX | 0 | 7056 | 12480 | 19536 |
| PMDF-LAN | 0 | 1264 | 1456 | 2720 |
| PMDF-DIRSYNC | 0 | 2400 | 3088 | 5488 |
| PMDF-XGS | 0 | 192 | 272 | 464 |
| PMDF-X400 | 0 | 2192 | 3008 | 5200 |
| PMDF-MSGSTORE | 0 | 4608 | 3760 | 8368 |
| PMDF-MB400 | 0 | 80 | 96 | 176 |
| || | ||||
| Total: | 97848 | 196080 | 162208 | 456136 |
PMDF is no longer copied to the system disk during installation. This means that during installation very few files are resident on the system disk unless they are actually being installed there. PMDF only requires about 2,000 temporary blocks on the system disk as a result.
All these numbers assume that PMDF is installed in a new location and/or existing files are not purged during the installation. Much less space is needed when PMDF is installed on top of an existing copy and purging is enabled. However, it is not possible for the kit to determine the exact amount of space needed in this case, so the worst case is assumed.
The installation procedure checks to make sure that enough space is available and will not install PMDF if there is not enough room. PMDF may be "trimmed" after installation to use less space by selective deletion of unneeded programs. However, this can only be done after the entire package is installed.
PMDF should be installed on a disk with no disk quotas active (e.g., a system disk) if possible. If this cannot be done, a disk quota entry should be set up for PMDF's UIC at this point in the installation. Use the PMDF server account UIC as described in Section 1.4.1 . Be sure to give PMDF enough quota to handle large numbers of messages (10,000 free blocks or more is recommended).
1.1.4 System parameters
If this is a new installation you would need at least 23000 free
GBLPAGES and about 70 free GBLSECTIONS. The need for GBLPAGES is
increased by the size of your compiled configuration file if a compiled
configuration is used. VIRTUALPAGECNT may also need to be increased if
you have a very large configuration.
Note that these numbers are only the best estimates available at press time. They may change from release to release. It would be better to err on the side of having too many free GBLPAGES and GBLSECTIONS than try to add the exact number each time.
PMDF servers normally run using the SYSTEM account and need an ENQLM of at least 400 and a FILLM of at least 200; so modify the quotas for your SYSTEM account if they are not already at or above these values. The SYSGEN parameters should also be modified so that PQL_MENQLM and PQL_DENQLM are at least 400 and PQL_MFILLM and PQL_DFILLM are at least 200, if they are not already at or above these values. These are dynamic parameters so no reboot is needed.
On OpenVMS VAX, this version of PMDF requires significantly more page file and more page file quota than previous versions of PMDF: perhaps 20000 pages per PMDF process. Such processes include each Worker Process under the Dispatcher, as well as each channel job running in a Process Symbiont or batch queue. For instance, even on a system with very little message traffic at least a minimum of 150,000 block page file is likely required. A system with a basic PMDF configuration (allowing up to 5 each of SMTP, POP, IMAP, HTTP, and POPPASSD processes, and with four PMDF Process Symbiont queues) that is running full out (all processes active) may require a 600,000 block page file.
Page file requirements have not changed substantially on OpenVMS ALPHA.