PMDF System Manager's Guide
PMDF-REF-6.0

Previous | Contents

8.2.1 Restarting specific components

Table 8-1 provides an overview of when specific components should be restarted. For restarting PMDF components, use the PMDF RESTART (OpenVMS) or pmdf restart (UNIX or NT) utility.

Table 8-1 Restarting components
Component Restart after changes to:
  • Circuit check
  • The PMDF configuration¹, especially (but not only) the circuit check configuration file
  • Dispatcher
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes
  • The PORT_ACCESS mapping table in the PMDF mapping file
  • On OpenVMS, the PMDF_TIMEZONE logical name's value
  • SMTP server
  • The PMDF configuration¹
  • The TCP/IP channel option file
  • New (replaced) PMDF databases²
  • HTTP server
  • The HTTP server configuration file, http.cnf
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes for changes affecting the HTTP service definition
  • The HTTP_ACCESS mapping table in the PMDF mapping file
  • Add the filter, destinationfilter, sourcefilter, or related channel keywords to a channel, or create a new system wide filter file
  • IMAP server
  • The IMAP server configuration file, imapd.cnf
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes for changes affecting the IMAP service definition
  • Initial creation of the PMDF password database
  • Conversion from PMDF V5.0 or earlier password database format to PMDF V5.1 and later format
  • On UNIX, initial creation of the PMDF profile database
  • The PMDF configuration¹ as it relates to the IMAP server, particularly:
    • The security configuration file
    • The PORT_ACCESS mappings authentication control features
    • On OpenVMS, certain channel keyword changes on the local channel definition
  • POP server
  • The POP server configuration file, pop3d.cnf
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes for changes affecting the POP3 service definition
  • Initial creation of the PMDF password database
  • Conversion from PMDF V5.0 or earlier password database format to PMDF V5.1 and later format
  • On UNIX, initial creation of the PMDF profile database
  • The PMDF configuration¹ as it relates to the IMAP server, particularly:
    • The security configuration file
    • The PORT_ACCESS mappings authentication control features
    • On OpenVMS, certain channel keyword changes on the local channel definition
  • POPPASSD server
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes for changes affecting the POPPASSD service definition
  • Initial creation of the PMDF password database
  • Conversion from PMDF V5.0 or earlier password database format to PMDF V5.1 and later format
  • The PMDF configuration¹ as it relates to the POPPASSD server, particularly:
    • The security configuration file
    • The PORT_ACCESS mappings authentication control features
  • Lotus Notes channel servers
  • The PMDF configuration¹
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes for changes affecting the LN service definitions
  • New (replaced) PMDF databases²
  • Lotus Notes channel option files
  • PMDF-XGS (SNADS) channel servers
  • The PMDF configuration¹
  • The Dispatcher configuration file, dispatcher.cnf, and files it includes for changes affecting the SNADS service definition
  • New (replaced) PMDF databases²
  • PMDF-XGS channel option files
OpenVMS only
  • Counters synchronization process
  • The PMDF_COUNTER_INTERVAL logical
  • Process Symbiont³
  • The Process Symbiont option file
  • New MR_* channels or changes in the user or daemon channel keyword clauses on MR_* channels
  • FAX_RECEIVE
  • The PMDF configuration¹, at least any changes affecting PMDF-FAX
  • The FAX_TO_DATA channel option file
  • MailWorks server, ALL-IN-1 Sender, ALL-IN-1 Fetcher 4 5
  • The PMDF configuration¹
  • MRIF channel option files
  • New (replaced) PMDF databases²
  • The PMDF_TIMEZONE logical name's value
  • Queue to e-mail symbiont³
  • The Q2EMAIL option file
  • User agents, e.g., PMDF MAIL, VMS MAIL, PMDF Pine
  • The PMDF configuration¹
  • New (replaced) PMDF databases²
  • The PMDF_TIMEZONE logical name's value
UNIX and NT
  • Job Controller
  • The Job Controller configuration files, job_controller.cnf and job_controller.cnf_site
UNIX only
  • X.400 TSAPD process
  • The isotailor file (located in the PMDF_TABLES directory), as after reconfiguring PMDF-X400 to use a different transport

¹Here the PMDF configuration comprises the base PMDF configuration files or compiled configuration, i.e., the PMDF configuration, alias, mappings, conversion, option, system wide filter, and security configuration files.
²While a new version of a PMDF database requires restarting PMDF components--- for instance, a new version of the PMDF alias database requires restarting the SMTP server in order for the SMTP server to see the new version---a database updated "in place", via for instance the PMDF CRDB/APPEND (OpenVMS) or pmdf crdb -append (UNIX and NT) command does not require restarting any components, particularly not the SMTP server.
³To restart symbionts, use DCL commands: STOP/QUEUE/RESET and START/QUEUE.
4When using PMDF-MR in MR TS replacement mode; restarting MR application servers is not necessary when using PMDF-MR to connect to a real Message Router.
5Must be restarted using the server's own restart mechanism.

Previous | Next | Contents