The following is a list of tasks which must be completed following an upgrade installation of PMDF, PMDF-MTA, PMDF-ACCESS, PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MB400, PMDF-MR, PMDF-MSGSTORE, PMDF-POPSTORE, PMDF-X400, and PMDF-XGS.
SYS$LIBRARY:dcltables.exe must be reinstalled manually
across the cluster using the command:
$ INSTALL REPLACE SYS$LIBRARY:dcltables.exeIn addition, if you are installing or upgrading PMDF in a mixed architecture cluster, then you must issue, prior to the above INSTALL command, the command
$ SET COMMAND/TABLE=SYS$COMMON:[syslib]dcltables.exe -
/OUTPUT=SYS$COMMON:[syslib]dcltables.exe PMDF_COM:pmdf.cld
Issue this command on a cluster member of architecture type different
from that of the system on which you installed PMDF. That is, if you
installed PMDF on an Alpha member of the cluster, then issue the above
SET command on a VAX cluster member. If instead you installed PMDF on a
VAX cluster member, then issue that command on an Alpha cluster member.
PMDF_COM:post_install.com
procedure on a system of the "other" architecture, or on each
system having a distinct system disk. 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 oldpmdf_startup.cominto the new version of this file. As such, the installation procedure preserves any existingpmdf_startup.comfile aspmdf_startup.oldso that changes can be retrofitted manually. It is far preferable, however, for sites to refrain from adding private commands, logical definitions, etc., to thepmdf_startup.comcommand procedure.
pmdf_startup.com itself, which will be replaced when you
upgrade PMDF, you may 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. $ PMDF CNBUILD $ INSTALL REPLACE PMDF_CONFIG_DATAYou cannot copy over an old compiled configuration for use with PMDF V6.0; the compiled configuration format always changes with each new release of PMDF. You will also need to reinstall the configuration image on any other cluster members running PMDF. If you use PMDF in a mixed architecture cluster, then you will 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.
$ PMDF CACHE/REBUILDNote that it is also a good idea to rebuild the PMDF queue cache database after even minor dash upgrades.
pmdf_submit_jobs.com
command file created during the installation is used to resubmit PMDF
service jobs after a system queue failure or initialization, or after
the jobs have been deleted, as during the pre-installation steps. You
must resubmit the PMDF periodic jobs now by issuing the command
$ @SYS$STARTUP:pmdf_submit_jobs.com(Your system startup procedure should issue this command as well, so that the jobs will be submitted after a system reboot.)
Note:
The PMDF installation has no way to merge local changes made in an old version ofpmdf_submit_jobs.cominto the new version of this file. Therefore the installation procedure preserves any existingpmdf_submit_jobs.comfile aspmdf_submit_jobs.oldso that changes can be retrofitted manually. It is far preferable, however, for sites to refrain from adding private commands, logical definitions, etc., to thepmdf_submit_jobs.comcommand procedure; instead, add them to the procedure which invokespmdf_submit_jobs.com.
pmdf_startup.com installs a number of images using
the OpenVMS INSTALL utility. These images are listed in the file
pmdfimage.dat in the PMDF_COM: directory. The
pmdfimage.dat file is reserved for PMDF use and should not
be modified.
Site-specific images can be installed by using the file
siteimage.dat in the PMDF_COM: directory.
pmdf_startup.com checks to see if this file exists and
installs the images listed in it if it does exist. The
siteimage.dat file has the same format as
pmdfimage.dat. This format is extremely simple---a file
name is specified followed by the appropriate qualifiers for OpenVMS
INSTALL. The file name must be separated from the qualifiers by at
least one space or tab character. The siteimage.dat file
is not provided by the installation process; it must be created
manually. If you have installed a new version of PMDF in a different
location you should copy over any old siteimage.dat file
you have previously built. Once you have built or copied over this file
you can either re-run pmdf_startup.com to install the
additional images it specifies or use the command:
$ PMDF INSTALL CREATEIn either case the images specified by
pmdfimage.dat will
be reinstalled, but this will not hurt anything. pasrtl.exe (VAX) or
pas$rtl.exe (Alpha), if your system is running OpenVMS 6.1
or later and is using an older version of the RTL. This new version of
the Pascal RTL will be included in the next releases of OpenVMS and DEC
Pascal for OpenVMS.
If you are running a shared PMDF configuration on a cluster, then note
that the PMDF installation will only update the Pascal RTL on the node
on which you perform the installation; you must separately update the
Pascal RTL on any other system disks. (Sites running PMDF on a mixed
architecture cluster or on a cluster with multiple system disks should
note that post_install.com does not update the
Pascal RTL; you must still update the Pascal RTL separately.) See
Appendix A for details. PMDF_POPSTORE_PROFILES:[000000] directory.
This database is only used for management functions and does not in any
way impact the performance of the popstore.
Sites which were using the popstore under PMDF V5.1 should issue the
command
$ PMDF POPSTORE X-BUILD-USER-DBafter upgrading to PMDF V6.0. This command will scan the profile directory tree and build a user database. Sites upgrading from V5.1 of the popstore should note that the popstore will continue to function without this command being issued. At issue is that some management operations will not function until this command is executed.
dispatcher.cnf file and any
WEB500 path definition from your http.cnf file.
$ PMDF POPSTORE UPGRADEto cause their popstore user account names to be properly modified for compatibility with PMDF MessageStore profiles.
PMDF_TABLE:x400_mappings.sample may provide a useful
sample starting point.
PORT_ACCESS TCP|*|110|*|* $YPOP-RULES TCP|*|143|*|* $YIMAP-RULESThen you would need corresponding security configuration ruleset definitions of:
[RULESET=DEFAULT] ENABLE=MSGSTORE/*,PASSDB/*,SYSTEM/* ! [RULESET=POP-RULES] ENABLE=MSGSTORE/*,PASSDB/CRAM-MD5,PASSDB/APOP,SYSTEM/* ! [RULESET=IMAP-RULES] ENABLE=SYSTEM/*
/, in normal folder names. If you are upgrading
from PMDF V5.1 or earlier, IMAP users with existing folder names
containing the slash character will need to rename those folders using
something other than IMAP, e.g., using VMS MAIL or PMDF MAIL,
in order to see the folders from IMAP. You may find the FIND_SLASHES
program helpful for spotting (and optionally renaming) such folders, as
discussed in Section 1.5 .
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.
notes.ini,
defining server tasks from
ServerTasks=...,PNGATECto
ServerTasks=...,PNGATECIN,PNGATECOUT
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.
$ PMDF STARTUP DISPATCHER