The following is a list of tasks which must be completed following a first 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, is used to define PMDF logical names and
install PMDF images. Add the following command to your system startup
command procedure:
$ @SYS$STARTUP:pmdf_startup.comThe
pmdf_startup.com procedure should be executed
before any networks are started. If you want this command
procedure to run as a SYSMAN startup task you can use the SYSMAN
STARTUP ADD FILE command to enter it into the SYSMAN database. When
using SYSMAN, you must ensure that pmdf_startup.com is
executed early in the startup phase before any networks have been
started. If this is an initial installation of PMDF, there is no need
to stop or shutdown your networks before executing
pmdf_startup.com manually if you did not ask KITINSTAL to
run pmdf_startup.com during the installation. Just be sure
that the order of pmdf_startup.com,
pmdf_submit_jobs.com and any commands to start networks
and queues is correct in your system startup procedure so when the
system reboots PMDF will be started properly.
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
a site-supplied pmdf_site_startup.com procedure and
executes it, if one exists. $ INSTALL CREATE PMDF_CONFIG_DATA/OPEN/SHARED/HEADERIf the old PMDF system is of the other architecture type, or if you are upgrading that old system as well as newly installing on the new additional system, then you will need to first generate a newly compiled configuration and then install it with the commands:
$ PMDF CNBUILD $ INSTALL CREATE PMDF_CONFIG_DATA/OPEN/SHARED/HEADER
pmdf_submit_jobs.com, is executed. Run the PMDF CONFIGURE
QUEUES utility to generate queue initialization and queue start
procedures suitable for your system; e.g.,
4
$ PMDF CONFIGURE QUEUES
This utility will create the following command files
SYS$STARTUP:PMDF_INIT_QUEUES.COM
SYS$STARTUP:PMDF_START_QUEUES.COM
SYS$STARTUP:PMDF_STOP_QUEUES.COM
SYS$STARTUP:PMDF_DELETE_QUEUES.COM
How many execution queues do you want? [4] 4
Do you want all queues to run on this node yournode? [Y] Yes
Do you want to initalize the queues now? [Y] Yes
Do you want to start the queues now? [Y] Yes
where your DECnet node name will appear where
yournode is shown above. If you have PMDF-MTA
licensed on multiple nodes in a cluster, you may wish to have execution
queues run on the multiple PMDF-MTA nodes for load balancing and
redundancy. pmdf_init_queues.com and
pmdf_start_queues.com contain sample commands to
initialize and start PMDF service queues, respectively; you may
customize the queue initialization and start commands in those files,
if you wish. (The pmdf_stop_queues.com and
pmdf_delete_queues.com procedures are provided for
convenience in testing, but are generally not used in production
setups.) If you wish to use the default queue definitions generated by
the PMDF CONFIGURE QUEUES utility, answer YES when asked
if you wish to initialize and start the queues now. So that these
queues will be properly initialized and started at system startup, you
must add the commands to initialize and start the queues to your system
startup procedure. In your system startup procedure, the queue
initialization commands, e.g.,
pmdf_init_queues.com, must be executed after
pmdf_startup.com is executed, normally before networking
packages PMDF employs have started. The queue start commands,
e.g., pmdf_start_queues.com, should generally be
issued after all networking packages PMDF employs have started, but
must be issued before pmdf_submit_jobs.com is
executed. Details on PMDF Process Symbiont queues may be found in
the PMDF System Manager's Guide .
pmdf_submit_jobs.com, is used to resubmit PMDF service
jobs after a system queue failure or initialization. The procedure
pmdf_submit_jobs.com must be executed by your system
startup after all networks are started and after the
MAIL$BATCH queue and other PMDF service queues have been initialized
and started. After initializing the MAIL$BATCH queue as described
in the previous step, execute the command
$ @SYS$STARTUP:pmdf_submit_jobs.comand then add this command to your system startup procedure. Again, in your system startup procedure, this command procedure must be executed after executing
pmdf_startup.com and after all PMDF
service queues have been initialized and started. If you want this
command procedure to run as a SYSMAN startup task, you can use the
SYSMAN STARTUP ADD FILE command to enter it into the SYSMAN database.
If using SYSMAN, be sure to execute pmdf_submit_jobs.com
in a late startup phase, after your queues are started.
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.
$ IF F$EDIT(F$GETJPI("","USERNAME"),"TRIM") .EQS. "pmdfacct" THEN EXIT
at the beginning of the system login command procedure.
pmdfacct is the name of the PMDF server account
you previously selected. 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.
$ INITIALIZE/QUEUE/START/DEVICE=SERVER/NOENABLE_GENERIC - /PROCESSOR=PMDF_PROCESS_SMB/PROTECTION=(S:RWE,O:RWD,G:R,W:R) PMDF_1$ INITIALIZE/QUEUE/START/DEVICE=SERVER/NOENABLE_GENERIC - /PROCESSOR=PMDF_PROCESS_SMB/PROTECTION=(S:RWE,O:RWD,G:R,W:R) PMDF_2$ INITIALIZE/QUEUE/START/DEVICE=SERVER/NOENABLE_GENERIC - /PROCESSOR=PMDF_PROCESS_SMB/PROTECTION=(S:RWE,O:RWD,G:R,W:R) PMDF_3$ INITIALIZE/QUEUE/START/DEVICE=SERVER/NOENABLE_GENERIC - /PROCESSOR=PMDF_PROCESS_SMB/PROTECTION=(S:RWE,O:RWD,G:R,W:R) PMDF_4$ INITIALIZE/QUEUE/START/DEVICE=SERVER/GENERIC=(PMDF_1,PMDF_2,PMDF _3,PMDF_4) - /PROTECTION=(S:RWE,O:RWD,G:R,W:R) MAIL$BATCHOr if you prefer to instead use a regular batch queue for PMDF processing, you may instead execute a command such as
$ INITIALIZE/QUEUE/START/BATCH/BASE_PRIORITY=4/JOB_LIMIT=4 MAIL$BATCH