This chapter describes the two ways in which a PMDF-ACCESS license may be used, and discusses whether and how to use the PMDF-ACCESS configuration utility.
7.1 How PMDF-ACCESS may be used
There are two ways to use a PMDF-ACCESS license. In the case of a
member of a homogeneous OpenVMS cluster which already has a PMDF-MTA
system, a PMDF-ACCESS license is usually used simply to extend PMDF
functionality to the PMDF-ACCESS system. In this case, there is no
actual configuration to perform on the PMDF-ACCESS system; you merely
adjust (if necessary) the main PMDF-MTA configuration and activate
PMDF-ACCESS on the new system. See Section 7.2 below.
In the case of a system which is not clustered with a system running PMDF-MTA, or which is a member of a cluster which is sufficiently inhomogeneous to require a separate PMDF configuration on the system, or on which for any other reason you wish to have a separate PMDF configuration, you will need to create a PMDF-ACCESS specific configuration for the system using the PMDF-ACCESS configuration utility; see Section 7.3 for an overview, Section 7.4 for a description of the information you must be prepared to provide to the PMDF-ACCESS configuration utility, and Chapter 8 for an example PMDF-ACCESS configuration dialogue.
7.2 Activating PMDF-ACCESS on a PMDF-MTA cluster member system
On a PMDF-ACCESS system which will be sharing the use of a PMDF-MTA
configuration, you install PMDF-ACCESS by registering and loading the
PMDF-ACCESS license and running the pmdf_startup.com
procedure to define PMDF logicals pointing to the PMDF-MTA
configuration. (If the PMDF-ACCESS system is of the other architecture,
VAX or Alpha, than the PMDF-MTA system and if you haven't previously
done so, you first need to run the post_install.com
procedure.) See Chapter 1 for details.
In this case there is no actual configuration to perform on the
PMDF-ACCESS system. However, you may well want to adjust the PMDF-MTA
configuration to include new information about the PMDF-ACCESS system;
for instance, add a rewrite rule to the pmdf.cnf file on
the PMDF-MTA system that rewrites the PMDF-ACCESS system's name to the
PMDF-MTA's local host name. And if you use TCP/IP networking you may
want to check that your nameserver has an MX record for the PMDF-ACCESS
system name pointing to the PMDF-MTA system (unless you run an SMTP
server on the PMDF-ACCESS system itself).
7.3 The PMDF-ACCESS configuration utility
The PMDF-ACCESS configuration utility generates a configuration for one
or more PMDF-ACCESS nodes which are connected to the PMDF-MTA node
using either TCP/IP or DECnet. (Note that a PMDF-ACCESS node in a
homogeneous cluster does not need its own configuration and
the PMDF-ACCESS configuration utility should not be used---the
PMDF-MTA configuration will suffice both for the PMDF-MTA system and
for any PMDF-ACCESS systems in such a cluster.) This chapter provides a
checklist of the steps you need to take to complete the configuration
of PMDF-ACCESS.
If you don't have either TCP/IP or DECnet, a PhoneNet channel can be used to connect to your PMDF-MTA node, but this procedure does not generate such a channel for you. You would have to manually edit the configuration file by following instructions in the PhoneNet channels chapter in the PMDF System Manager's Guide.
A history of the configuration run is saved in the file
access_configure.history in the PMDF table directory when
you run the PMDF CONFIGURE ACCESS utility. When you run PMDF CONFIGURE
ACCESS again, you will be prompted as to whether the answers from the
history file should be used as default answers. The history file should
not be deleted casually, as it could save you from typing the same
answers over again, and may prove useful to Innosoft technical support
should you encounter problems.