The PMDF distribution kit contains the distribution media and all necessary license PAKs. (You must have license for a layered product before you can install it.)

You can install any of the PMDF layered products, even if you do not have a PAK for it. However, you will not be able to use that layered product until you have registered and loaded the proper PAK. If you are upgrading PMDF, you can 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

PMDF requires that HP Pascal RTL V5.0-15 or later (VAX), or V5.0-18 or later (Alpha), or V5.0-25 or later (I64) be installed on your system before you can install PMDF. Process Software has received permission from Hewlett-Packard Company to include the Pascal RTL for VAX and Alpha in the PMDF distribution kit. If RTL is not on your system, the PMDF installation procedure will install it automatically.

If you will be using TCP/IP-based components of PMDF (for example, the PMDF Service Dispatcher and all its services), then you must have a TCP/IP package installed and configured. The TCP/IP package must be one of the following:

• Hewlett-Packard Company's TCP/IP Services for OpenVMS (UCX) V4.0 or later. If you are using V4.1 of HP TCP/IP Services for OpenVMS (UCX), you must have "ECO 5" or later installed on your system.
• Process Software's MultiNet V3.4A or later, with all UCXDRIVER patches.
• Process Software's TCPware V5.0 or later.
• The Wollongong Group's Pathway V2.5.x or later, with all patches (in particular C82195).

There are also several important OpenVMS patches that you should obtain and install (if you have not done so already). The following OpenVMS patches will fix bugs which exist, regardless of whether or not you run PMDF.

See also the Process Software PMDF support web pages for the latest list of required operating system patches (http://www.process.com/techsupport/pmdf.html).

• CSCPAT VAXSYS01_062 (for VAX V6.2 systems), or CSCPAT VAXSHAD09_061 (for VAX 6.1 systems) Sites that are using the cluster I/O cache with an OpenVMS VAX V6.1 or V6.2 system anywhere in the cluster could see corruption of shared files anywhere in the cluster. (CSCPAT VAXSYSA01_062 supersedes CSCPAT VAXSYS14_061.) The bugs impact files that see a high rate of open/update/close operations, such as the mail.log_current, and the PMDF queue cache database files.
• CSCPAT VAXRMS02_061 (for VAX systems, superceded by the VAXRMS04_061 patch). These patches will fix a bug in the VMS callable CONVERT utility. This bug impacts files that are operated on by CONVERT/RECLAIM (such as users' 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"). This bug also impacts PMDF's queue cache database.
• The latest HSC and HSJ software Sites that are using the cluster I/O cache and HSCs or HSJs could see some file corruption.
• ALPLIBRF08_070 (for Alpha/VMS V7.0) This patch has no dependencies.
• VAXCDU01_061 (for OpenVMS VAX V6.1) This patch fixes a size problem with a command table. Without this patch, you will encounter a %CDU-F-INTNODESPACE error when you attempt to install the new PMDF command line definitions. Consequently, PMDF will not run.
• ALPMAIL02_071 (for OpenVMS Alpha 7.1), or VAXMAIL02_062 (for OpenVMS VAX 6.2), or VAXMAIL02_071 (for OpenVMS VAX 7.1) This patch fixes several callable MAIL bugs, including a callable MAIL bug that could result in lost e-mail message bodies. E-mail could be lost under the following circumstances:
  • Two messages were delivered within a short period of time, and the first message is "large" (and it is stored in an external MAIL$*.MAI file), and the second message is "small" (and it is stored in the main mail file). Under these circumstances, the deletion of the large message could result in the deletion of the body of the small message. Even though the small message would still appear to be present in the mail file (as shown with a DIRECTORY command), the message body would no longer exist.
  • The messages were copied to another folder, possibly by the PMDF IMAP server, or the PMDF FOLDER utility (which is used implicitly by certain DELIVER operations).
  Contact HP regarding the availability of patches for other versions of OpenVMS.
• Sites running OpenVMS VAX V6.2, or V7.0, or V7.1, or OpenVMS Alpha V7.1 should obtain and install the following patches:
  • VAXMAIL01_062 (superseded by the VAXMAIL02_062 patch)
  • VAXMAIL02_070, VAXMAIL01_071 (superseded by the VAXMAIL03_071 patch)
  • ALPMAIL02_070, or ALPMAIL01_071 (superseded by the ALPMAIL03_071 patch)
  These patches fix a number of callable MAIL bugs, including a problem of occasional access violations in MAILSHRP (which is called by PMDF MAIL and the PMDF POP server).

  Note This problem occurred primarily at sites that had many thousands of simultaneous mail users.

If appropriate, contact HP to obtain these patches. You should also check to see if there are even more recent patches that supersede those listed above. You should also ask HP for a list of recommended patches that you need to apply to your version of the operating system.

1.1.2 Distribution Media

CD-ROM distributions contain a standard OpenVMS file system with PMDF product save sets residing in the [pmdf066.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 pmdf066

where device is the OpenVMS device name of your CD-ROM drive.

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:[pmdf066.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: PMDF066 $ COPY/LOG dka500:[PMDF066.OPENVMS]*.* 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.

You should read through this guide before beginning the installation of or upgrade to PMDF V6.7. Release notes (bug fixes and new features) for PMDF V6.7 can be found in the PMDF V6.7 Release Notes, visible at the Process Software web site.

1.1.3 Disk Space Requirements

Table 1-1 Disk Space Requirements for PMDF

	Blocks Required
Product	Common	VAX	ALPHA	I64	Total
PMDF	91686	123801	113391	188094	516972
PMDF-LAN	0	1059	1306	3310	5675
PMDF-DIRSYNC	0	2070	2756	6716	11542
PMDF-MSGSTORE	0	1537	1634	4134	7305
PMDF-TLS	0	30480	22587	35969	89036
Total:	91686	158947	141674	238223	630530

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 can 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

Note that these numbers are only the best estimates available at press time. They can 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, as of version 6.0, 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) might require a 600,000 block page file.

Page file requirements have not changed substantially on OpenVMS ALPHA.