HDTenEightyP/NetNews huggingface dataset:
From: dmpm%dukemc.bitnet@ymir.claremont.edu (James Dryfoos - Postmaster)
Newsgroups: vmsnet.mail.pmdf
Subject: Suggestion for DELIVER
Date: 28 Aug 92 16:16:25 GMT
Organization: Duke University Medical Center, Durham NC, USA
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 28 Aug 1992 11:16:25 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO3Y26M8F695OKYS@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I would like to use DELIVER to file certain message.
Problem I have is that we do a lot of MAIL-11 mail that we do not
want to go through PMDF.  When mail gets processed by DELIVER and
even if the rule says just put it in the NEWMAIL folder, it ends
up with the in% inducer on the front.  This means when I go to reply to it,
it goes through PMDF when I wish it would not.

All I am trying to feel out is, if an option that says do not modify
the message in any way (i.e. do not add the in% to the from address)
and just place it in NEWMAIL folder would be possible.


Thanks,

Jim
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF Process Symbiont problems
From: bthomas@drifter.uwyo.edu
Date: 01 Sep 1992 14:37:03 -0700
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 01 Sep 1992 14:37:03 -0700
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO9T8ANL3695O9DO@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


I converted our PMDF-MR gateway jobs from the old method of using
standard batch queues to using the PMDF process symbiont two days
ago. Starting today I have been getting the following sequence of
errors on the operator consoles:

%PMDF-W-PRCSMBWRN, PMDF process symbiont non-fatal warning
%PMDF-W-MRLSUBERR, Error submitting OMDF-MR for local mailbox "SMTP",
  status=178028674
-PMDF-E-HOST, Illegal host/domain in address "!AD"

Our Message Router mail box for PMDF-MR is "SMTP" instead of "PMDF"

The manual says that the error may be due to an incorrect PMDF-MR configuration.
I used MR-CONFIGURE to build the PMDF-MR configuration. PMDF-MR seems to still
work since jobs get started on the symboint queues and mail goes from MR to
PMDF (excluding a bug in PMDF-MR, Thanks for the quick answer on that Ned).

Did I miss something when I changed the queues or is something more required
in the PMDF-MR configuration to make this work?

-------------------------------------------------------------------------------
|   ####   ###  ##    |   Brad Thomas                                         |
|   ####   ###  ##    |   System Programmer                                   |
|   ####   ###  ##    |   Network Development Group                           |
|   ####   ###  ##    |   University of Wyoming                               |
|    ###    #   #     |   Bthomas@Outlaw.UWyo.Edu                             |
|     ###### ###      |   bthomas@drifter.uwyo.edu                            |
-------------------------------------------------------------------------------
From: dmpm%dukemc.bitnet@ymir.claremont.edu (James Dryfoos - Postmaster)
Newsgroups: vmsnet.mail.pmdf
Subject: More on (Any status returned by $ PMDF SEND command in 4.1?)
Date: 28 Aug 92 16:11:27 GMT
Organization: Duke University Medical Center, Durham NC, USA
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 28 Aug 1992 11:11:27 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO3WLVBGCI95OLLK@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>I would like to use PMDF SEND command under program control, but
>cannot find any sort of return status on failure (except for the text message).
>Is there anything like deliver_status and deliver$message in this facility?
>Even upon failure (such as bad address) $status is 1.
>This is a much needed feature.
>
>Thanks,
>
>Jim

I would like to change this a bit.  Some failures do result in an error in
$status.  However, my problem is:

%PMDF-E-ALLADDRBAD, All addresses specified are bad; message not sent
$ stat = $status        !Does $status return anything - no
$ sho sym stat
  STAT = "%X00000001"

