Example 16-1 and Example 16-2 configure configures a PMDF-MR gateway at EXAMPLE.COM on node NAPLES, and Example 16-3 shows the corresponding checklist file. This is the same sample site pictured in Figure 4-1 and configured by Example 4-1. Example 16-4 shows an example of building the DCF utility.

EXAMPLE's Message Router network consists of the two cluster nodes, MILAN and NAPLES, running a cluster-common Message Router configuration, as well as the remote Message Router node, named NOPMDF. MAILbus components in use include:

Message Router Node	MAILbus Component	Mailbox Name
NAPLES	ALL-IN-1	A1
NOPMDF	MAILworks	AM
NAPLES	MR/X.400	MRX
NOPMDF	MR/PROFS	MRP

All four Message Router components will be given a unique domain name so that they can all be reached without explicit routing in the addresses. In addition, EXAMPLE has installed and configured PMDF-FAX and PMDF-X400 and chooses to provide specific Message Router mailboxes for each of these PMDF layered products.

EXAMPLE.COM also has another node, nomr.example.com, which does not have Message Router, but on which they would like to run ALL-IN-1 and MAILworks; to do this, they will use the Message Router Transport Service replacement capability of PMDF-MR. Assuming that PMDF-MTA and PMDF-MR have been installed on nomr.example.com, and that PMDF-MTA has been configured on nomr.example.com, then Example 16-5 shows a sample dialogue for configuring PMDF-MR on nomr.example.com, while Example 16-6 shows a corresponding checklist file.

PMDF-MR is configured using the PMDF CONFIGURE MR utility. The procedure will prompt for information specific to your installation of PMDF, PMDF-MR, and Message Router. Whenever appropriate, each prompt supplies a default answer which is enclosed within square brackets. Simply pressing return, [RETURN], selects the default answer.

Remember that the values in these samples are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual configuration.

Note that the procedure produces several output files that reflect your PMDF-MR configuration. You have the option of choosing different file names for these output files. The default names, however, are the names that are required for a running PMDF-MR configuration. Supply alternate names if you want to examine the results of different inputs without affecting your running PMDF-MR.

Example 16-1 Example PMDF-MR Configuration, Part 1

