PMDF Installation Guide
OpenVMS Edition
1.7 Post-Installation Tasks for Upgrades
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.
- 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
|
- 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.
- 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; 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.
- It is a good idea to rebuild the PMDF queue cache database after
even minor dash upgrades.
- The
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 of pmdf_submit_jobs.com into the new version of
this file. Therefore, the installation procedure preserves any existing
pmdf_submit_jobs.com file as
pmdf_submit_jobs.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_submit_jobs.com command procedure; instead, add them
to the procedure which invokes pmdf_submit_jobs.com .
|
- If you have performed an upgrade from a previous version of PMDF
you can continue to use your existing configuration files. You might
still run the configuration generator and compare the output with your
old configuration. You can always redirect the output of the
configuration generator utility to avoid overwriting your working
configuration. In many cases, the automatically generated configuration
will contain new rules and useful techniques you can apply to your own
configuration.
- The HTTP configuration file must be updated upon upgrading to PMDF
V6.2. The HTTP configuration file is usually
pmdf_table:http.cnf
on VMS. This file can be updated by
running the pmdf configure dispatcher
utility, or by
editing the http.cnf
file manually. The manual steps are
as follows. Add the following three lines:
[PATH=/images/]
GET=PMDF_HTTP_GET
HIDDEN=1
|
Find the following lines and replace them as follows:
- replace
[PATH=/popstore_user/]
with
[PATH=/msps_user/]
- replace
[PATH=/popstore_pwd/]
with
[PATH=/chng_pwd/]
- As of PMDF V6.2, the global pmdf filter file
(
pmdf.filter
in the table directory) requires the
require
command, the same way that the channel and user
filter files always have. If you have a global filter file that
contains any of the following commands, you must add a
require
statement to the top of your filter file, which
lists the commands that the filter file uses.
envelope
fileinto
reject
vacation
- If there were messages in your old queue created by an earlier
version of PMDF, you can move them into the new PMDF queue at this
time.
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 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 this command:
In either case, the images specified by pmdfimage.dat
are
reinstalled. This will not hurt anything.
- Versions of the HP Pascal RTL (Run Time Library) earlier than
V5.0-15 (VAX) or V5.0-18 (Alpha) were not fully thread-safe; PMDF's
multithreaded SMTP server and multithreaded SMTP client were liable to
exercise these problems.
Hewlett-Packard Corporation has given Process Software permission to
distribute an updated version of their Pascal RTL. As of PMDF V5.0-6,
the PMDF installation procedure will check the version of the Pascal
RTL installed on the system on which you install PMDF, and will install
an updated Pascal RTL,
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
Compaq 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.
- If you also installed PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MB400,
PMDF-MR, PMDF-X400, or PMDF-XGS for the first time, or are using
PMDF-MSGSTORE or PMDF-POPSTORE for the first time, then you should
configure them now. Configuration instructions for PMDF-MSGSTORE and
PMDF-POPSTORE can be found in Chapters 7 and 8.
Configuration instructions for PMDF-FAX can be found in Chapters
11 and 12; configuration instructions for PMDF-LAN
can be found in Chapters 9 and 10; configuration
instructions for PMDF-MB400 can be found in Chapters 13 and
14; configuration instructions for PMDF-MR can be found in
Chapters 15 and 16; configuration instructions for
PMDF-X400 can be found in Chapters 17 and 18;
configuration instructions for PMDF-XGS can be found in Chapters
19 through 22.
- If you are upgrading PMDF-MR, then you are encouraged to re-run the
PMDF CONFIGURE MR utility so as to generate new FROM_MR and TO_MR
mapping rules. More versatile mappings are now generated by this
utility.
- Sites with existing popstore users who want to use the PMDF
MessageStore should issue this command:
to cause their popstore user account names to be properly modified for
compatibility with PMDF MessageStore profiles.
- 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.
- 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.
- 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.
- 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).
- If you are upgrading from PMDF V5.0 or earlier, there are
additional steps you need to perform, described in Section 1.7.3. If you
are upgrading from V5.1, see additional steps in Section 1.7.2. If you
are upgrading from V5.2, see additional steps in Section 1.7.1.
- When all the above post-installation tasks have been completed
(including those described in Section 1.7.1 to Section 1.7.4, if
appropriate), it is time to start PMDF back up:
- Start up the PMDF Dispatcher with the command
$ PMDF STARTUP DISPATCHER
|
- Start up the MAIL$BATCH queue and any other PMDF queues.
- 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.