home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!utcsri!newsflash.concordia.ca!garrot.DMI.USherb.CA!uxa.ecn.bgu.edu!psuvax1!psuvm!auvm!INNOSOFT.COM!DAN
- Errors-to: epmdf@YMIR.BITNET
- X-Envelope-to: PMDF-L@IRLEARN.BITNET
- X-VMS-To: IN%"martinez@iris-dcp.es"
- X-VMS-Cc: IPMDF
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GR9Q5I216Q8ZHQN5@YMIR.CLAREMONT.EDU>
- Date: Wed, 18 Nov 92 05:15:10 GMT
- Sender: PMDF Distribution List <PMDF-L@IRLEARN.BITNET>
- From: "Daniel C. Newman" <DAN@INNOSOFT.COM>
- Subject: RE: Help: mapping file for VMS addresses
- Newsgroups: bit.listserv.pmdf-l
- Lines: 58
-
- > According to the manual, I have created a PMDF_MAPPING_FILE that reads
- >
- > ...
- >
- > PMDF-TO-VMSMAIL
- >
- > PSI$%IBERPAC.* PSI$%ARTIX.$0$>
- >
- > ...
-
- There are two typos in the documentation. First, notice how the second
- paragraph of item 2. gives the table name as "PMDF-TO-VMSMAIL" although the
- discussion is "VMSMAIL to PMDF" and the example table shows "VMSMAIL-TO-PMDF"?
- Well, the correct table name is indeed "VMSMAIL-TO-PMDF".
-
- Now, notice how in the second paragraph the format
-
- channel_name|address
-
- is given. However, the example does not use this format. Well, in this
- regard the example is incorrect.
-
- So, your table should look like
-
- VMSMAIL-TO-PMDF
-
- d|PSI$%IBERPAC.* PSI%ARTIX.$0$>
-
- Do not use "$%" in the right hand side. It isn't obvious that you shouldn't
- do this. I'll look into making PMDF V4.2 treat $% and $* in the right hand
- side as % and *.
-
-
- You can test your mapping as follows:
-
- $ pmdf test/mapping
- Enter mapping name: VMSMAIL-TO-PMDF
- Input string: d|PSI%IBERPAC.xxx
- Output string: PSI%ARTIX.xxx
- Output flags: [0,62]
- Input string: ^Z
- $
-
- Note that if you use a compiled configuration, then you must recompile
- and reinstall before your mapping file (or changes to it) will be seen by PMDF.
- If you have PMDF V4.1-6 or earlier, two bugs prevent you from being able to
- use mapping files with compiled configurations. If you have 4.1-7, then use
- the command
-
- $ PMDF CNBUILD/OPTION
-
- to compile your configuration. If you have 4.1-8 or later, then none of these
- problems affect you. You can type out the file PMDF_ROOT:[EXE]IDENT.OPT to
- determine which revision level of PMDF you have. If you have 4.1-6 or earlier,
- and are using a compiled configuration, then let me know and we will arrange
- to get you an updated tape.
-
- Dan
-