-Jim
From: gdha@se.alcbel.be
Newsgroups: vmsnet.mail.pmdf
Subject: UUCP bang style addresses
Date: 25 Aug 92 08:08:17 GMT
Reply-To: gdha@se.alcbel.be
Organization: Alcatel Bell, Antwerpen, Belgium
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Aug 1992 08:08:17 +0000 (GMT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Return-Path: root@se
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNZI0XPQVM95O5K4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"alcbel-list-pmdf@alcbel.UUCP"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT



Dear PMDF-users,
		Could someone explain me how to use the bang style addresses (UUCP)
in a PMDF configuration file. I'm interested in the use of the pattern "$!", but
 do
not know how to use it.
Thanks in advance, Gratien
--
  _______ 		Gratien D'haese    Switching Systems Division  se121
  \     /Alcatel			  F. Wellesplein 1, B-2018 Antwerpen
   \   /  Bell		e-mail: gdha@se.alcbel.be    Phone: (32) 3 240 94 51
    \/ Telephone		gdha@alcbel.be 	     Fax:   (32) 3 240 99 50
From: dsroberts@beckman.com
Newsgroups: vmsnet.mail.pmdf
Subject: Justifying PMDF maintenance costs
Date: 27 Aug 92 10:19:43 PDT
Organization: Beckman Instruments

We've been using PMDF for a year now, and it's time to renew the contract.
There was a great deal of management resistance here to PMDF simply because the
maintenance cost more than the initial license, and management has been looking
for an excuse to get rid of it.  Mgmt was sold on the PMDF-MR capability, but
we have subsequently gotten rid of ALL-IN-1 and the need for PMDF-MR, so I am
in the painful position of having to justify PMDF all over again.  We'll dump
-mr, but I need justification to keep regular PMDF.  I've explained about 
the flexible addressing, DELIVER, and personal aliases, but so far am 
getting no budget.

My question for the list, how do you justify PMDF to your management when you
already have MultiNet's SMTP processing capabilities?  Do other managements
think personal aliases are enough, or is there more that I'm forgetting in
trying to justify continuing support for this product?  Has anyone put together
some justification documents for THEIR management?  Or maybe PMDF just isn't
necessary for us.
-- 
   Don Roberts                   Internet:  don@beckman.com
   Beckman Instruments, Inc.     Phone:     714/961-3029
   2500 Harbor Bl. Mailstop X-12 FAX:       714/961-3351
   Fullerton, CA  92634          Disclaimer:  Blame me, not Beckman.
   People are as happy as they decide to be - A. Lincoln
From: klensin@infoods.mit.edu (John C Klensin)
Newsgroups: vmsnet.mail.pmdf
Subject: RE:  vrfy and expn commands
Date: 26 Aug 92 11:28:17 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 26 Aug 1992 07:28:17 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO0W4DPNO295NWAQ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"WITTWER@tech.ascom.ch"
X-Vms-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Mail-System-Version: <VAX-MM(312)+TOPSLIB(155)+PMDF(4.1)@INFOODS.MIT.EDU>

Fritz,
  To add a bit to Ned's (correct) answer...
  -- Many versions of sendmail "implement" VRFY and EXPN identically
and, in both cases, simply do a syntax check.  In other words, if you
send "VRFY foo@bar" you get back "<foo@bar>" for any instance of "foo"
and "bar".  This behavior is broken, even if the "sendmail is the real
standard" community thinks otherwise.
  -- A few versions of sendmail implement VRFY identicially to EXPN, i.e.,
if you send them an address that points to a list, they pass back the
list expansion.  PMDF has, if I recall, a little bit of this behavior
relative to system aliases.  As far as I can tell from RFC821, VRFY should
be returning only one line of information that tells you whether the
mail will be accepted for, and delivered to, that address by that SMTP
server.  If that reading is correct, this is a bug, although rarely a
serious one.
  -- RFC 1123 makes explicit provision for the cases in which it is
not possible to fully verify an address because the SMTP server being
addressed will have to gateway or relay the mail (section 5.2.3) and
assigns a new code, 252, for that purpose.  My interpretation of the
intent here is that PMDF should probably be returning 252, rather than
250, when there is a remote address that cannot be verified.  On the
other hand, this is not what one would call a big deal.
  -- VRFY is an RFC821 facility.  It really has no business knowing
about personal names and should not be returning an address string that
cannot appear in a RCPT TO command.  So, if an implementation of
sendmail is returning personal names, that, too, is probably a bug or at
least a serious mis-feature.
  -- 250 is documented in RFC821

It is quite unfortunate, but the version of sendmail that has
traditionally been shipped with SUN OS, together with the default config
files shipped with it, are seriously broken and not suitable for use
with Internet mail.  Anyone who wants to think of that as "the standard"
should get used to communicating only with other Suns, and only over
LANs and considering themselves very fortunate when anything else works.

      john
From: ned@innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: UUCP bang style addresses
Date: 27 Aug 92 17:55:01 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 27 Aug 1992 09:55:01 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO2LSVCC7M95OE2Z@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"gdha@se.alcbel.be"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

The $! control sequence has nothing at all to do with UUCP paths. It
is used to extract a part of a domain specification.

The handling of bang paths is detailed in section 3.2.4.1 of the
manual (page 3-10). This is simply part of the overall strategy PMDF
uses to handle addresses; there is no special facility for handling these
sorts of addresses.

If you have a specific goal in mind (rather than the intent to use some
particular feature) please explain it in greater detail. Bang path
addresses work just like any other address format in PMDF; unless you're
trying to produce them for a UUCP connection there should be no reason
to handle them specially.

				Ned
From: dmpm%dukemc.bitnet@ymir.claremont.edu (James Dryfoos - Postmaster)
Newsgroups: vmsnet.mail.pmdf
Subject: Help:  Any status returned by $ PMDF SEND command in 4.1?
Date: 28 Aug 92 14:47:34 GMT
Organization: Duke University Medical Center, Durham NC, USA
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 28 Aug 1992 09:47:34 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO3TITMIPE95OK0Q@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I would like to use PMDF SEND command under program control, but
cannot find any sort of return status on failure (except for the text message).
Is there anything like deliver_status and deliver$message in this facility?
Even upon failure (such as bad address) $status is 1.
This is a much needed feature.

Thanks,

Jim
From: rickm@oregon.uoregon.edu (Rick Millhollin)
Newsgroups: vmsnet.mail.pmdf
Subject: PhoneNet Channel Problem
Date: 25 Aug 92 17:50:01 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Aug 1992 10:50:01 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO04EJLA4I95NH2F@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
X-Vms-Cc: rickm
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

One of our systems is the slave end of a PhoneNet channel, and since I upgraded
it to PMDF V4.1 this past weekend, the channel has not worked.  The slave log
contains a bunch of messages like:

25-AUG-92  10:14:10: Timeout on acknowledgement read, retransmitting

The PMDF.CNF stuff related to this channel and P_OPTIONS file are the same, and
I can't find anything different to explain the problem.  The other end is still
PMDF V4.0.  Can anybody help me with this?  Thanks...
From: ghc@vger.niddk.nih.gov (Gerson H Cohen)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Problem with personal aliases
Date: 25 Aug 92 18:49:43 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Aug 1992 14:49:43 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: IPMDF@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNZX8K4XPE95O8YP@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"NED@INNOSOFT.COM"
X-Vms-Cc: IPMDF,GHC
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Ned,

    I think thast you're hitting me pretty hard on this one.
While it may be documented that pmdf test is not appropriate
to use for personal aliases, I didn't know and stepped into
it.  It did seem reasonable - I'm sorry!

    I am not responsible for the condition of the miriad of
mishappen sendmails in the world.  Their purpose is just to
haunt us all.

    As for:

> Finally, I don't know what you expected to get, but this is the expected
> result when you use a persnoal alias that is marked private and noexpand.
> If you want the alias to expand into the real address just mark it expand
> and it will. If you want it to expand into an alias other people can use
> mark it public.

Again I have to plead ignorance.  I had to search for a while
[for the manual as well as for the answer] to understand what you
were saying.  I note that I could only use the resultant address
[when I used expand] if I set transport to in%.  I couldn't come
up with any suitable combination of quotes to get the address through.
Is that correct?

Gerson

-
Dr Gerson H Cohen
National Institutes of Health
Bldg 2, Room 312
Bethesda, MD  20892
'Phone: (301)496-4295
Internet: ghc@vger.niddk.nih.gov
BITNet:   ghc@nihklmb
From: linda Knutson; 802-388-3711 x5577
Newsgroups: vmsnet.mail.pmdf
Subject: need help will bounced mail
Date: 25 Aug 92 19:52:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Aug 1992 14:52 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNZXER3NW295O8L0@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"INFO-PMDF@YMIR.BITNET"
X-Vms-Cc: KNUTSON
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Can anyone be of help on a sticky problem of mine?  I frequently
get mail bounced to me as the postmaster coming from node
umichum.bitnet.  The mail is addressed to mailer@midd.bitnet
rather than a specific user.  The text of the messages indicate
to me that the sender was not intending the mail to go to some
vanilla postmaster type with the generic name of MAILER.  Why do
these messages come in without a specific users address?  Is
there something wrong at my end?  I know that some messages from
this node come through just fine - sometimes the text of the
message is enough for me to discover who it was supposed to go to
and the users I have contacted say that most of the time the
messages from this node come to them directly.  Does anyone have
a clue about what's going on here?

Sample of bounced message with message text deleted:
************************************************************************
From:   IN%"postmaster@midd.cc.middlebury.edu"  "PMDF Mail Server" 25-AUG-1992 1
   4:00:55.27
To:     IN%"postmaster@midd.cc.middlebury.edu", IN%"USERFDDR@UMICHUM.BITNET"
CC:
Subj:   Undeliverable gateway mail

Return-path: <postmaster@midd.cc.middlebury.edu>
Received: from MIDD.CC.MIDDLEBURY.EDU by MIDD.CC.MIDDLEBURY.EDU (PMDF #12477)
 id <01GO01S4R5UO0004LD@MIDD.CC.MIDDLEBURY.EDU>; Tue, 25 Aug 1992 14:00 EST
Date: Tue, 25 Aug 1992 14:00 EST
From: PMDF Mail Server <postmaster@midd.cc.middlebury.edu>
Subject: Undeliverable gateway mail
To: postmaster@midd.cc.middlebury.edu, USERFDDR@UMICHUM.BITNET
Message-id: <01GO01S4R5UO0004LD@MIDD.CC.MIDDLEBURY.EDU>
X-Envelope-to: knutson

The following message could not be processed by the BSMTP gateway.

----------------------------------------

Received: from JNET-DAEMON by MIDD.CC.MIDDLEBURY.EDU (PMDF #12477) id
 <01GO01RXPFZ40000DT@MIDD.CC.MIDDLEBURY.EDU>; Tue, 25 Aug 1992 14:00 EST
Received: From UMICHUM(MAILER) by MIDD with Jnet id 6596 for MAILER@MIDD; Tue,
 25 Aug 1992 14:00 EDT
Date: Tue, 25 Aug 92 13:58:06 EDT
From: "ROY S. HANASHIRO" <USERFDDR@UMICHUM.BITNET>
Subject: hello
To: MAILER@MIDD.BITNET
Message-id: <15342831@UMICHUM.BITNET>
X-Envelope-to: mailer@BITNET-GATEWAY
From: especially the mouth part of the face
Newsgroups: vmsnet.mail.pmdf
Subject: postmaster bounces - 4.1-10
Date: 28 Aug 92 16:09:39 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 28 Aug 1992 11:09:39 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO3WH6Z25U95ODAO@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I've just upgraded to 4.1, well actually I did it as a new install and copied
the config files from my old 4.0 installation and then switched over from
ctlsmb to pmdf_process_smb. 4.1 does seem to use less resources in mail$batch,
thanks to the developers for getting around the dir/sin bottleneck! I'll bet
this will help us out a lot when we get smothered when the semester starts.


There is an (as far as I can tell) undocumented difference in the behavior of
BSMTP processing: apparently the (local) recipient is checked by the gateway
channel instead of by the local channel. So if you don't want to get bounces
for every unknown user, you have to put nosendpost on the bit_gateway channel.
I'm sure there must be some good reason for this but frankly,  I preferred the
old behavior and think it was much 'cleaner'. I could find out about bsmtp
errors, but the mandane misaddressed mail would be handled by the local channel
(which would have nosendpost). After all it's a local error. Also, the
vast majority of mail which is correctly addressed will now be checked twice,
once by bit-gateway and once by the local channel (vms mail).

Are other folks sucessfully using the postheadonly keyword? It's not working
for me. I have it in a defaults channel block, but I still get the bodies. If I
can get postheadonly to work, I'll take nosendpost off the bsmtp channel.

I would recommend that people on bitnet with a heavy mail load install
bn_master and bn_gateway /open/head/shared. Here these images are invoked
hundreds of times a day. I have also streamlined task_server.com by adding a
set nover and letting all the logfile information just go into the single
process log file. If there is a problem, we can always go back to the old
one. Wirth the one shipped there are way too many files created, with way too
much data in them for normal operation. Our [log] directory was getting up to
10,000 blocks w/ hundreds of files!
From: gdha@se.alcbel.be
Newsgroups: vmsnet.mail.pmdf
Subject: How to rewrite UUCP bang style addresses
Date: 28 Aug 92 12:13:29 GMT
Organization: Alcatel Bell, Antwerpen, Belgium
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 28 Aug 1992 12:13:29 +0000 (GMT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Return-Path: uucp@mccall.UUCP
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO40KY9ZHE95OMKJ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT



The problem I have with UUCP style addresses is the following:
My PMDF conf appends the localhostname "se" to an UUCP address, e.g. "b!a". I
 would rather
rewrite such an address to something like "b!a@alcbel" instead of "b!a@se".
That's all.
--
  _______ 		Gratien D'haese    Switching Systems Division  se121
  \     /Alcatel			  F. Wellesplein 1, B-2018 Antwerpen
   \   /  Bell		e-mail: gdha@se.alcbel.be    Phone: (32) 3 240 94 51
    \/ Telephone		gdha@alcbel.be 	     Fax:   (32) 3 240 99 50
Newsgroups: vmsnet.tpu
Subject: TPU with wordstar commands
From: oldenhuis@ib.agro.nl
Date: Sun, 30 Aug 92 22:27 MET
Reply-To: OLDENHUIS@IB.AGRO.NL
Organization: The Internet
Return-Path: <TPU-Mgr@SHSU.edu>
Errors-To: TPU-Mgr@SHSU.edu
X-Listname: Text Processing Utility (TPU) Language Discussion List
X-Envelope-To: info-tpu@shsu.edu
X-Vms-To: IN%"info-tpu@shsu.edu"
X-Vms-Cc: OLDENHUIS

Dear netters,

Can anyone help me to set up my TPU (EVE) with Wordstar commands??
We use a VAX/VMS system. There must be initialization files or (even better)
section files to make the TPU a Wordstar editor.

Please help me and send those files by E-mail.

Roelof Oldenhuis   <OLDENHUIS@IB.AGRO.NL>
From: w_costa@unhh.unh.edu
Newsgroups: vmsnet.tpu
Subject: Binding EVE_FIND_NEXT to a double key stroke.
Date: 29 Aug 92 04:47:12 GMT
Reply-To: <W_COSTA@UNHH.UNH.EDU>
Organization: The Internet
Return-Path: <TPU-Mgr@SHSU.edu>
Errors-To: TPU-Mgr@SHSU.edu
X-Listname: Text Processing Utility (TPU) Language Discussion List
X-Vmsmail-To: SMTP%"info-tpu@shsu.edu"

TPU folks...

    Easy question (I hope).  I've figured out that to make CTRL-F call the
    EVE_FIND routine, I can use the following TPU code in a COMMAND file:

    	define_key('eve_find("")', key_name(CTRL_F_KEY));

    But how would I bind CTRL-F CTRL-F (i.e. pressing CTRL-F twice) to the
    eve_find_next routine?  (I've tried using the EVE$ source in
    SYS$EXAMPLES: for inspiration, but there's too much I still don't
    understand about TPU.)

    Thanks in advance for the help.

    						Bill Costa
    						W_COSTA@UNH.EDU