The following is a list of tasks which must be completed following an upgrade installation of PMDF, PMDF-MTA, PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MB400, PMDF-MR, PMDF-MSGSTORE, PMDF-POPSTORE, PMDF-X400, PMDF-TLS, and PMDF-XGS.

1. If you are installing PMDF on multiple systems in a cluster with systems on different system disks (for example a mixed-architecture cluster), you should execute the pmdf_com:post_install.com procedure on one system for each distinct system disk, other than the one on which you installed PMDF. For any systems in the cluster that you do not run post_install.com on, the image sys$library:dcltables.exe must be reinstalled manually using the command:

   $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE

   
   

2. The installation procedure replaces the old version of the file pmdf_startup.com in the SYS$STARTUP directory with a new version. (This is the procedure normally executed during system startup to define PMDF logicals and install PMDF images.) If PMDF is running in a cluster, you should execute pmdf_startup.com on any other cluster members sharing this PMDF configuration to ensure that all such systems have current logical name definitions.

   Note The PMDF installation has no way to merge local changes made in an old pmdf_startup.com into the new version of this file. As such, the installation procedure preserves any existing pmdf_startup.com file as pmdf_startup.old so that changes can be retrofitted manually. It is far preferable, however, for sites to refrain from adding private commands, logical definitions, etc., to the pmdf_startup.com command procedure.

   Rather than customizing pmdf_startup.com itself, which will be replaced when you upgrade PMDF, you can create a PMDF_COM:pmdf_site_startup.com procedure and put your site specific PMDF definitions in that file. When pmdf_startup.com executes, it checks for the existence of such a site-supplied pmdf_site_startup.com procedure and executes it, if it exists.
   
3. If you use a compiled PMDF configuration, you must recompile and reinstall your PMDF configuration; e.g.:

   $ PMDF CNBUILD $ INSTALL REPLACE PMDF_CONFIG_DATA

   You cannot copy over an old compiled configuration for use with PMDF V6.2-1; the compiled configuration format always changes with each new release of PMDF. You need to reinstall the configuration image on any other cluster members running PMDF. If you use PMDF in a mixed architecture cluster, you need to recompile your configuration on a cluster member of each architecture type, so that both forms of the compiled configuration will be available for reinstallation.

4. Sites with existing popstore users who want to use the PMDF MessageStore should issue this command:

   $ PMDF POPSTORE UPGRADE

   to cause their popstore user account names to be properly modified for compatibility with PMDF MessageStore profiles.

5. If you are upgrading PMDF-MTA and use PMDF's MAILSERV facility you should update your site-specific MAILSERV help and index files to reflect the new version and new capabilities. Sample versions of these files are provided as the files mailserv_help.sample and mailserv_index.sample, respectively, in the PMDF_TABLE: directory. These files should be compared against their site-specific equivalents help.txt and index.txt, both located in the PMDF_MAILSERV_FILES_DIR:[000000] directory, and the site-specific files updated appropriately.
6. If you are using the PMDF-LAN Lotus Notes channel, PMDF-DIRSYNC Lotus Notes directory agent, or PMDF-XGS, be sure to upgrade the PMDF images used on the Lotus Notes server or XGS transport bridge system. These are OS/2 or NT PMDF images, available under the pmdf_root:[other] directory on the PMDF system, or available directly off the PMDF distribution CD-ROM under the other directory. Note that this is an ISO 9660 with Rockridge extensions CD-ROM, readable from many different platforms including OS/2 and NT.
   1. For PMDF-XGS, shutdown all the PMDF-XGS processes on the transport bridge, copy the respective files to the transport bridge system, and restart the processes.
   2. For a PMDF-LAN Lotus Notes channel, shut down the PMDF Lotus Notes Server Add-ins, using Lotus Notes server console commands such as TELL PNGATECIN QUIT, and TELL PNGATECOUT QUIT (or just TELL PNGATEC QUIT if you were using just the one Server Add-in). Then copy the new server Add-ins to the Lotus Notes server, and start them back up (e.g., LOAD PNGATECIN and LOAD PNGATECOUT).
7. If you are upgrading from PMDF V5.0 or earlier, there are additional steps you need to perform, described in Section 1.7.4. If you are upgrading from V5.1, see additional steps in Section 1.7.3. If you are upgrading from V5.2, see additional steps in Section 1.7.2. If you are upgrading from V6.0, V6.1, or V6.1-1, see additional steps in Section 1.7.1.
8. When all the above post-installation tasks have been completed (including those described in Section 1.7.2 to Section 1.7.5, if appropriate), it is time to start PMDF back up:
   1. Start up the PMDF Dispatcher with the command

      $ PMDF STARTUP DISPATCHER

   2. Start up the MAIL$BATCH queue and any other PMDF queues. You can use the commands

      $ @SYS$STARTUP:PMDF_INIT_QUEUES.COM $ @SYS$STARTUP:PMDF_START_QUEUES.COM

   3. If you are using PMDF-MR in MR TS replacement mode (no real Message Router), you should restart your MailWorks server and ALL-IN-1 Sender and ALL-IN-1 Fetcher so that they can reconnect to the new version of PMDF-MR and resume running.