$ SET DEFAULT PMDF_TABLE: $ PMDF CONFIGURE MR PMDF-MR Configuration Utility, Version 6.2 This utility creates an initial pair of databases for mapping PMDF RFC 822-style addresses to Message Router X.400-style addresses and back again. Use this utility to assign RFC 822-style domain names to your Message Router user agents and gateways so that they can interoperate with all of your other PMDF channels. At various stages of this procedure you will need to supply RFC 822-style domain names. Be sure that the names you choose are within a domain or subdomain over which you have administrative authority, and are not currently being used for anything else. Important note: No changes are made to existing PMDF-MR database information until all questions have been answered. This utility can be aborted at any prompt by entering a CTRL/Z. The files output by this utility can optionally be redirected to a different location so they will have no impact on the existing PMDF-MR databases. You have a history file from a previous run of the configure utility. Do you want to use answers from the previous run as defaults [N]? [RETURN] Do you wish to continue [Y]? [RETURN] Do you wish to have a detailed explanation printed before each question [N]? y In addition to acting as a gateway to Message Router, PMDF-MR has the ability to act as a replacement for Message Router for any agent that is built using the MRIF API interface. Agents using this interface include: ALL-IN-1 Integrated Office System V3.0 or later/Office Server [A1] MAILworks Server for OpenVMS (aka ALL-IN-1 Mail) [AM] Properly implemented Message Router gateways from non-HP vendors can be supported as well. This capability is especially useful on AXP systems, where native Message Router support is not available. This phase of this procedure will generate the necessary channel definitions and option files. This is equivalent to defining mailboxes using the MRMAN utility. If you need Message Router emulation facilities you should enter YES, otherwise enter NO. Do you wish to set up any Message Router replacement mailboxes [N]? n A standard domain-style host name is used to refer to the PMDF-MR gateway from the Internet/822 side. Message Router addresses then appear relative to this gateway on the Internet/822 side. For example, if you choose a domain name like MR.EXAMPLE.COM for the gateway, an address of the form USER%A1@MR.EXAMPLE.COM might be used from the Internet/822 side to send messages to local ALL-IN-1 users. The choice of the MR.domain format is a common one. Be sure that the name you choose is within a domain or subdomain that you have administrative authority over. In any case, be sure to choose a name that is NOT currently in use. Domain name of the PMDF-MR gateway []? mr.example.com A Message Router mailbox is used by the PMDF-MR to receive messages from Message Router. This mailbox will appear as routing information in Internet/822 addresses on the Message Router side of the gateway. For example, if the mailbox chosen is PMDF (the default), the Internet address DOE@NAPLES.EXAMPLE.COM would appear to MRGATE as MRGATE::PMDF::"DOE@NAPLES.EXAMPLE.COM" and to ALL-IN-1 Electronic Messaging as DOE@NAPLES.EXAMPLE.COM@PMDF Message Router mailbox name for the gateway [PMDF]? PMDF Enter the password associated with this gateway's Message Router mailbox. Message Router protects each mailbox with a password. These passwords should not be public information since they are the primary means of controlling access to Message Router mailboxes. Password for PMDF's Message Router mailbox []? secret PMDF-MR supports many different Message Router User Agents and Gateways in the MAILbus product family, including (but not limited to): ALL-IN-1 Integrated Office System or Office Server [A1] MAILworks Server for OpenVMS (aka ALL-IN-1 Mail) [AM] Message Router X.400 Gateway (aka MRX) [MRX] Message Router/SNADS Gateway (aka MR/S) [MRS] Message Router/PROFS Gateway (aka MR/P) [MRP] VMS MAIL Gateway (aka MRGATE) [MRGATE] Properly implemented Message Router gateways from non-HP vendors are supported as well, including (but not limited to): MBLINK Message Router to cc:Mail Gateway [CCGATE] SoftSwitch Message Router Gateway [SSW] AlisaMail Message Router Gateway [MRAM] [Type RETURN for more]: [RETURN] NOTE: In the above product lists, common or default Message Router mailbox names for each product are provided at the far right, within the square-brackets. Note that products installed at particular sites might very well use different mailbox names. You will need to be familiar with your own Message Router configuration in order to configure PMDF-MR support for these and other User Agents and Gateways. Some Message Router gateways, including MRX, MR/S, MR/P, require specific support from PMDF-MR. This procedure will explicitly prompt for MRX, MR/S, and MR/P support in a later phase. This phase of this procedure will generate support for those Message Router gateways and user agents that require only ROUTE and USERID fields within Message Router addresses. Those products which are known to fall into this category include A1, AM, MRGATE, CCGATE, SSW, and MRAM. If you need to access any such Message Router user agents or gateways from PMDF-MR you should enter YES, otherwise enter NO. Do you wish to assign domain names to Message Router mailboxes [Y]? y Enter a domain name to be associated with a particular Message Router User Agent or Gateway mailbox. Each Message Router User Agent or Gateway mailbox needs to have its own unique domain name so that PMDF-MR can recognize it on incoming mail. If there are no more User Agent or Gateway mailboxes then just hit RETURN. Domain name for one MR mailbox [RETURN if no more]? a1.example.com Enter the Message Router mailbox name for the User Agent or Gateway that corresponds to the previous domain name. If the MR mailbox is on a different node it can be entered in the form MAILBOX@NODENAME. Path corresponding to previous domain name in MAILBOX@NODE format []? A1 Domain name for one MR mailbox [RETURN if no more]? am.example.com Path corresponding to previous domain name in MAILBOX@NODE format []? AM@NOPMDF Domain name for one MR mailbox [RETURN if no more]? [RETURN] PMDF-MR is capable of handling MRX addresses specially. In particular, MRX addresses require that attributes be encoded into the actual route rather than being present as ordinary attributes. If you have any MRX gateways you want to access from PMDF-MR you should say YES, otherwise enter NO. Do you have one or more MRX gateways you wish to access [N]? y Enter a domain name to be associated with a given MRX mailbox. Each MRX mailbox needs to have its own unique domain name so PMDF-MR can recognize it on incoming mail. If there are no more MRX mailboxes just hit RETURN. Domain name for one MRX gateway [RETURN if no more]? mrx.example.com Enter the MRX mailbox that corresponds to the previous domain name. If the MRX mailbox is on a different node it can be entered in the form MAILBOX@NODENAME. Path corresponding to previous domain name in MAILBOX@NODE format []? MRX Domain name for one MRX gateway [RETURN if no more]? [RETURN] PMDF-MR is capable of handling MR/S addresses specially. In particular, MR/S addresses require that attributes that must be encoded into the route; they are not part of the regular attribute set. If you have any MR/S gateways you want to access from PMDF-MR you should say YES, otherwise enter NO. Do you have one or more systems behind MR/S gateways you wish to access [N]? n PMDF-MR is capable of handling MR/P addresses specially. In particular, MR/P addresses require that attributes that must be encoded into the route; they are not part of the regular attribute set. If you have any MR/P gateways you want to access from PMDF-MR you should say YES, otherwise enter NO. Do you have one or more systems behind MR/P gateways you wish to access [N]? y Enter a domain name to be associated with a given MR/P gateway. Each MR/P gateway needs to have its own unique domain name so PMDF-MR can recognize it on incoming mail. More than one PROFS system can be associated with any single gateway. If there are no more MR/P mailboxes just hit RETURN. Domain name to associate with an MR/P gateway [RETURN if no more]? profs.example.com Enter the Message Router mailbox mailbox that corresponds to the previous MR/P gateway domain name. If the MR/P mailbox is on a different node it can be entered in the form MAILBOX@NODENAME. Path to the MR/P gateway associated with this domain in MAILBOX@NODE format []? MRP@NOPMDF Enter the name of the PROFS system that should be used as a default if no other name is specified in an address. Name of the default PROFS system []? bigblue Domain name to associate with an MR/P gateway [RETURN if no more]? [RETURN] The FAX domain name is the domain name PMDF-FAX uses for sending plain text e-mail to FAX. Normally this is the domain name defined for this purpose when FAX_CONFIGURE.COM is run. Making this domain name known to PMDF-MR makes it possible to use more convenient and conventional address formats to send to PMDF-FAX. For example, when PMDF-MR is made aware of this domain name, a FAX address in ALL-IN-1 MAIL might look like this: *fn\15085551212@*o\Example@*at\John Doe@FAX This address actually conforms rather closely to the conventions for X.400 addresses in ALL-IN-1 MAIL. But without the special conversion rules an address like this would be required: "/FN=15085551212/O=Example/AT=John Doe/"@text-fax.local-domain@PMDF There is nothing wrong with this address; however, it is overly complex and it is not in a format natural to ALL-IN-1 MAIL. This domain name is optional; if you just hit RETURN no special handling for FAX addresses will be set up. Do not define this domain name for use in conjunction with anything other than PMDF-FAX; the processing done is quite specific to PMDF-FAX. Domain name for PMDF-FAX plain text []? text-fax.example.com A special Message Router mailbox is used to receive messages destined for PMDF-FAX. PMDF-MR recognizes this mailbox and handles it specially, rewriting addresses referencing it into a format acceptable to PMDF-FAX. In effect, this mailbox is associated automatically with the domain name previously established for PMDF-FAX. The default mailbox name is FAX. Press RETURN and this name will be used automatically. A different name can be used if desired. PMDF-FAX mailbox to be made known to Message Router [FAX]? FAX The X400 domain name is the domain name PMDF-X400 uses for sending X.400 messages. Normally this is the domain name defined for this purpose when X400_CONFIGURE.COM is run. Making this domain name known to PMDF-MR makes it possible to use more convenient and conventional address formats to send to PMDF-X400. This domain name is optional; if you just hit RETURN no special handling for X.400 addresses will be set up. Do not define this domain name for use in conjunction with anything other than PMDF-X400; the processing done is quite specific to PMDF-X400. Domain name for PMDF-X400 []? x400.example.com A special Message Router mailbox is used to receive messages destined for PMDF-X400. PMDF-MR recognizes this mailbox and handles it specially, rewriting addresses referencing it into a format acceptable to PMDF-X400. In effect, this mailbox is associated automatically with the domain name previously established for PMDF-X400. The default mailbox name is X400. Press RETURN and this name will be used automatically. A different name can be used if desired. PMDF-X400 mailbox to be made known to Message Router [X400]? X400 The printer channel domain name is the official host name associated with the printer channel defined in the PMDF configuration file. Making this domain name known to PMDF-MR makes it possible to use more convenient and conventional address formats to send to the printer channel. This domain name is optional; if you just hit RETURN no special handling for printer channel addresses will be set up. Do not define this domain name for use in conjunction with anything other than a PMDF printer channel; the processing done is quite specific to the PMDF printer channel. Domain name associated with the PMDF printer channel []? [RETURN] One or more Message Router mailboxes can be explicitly specified in an 822-style source route or percent hack. The gateway will convert such routes into one or more Message Router routing mailboxes automatically. However, the case where no routing information is specified must also be accommodated. A Message Router mailbox must be specified for use in this case. Press RETURN to use the default of MRGATE, which is the mailbox used by the Message Router VMS MAIL gateway. Message Router mailbox used by default [MRGATE]? [RETURN] Message Router establishes a mailbox name for the local system. This is used to generate address routes that are valid from remote systems. This name is usually the DECnet node name of your machine. Please enter this name; this gateway uses it to generate addresses that will be valid on remote machines. If you are using a remote Message Router, i.e. this system is not running Message Router, then the answer should be the name of the remote Message Router's mailbox. System's Message Router mailbox [NAPLES]? NAPLES Message Router routing information often includes local DECnet node names, cluster aliases, and other routing material which is simply stripped from addresses by local Message Router route processing. The MRMAN utility's SHOW * command can be used to find such routing entries; they have the general form: NULLNAME, Replace= (I.e. there is nothing to the right of the equals sign.) In most applications this sort of material should also be stripped from addresses during the address translation process. Enter any such routing entries you want stripped from addresses, one at a time. A blank entry terminates the list. If you are using a remote Message Router, then enter the information from the SHOW * command on that system. Local node name or other null routes [RETURN if no more]? MILAN Local node name or other null routes [RETURN if no more]? [RETURN] Message Router free form names (FFNs) are often used to store the full name of each user. In the RFC822 world personal name fields serve a similar function. Enter YES to have free form names converted to personal names. Entering NO blocks this conversion. (Note that both free form names and personal names are only included for legibility; they have no effect on the function of the address.) Convert Message Router Free Form Names to RFC822 personal names [Y]? [RETURN] Message Router telephone numbers (TNs) are often used to store user phone numbers. In the RFC822 world personal name fields are often used in this way. Enter YES to have telephone numbers converted to personal names. Entering NO blocks this conversion. (Note that both telephone numbers and personal names are only included for legibility; they have no effect on the function of the address.) Convert Message Router phone numbers to RFC822 personal names [Y]? [RETURN] Message Router free form names (FFNs) are often used to store the full name of each user. In the RFC822 world personal name fields serve a similar function. Enter YES to have 822 personal names converted into Message Router free form names automatically. Note that this might improve the display of PMDF-MR messages in ALL-IN-1, which in some contexts only displays the free form name and not the rest of the address. Convert 822 personal names into Message Router Free Form Names [Y]? [RETURN] Message Router free form names (FFNs) are often used to store the full name of each user. In the RFC822 world personal name fields normally serve a similar function. However, due to the problems some mailers have handling personal names, RFC822 comments are sometimes used for personal name information. This convention unfortunately conflicts with other uses for comments, notably as a means of transferring per-address attribute information. Enter YES to have RFC822 comment strings converted to free form names automatically. This will only be done after any configured attempts to convert personal name information have been tried and failed. Convert 822 comments into Message Router Free Form Names [N]? [RETURN] Message Router organization names (Os) are often used to store the name of the organization the address is from. In the RFC822 world the nonstandard Organization: header performs a similar function for message From: addresses. Enter YES to have the organization specified in the From: address converted into an Organization: header. Entering NO blocks this conversion. (Note that this header is only included because it is convenient for users; it has no other effects.) Retain organization specification in From: address as Organization: header [Y]? y The PMDF address of the local PostMaster is used when blank addresses (which are allowed in RFC822 but not in X.400) are encountered that must be converted into Message Router addresses. Please enter a full domain address for the local PostMaster. Do not use shortform host names since there is no guarantee that the address will be interpreted in the context where the shortform name is valid. RFC822 address of local PostMaster []? system@example.com On VAX, this gateway can flatten WPS-PLUS and DX messages into ASCII using a special utility. This utility is built from libraries provided as part of various Message Router product sets, notably the Message Router VMS Mail Gateway (MRGATE). If you intend to link this Document Conversion Facility (DCF) utility to convert messages in these special formats to ASCII, answer YES. If you answer NO, WPS-PLUS and DX message bodyparts will not be converted. IMPORTANT NOTE: The above described DCF facility is available ONLY on the VAX architecture. For Alpha AXP systems running PMDF-MR, you must answer NO to this question. In that case (or if you prefer on VAX) the following will apply: If not converted to ASCII, WPS-PLUS and DX message bodyparts will be extracted and labelled appropriately for MIME. You can then use a PMDF CONVERSION channel together with document conversion software such as CDA Library or KeyPAK to perform more comprehensive conversion than flattening to ASCII text. Flatten WPS-PLUS and DX messages to ASCII automatically [N]? y The rest of this configuration dialogue is shown in Example 16-2.

