PMDF Installation Guide
OpenVMS Edition
PMDF-INST-VMS-6.0

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.

• If PMDF was installed on a running cluster, the image SYS$LIBRARY:dcltables.exe must be reinstalled manually across the cluster using the command:

  $ INSTALL REPLACE SYS$LIBRARY:dcltables.exe
  

  In 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.
  
• If you are installing PMDF on multiple systems in a mixed architecture cluster, or in a cluster with system with multiple system disks, you should execute the PMDF_COM:post_install.com procedure on a system of the "other" architecture, or on each system having a distinct system disk.
  
• Two command files are created by the installation procedure and stored in the SYS$STARTUP directory. The first file, 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.com
  

  The 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 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 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.
  
• If this is a new installation on an additional system clustered with a system already running PMDF, that is, a new installation on a system which will share a configuration with an already installed and running PMDF, then if you use a compiled PMDF configuration on the old PMDF system, you will want to install the compiled PMDF configuration on this new system. (If this is a system which will have its own PMDF configuration, this step does not apply.) If the configuration you wish to use is already compiled for the current PMDF version for the architecture (VAX or Alpha) of the system you are newly installing on, you may simply install it with the command:

  $ INSTALL CREATE PMDF_CONFIG_DATA/OPEN/SHARED/HEADER
  

  If 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
  

  
  
• You must initialize and start a MAIL$BATCH queue and optionally additional service queues for PMDF processing. Such queues may be regular batch queues or, as is recommended, PMDF Process Symbiont queues to cut down on process creation overhead. The queues must be initialized and started before the second command file mentioned above, 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., ⁴

  $ 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.
  The PMDF CONFIGURE QUEUES utility creates four files in the SYS$STARTUP directory. 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 .
• The second command file created during the installation, 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.com
  

  and 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 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.

  ---

  
  
• Create PMDF's site specific configuration files using the automatic configuration generation utility. Refer to Chapters 5 and 6 (PMDF-MTA regular configuration), or to Chapters 27 and 28 (PMDF-MTA firewall configuration), or to Chapters 7 and 8 (PMDF-ACCESS configuration), for information, step-by-step procedures, and a example configuration.
  
• Once you have generated an initial configuration, you should take whatever steps are needed to complete the configuration of PMDF. The automatic configuration generator produces a check list which details any additional steps required to complete the configuration of PMDF.
  
• PMDF-MTA includes a facility called DELIVER, which is an adjunct to VMS MAIL that makes it possible for incoming mail messages to be handled and processed automatically based on information provided in a user supplied file. This integrated version of DELIVER obsoletes an older, standalone version of DELIVER that ran independently of PMDF. If your site had previously been using the older, standalone version of DELIVER, you may have commands to set up DELIVER in your system startup command file. These commands should be removed. You should change references to DELIVER% to IN% format. See the PMDF System Manager's Guide and the PMDF User's Guide, OpenVMS Edition for details on the integrated DELIVER component of PMDF.
  
• If you use the system login command procedure, SYS$SYLOGIN, you probably do not want it to perform its normal action when the PMDF server account logs in. You can avoid this by putting the line:

  $ 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 CREATE
  

  In either case the images specified by pmdfimage.dat will be reinstalled, but this will not hurt anything.
  
• Versions of the DEC 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. Digital Equipment Corporation has given Innosoft 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 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.
  
• If you also installed PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MB400, PMDF-MR, PMDF-X400, or PMDF-XGS, or if you will be using PMDF-MSGSTORE or PMDF-POPSTORE, then you should configure them now. Configuration instructions for PMDF-MSGSTORE and PMDF-POPSTORE may be found in Chapters 11 and 12 . Configuration instructions for PMDF-FAX may be found in Chapters 15 and 16 ; configuration instructions for PMDF-LAN may be found in Chapters 13 and 14 ; configuration instructions for PMDF-MB400 may be found in Chapters 17 and 18 ; configuration instructions for PMDF-MR may be found in Chapters 19 and 20 ; configuration instructions for PMDF-X400 may be found in Chapters 21 and 22 ; configuration instructions for PMDF-XGS may be found in Chapters 23 through 26 .

  ---

  Note

  ⁴ Using PMDF Process Symbiont queues significantly reduces process creation overhead in general, and in particular for sites using PMDF-MR allows for immediate pick up of messages from Message Router. The commands to initialize and start a generic MAIL$BATCH queue feeding four PMDF Process Symbiont execution queues would be

  $ 
  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$BATCH

  Or 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

  ---

  ---

  Previous | Next | Contents