Example 16-2 Example PMDF-MR Configuration, Part 2

This continues the configuration dialogue started in Example 16-1. Enter the name of the file to which the text form of the PMDF to MR mapping should be written. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. PMDF to MR mapping text file [PMDF_ROOT:[TABLE]TO_MR.TXT]? [RETURN] Enter the name of the file to which the text form of the MR to PMDF mapping should be written. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. MR to PMDF mapping text file [PMDF_ROOT:[TABLE]FROM_MR.TXT]? [RETURN] This procedure generates an options file that contains the Message Router gateway mailbox and password. This file is read by the gateway as it initializes and provides the information needed to connect to Message Router. WARNING: This file contains password information and should be protected against world read access! Gateway options file [PMDF_ROOT:[TABLE]MR_LOCAL_OPTION.]? [RETURN] Enter the name of the file to output the database form of the PMDF to MR mapping to. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. This file name must agree with the PMDF_TO_MR_DATABASE logical for it to be employed by the gateway. PMDF to MR mapping database [PMDF_ROOT:[TABLE]TO_MR.DAT]? [RETURN] Enter the name of the file to output the database form of the MR to PMDF mapping to. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. This file name must agree with the PMDF_FROM_MR_DATABASE logical for it to be actually used by the gateway. MR to PMDF mapping database [PMDF_ROOT:[TABLE]FROM_MR.DAT]? [RETURN] Enter the name of the file to contain the PMDF configuration rewrite rules created by this procedure. This file should subsequently be included in your PMDF configuration file. Rewrite rules text file [PMDF_ROOT:[TABLE]MR.RULES]? [RETURN] Enter the name of the file to write the channel block definition for the PMDF-MR channel to. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. Channel definitions text file [PMDF_ROOT:[TABLE]MR.CHANS]? [RETURN] This procedure generates a checklist file that contains the list of actions you must perform in order to make the PMDF-MR gateway operational. This procedure does *NOT* perform these operations itself; you must do them manually. PMDF-MR checklist file name [PMDF_ROOT:[TABLE]MR.CHECKLIST]? [RETURN] All configuration questions have been answered. This question gives you a last chance to change your mind before any files are written. Answer NO if you are not sure you want to generate the configuration you have specified. Answer YES if you do. Do you wish to generate the configuration files [Y]? Y Generating PMDF to MR mapping text file... PMDF to MR mapping text file is complete. Generating MR to PMDF mapping text file... MR to PMDF mapping text file is complete. Generating the MR.RULES file... MR.RULES file is complete. Generating the MR.CHANS file... MR.CHANS file is complete. Generating the setup checklist... Checklist file is complete. Converting the PMDF to MR mapping text file to a database... Entries converted: 112 Exceptions generated: 0 Entries too long to fit: 0 PMDF to MR mapping conversion is complete. Converting the MR to PMDF mapping text file to a database... Entries converted: 324 Exceptions generated: 0 Entries too long to fit: 0 MR to PMDF mapping conversion is complete. Generating options files... Options files are complete. *********************************************************************** * * To complete your PMDF-MR configuration, carry out the steps * detailed in the setup checklist PMDF_ROOT:[TABLE]MR.CHECKLIST;. * *********************************************************************** Enter Yes if you want to see the checklist now. You can still type the file out later if you say No. Do you want to see the checklist now [Y]? n $

Example 16-3 Example Checklist File for PMDF-MR Configuration

$ TYPE mr.checklist Checklist for setting up your PMDF-MR gateway. Written by SYSTEM, 1-NOV-2002 15:23 This file was created by the PMDF-MR configuration generator V6.2. (1) Add the gateway mailbox or mailboxes to your Message Router configuration: $ RUN SYS$SYSTEM:MRMAN MRM> add "PMDF"/owner=SYSTEM/suppress/ignore/service/password=secret MRM> add "FAX"/replace="FAX@PMDF" MRM> add "X400"/replace="X400@PMDF" If you are using the PMDF Process Symbiont for immediate notifications, then also do MRM> modify "PMDF"/notify=PMDF_MR_NOTIFY If you are not using the PMDF Process Symbiont, you should be. Be sure to read the chapter on setting up the Process Symbiont. If you are configuring PMDF-MR to connect via DECnet to a remote Message Router (that is, PMDF-MR and Message Router are not running on the same node or cluster) then also do MRM> modify "PMDF"/NOOWNER Also define the logical name PMDF_MR_NOTIFY on the remote node running Message Router like this: $DEFINE/SYSTEM PMDF_MR_NOTIFY "node::""TASK=PMDF_MR_NTFY""" where node is the DECNET node name of the system running PMDF (2) Build the DCF utility by executing the procedures: $ @PMDF_COM:DCF_EXTRACT.COM $ @PMDF_COM:DCF_BUILD.COM Refer to the PMDF-MR chapter in PMDF System Manager Manual for more details on building the DCF facility. (3) Add the contents of the MR.RULES file to the existing set of rewrite rules in your PMDF configuration file by adding the line <PMDF_ROOT:[TABLE]MR.RULES to the rewrite rules section of your PMDF.CNF file; it should be be added before any general TCP/IP rewrite rules (e.g., .COM, .EDU, etc. normally included as <PMDF_TABLE:INTERNET.RULES). It should start in column one with no surrounding blank lines added by you. Note: if you find the lines ! ! Rewrite rules for PMDF-MR ! !<PMDF_TABLE:MR.RULES around the middle of your PMDF.CNF file, merely uncomment the line "!<PMDF_TABLE:MR.RULES" and, if necessary, change the file name so that it reads ! ! Rewrite rules for PMDF-MR ! <PMDF_ROOT:[TABLE]MR.RULES (4) Include the channel definition in your configuration file by adding the line <PMDF_ROOT:[TABLE]MR.CHANS to the very end of your PMDF_TABLE:PMDF.CNF file; it should start in column one and be preceded by a single blank line. Note: if you find the lines ! ! PMDF-MR channels ! !<PMDF_TABLE:MR.CHANS towards the end of your PMDF.CNF file, merely uncomment the "!<PMDF_TABLE:MR.CHANS" line and, if necessary, change the file name so that it reads ! ! PMDF-MR channels ! <PMDF_ROOT:[TABLE]MR.CHANS If your Message Router is not running on this node, then edit PMDF_TABLE:MR.CHANS and add the continuation character \ at the end of the line starting with mr_local, and add the line DAEMON nameofnode as the next line. Use the name of the node running Message Router where nameofnode is shown. (5) If you are running a domain name system (DNS) nameserver, you will need to insert MX or A record(s) for the gateway into your database, the MX record(s) should point to your PMDF system. If you are using host tables, make sure to add host aliases for the gateway. The names to be added are: mr.example.com a1.example.com am.example.com (6) If you have not set up PMDF Process Symbiont queues already you need to set them up following the instructions in the Process Symbiont chapter of the PMDF System Mananger's Guide. If you already have PMDF Process Symbiont queues, then stop all PMDF processing queues using a command of the form: $ stop/queue/reset QUEUE-NAME where QUEUE-NAME is the name of any one of the PMDF Process Symbiont queues. The STOP/QUEUE/RESET will stop them all. You then need to start each of the PMDF processing queues using a START/QUEUE command for each one. Restarting these queues ensures that the PMDF Process Symbiont uses the new configuration information so that it properly handles Message Router notifications. (7) For proper handling of attachments, you should consider enabling mappings such as those demonstrated in the sample file PMDF_TABLE:MR_MAPPINGS.SAMPLE. To enable these mappings, you might start by cutting and pasting the contents of the sample file into the PMDF_TABLE:MAPPINGS. file. Modify the mapping entries, if necessary, to correspond to the Message Router label tags in actual use at your site. That's all!

Example 16-4 Example Build of the DCF Utility

$ SET DEFAULT PMDF_COM: $ @dcf_extract Directory to put libraries in: pmdf_root:[dcf] Path to saveset to extract libraries from: D0:[vmsinstal]mrgate032.a Extracting libraries... %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]KOALA.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]DCF_BASE.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]DCF_TRANSLATE.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]DCF_MAIL_CONVERSIONS.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]DCF_DSAF.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]WPADOC.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]WPABASE.OLB;1 %BACKUP-S-CREATED, created PMDF_ROOT:[DCF]XPORT.OLB;1 $ @dcf_build Directory containing object libraries: pmdf_root:[dcf] Linking DCF utility... $