HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DMPM%DUKEMC.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 28 Aug 92 22:39:15 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: More on (Any status returned by $ PMDF SEND command in 4.1?)
X-To:         DMPM@DUKEMC, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

>>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"

My previous message already addressed all of this and was sent before I received
this additional posting of yours.  However, for those interested, I'll explain
what is going on here that is causing some errors to set $STATUS and others not
to.

PMDF SEND, as shipped with PMDF, uses LIB$SIGNAL to signal an error.  Now,
LIB$SIGNAL will, in the case of a fatal error, also call $EXIT and $EXIT will
properly set the $STATUS and $SEVERITY symbols.  So, the errors which causes
$STATUS to be set were, undoubtedly, fatal errors.  All other errors (non-fatal
errors and warnings) were merely signalled but no $EXIT performed.  The
suggested code change I sent you should do what you want: display messages when
an informational, non-severe, or severe status code occurs AND always set
$STATUS and $SEVERITY appropriately.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"bob@camb.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 4 Sep 92 04:52:58 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: `Disconnected' remote PhoneNet dial-in processes
Newsgroups: bit.listserv.pmdf-l

The logout message is itself the problem. The SLAVE command file kills
the process with a STOP/ID=0 to avoid production of this message. Somehow
in the way you have things set up you are producing a logout message. This
has to be stopped.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"GHC@VGER.NIDDK.NIH.GOV"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 25 Aug 92 19:20:12 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Problem with personal aliases
X-To:         GHC@VGER.NIDDK.NIH.GOV, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

First of all, you cannot test personal aliases with PMDF TEST/REWRITE. It
does not contain any logic for testing them and will not produce
results that even vaguely resemble what you should get from personal
aliases. This restriction is a permanent one and will not be lifted in
the future -- the handling of the expansion of personal aliases is totally
ideosyncratic to the user agent doing the expansion. VMS MAIL, PMDF SEND,
Multinet MM, and our unreleased PMDF user agent all handle personal aliases
and all do it differently. The only aspect of personal aliases you can
test with PMDF TEST/REWRITE is whether or not they expand into the
proper list of envelope addresses.

Second, the message you received on HELIX was munged by a broken sendmail
configuration. One of sendmail's many problems is that it cannot handle
group address syntax. (More accurately, the configurations that ship
with 99.999% of the sendmails of the world don't handle group addresses
properly.) In practice this is a non-issue since you cannot use an
empty group address for anything anyway. But the address you should
have seen was something like this:

    To: HELIX: ;

The @host stuff is garbage that sendmail slapped on there. Ironically, there
are also some sendmails out there that will strip this garbage back off. What
a pile.

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.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 30 Aug 92 01:22:19 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      PMDF-MR, MIME, WPS-Plus format attachments
X-To:         ipmdf@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l

I am looking to replace some ALL-IN-1 mailing lists with lists
maintained with PMDF.  The way I am planning to do this would cause
some mail that currently stays within the ALL-IN-1 system to leave
it, go through PMDF and then reenter ALL-IN-1.  The problem about
which I'm worrying is WPS-Plus format attachments.  It appears to me
that I'll have to tell PMDF-MR to translate them to ASCII, for the
benefit of the non-ALL-IN-1 users. And that will be a loss in
functionality as perceived by the community of ALL-IN-1 users.

I was wondering if this was the sort of area that MIME could
address.  Could PMDF-MR, when processing mail from the MR, generate
both formats (WPS-Plus and ASCII) as alternatives?  And then (second
question) could PMDF-MR simply discard the ASCII alternative when
processing in the other direction?

Independently to the above, is there some other way of addressing
this issue that I should know about?

Thanks - Bob Tinkelman
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"INFO-PMDF@YMIR.BITNET"
X-VMS-Cc: KNUTSON
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 25 Aug 92 21:41:55 GMT
From:         "Linda Knutson; 802-388-3711 x5577" <KNUTSON@MIDD>
Subject:      need help will bounced mail
X-To:         INFO-PMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"NED@INNOSOFT.com"
X-VMS-Cc: IN%"info-pmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 4 Sep 92 11:26:26 GMT
From:         Jeremy Begg <JEREMY@VSM.COM.AU>
Subject:      RE: Erroneous output from CONFIGURE.COM
Newsgroups: bit.listserv.pmdf-l

>> Didn't work.  I removed the "charset7 us-ascii" without success, and then
>> also the "charset8 iso-8859-1" and that didn't help either.
>
>Did you remove them from both the D AND the L channels? You have to get rid of
>it in both places. charset8 has nothing to do with it unless you use 8-bit
>characters. You can also solve the problem by getting rid of the linelength
>limits. The proper solution, of course, is to get a newer version of PMDF that
>handles this interaction correctly. Please contact your distributor if you want
>a updated version; all distributors have had updated versions in hand for quite
>a while.

Thanks, that's fixed it.  I'll see if I can get a later release.

        Jeremy Begg
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 31 Aug 92 13:04:55 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      Mail-11 delivery and soft-vs-hard failures
X-To:         ipmdf@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l

I had a message [headers attached] stuck in pmdf_root:[queue.d].  The
d_master.log file contained:

        %MAIL-E-SENDERR, error sending to user KEITH at BELMT3
        554 Unbalanced '"'

This looks like cases I've seen on other systems which had bad sendmail.cf
files.  [BELMT3 is an Ultrix machine, I believe.]

What determines whether PMDF treats an error like this as a permanent
error (bouncing the mail msg immediately) or a temporary error (leaving
the msg queued for a later retry)?

In this case, bouncing it would probably have been more appropriate.
We are running PMDF 4.1-6 at this site.









m;labo@apollo.hp.com
keith@belmt3.belmont.com

Received: from rutgers.edu by camb.com (PMDF #2344 ) id
 <01GO4FH6XJWW90OO1C@camb.com>; Fri, 28 Aug 1992 17:16:10 EDT
Received: from mit-eddie.UUCP by rutgers.edu (5.59/SMI4.0/RU1.4/3.08) with UUCP
 id AA04414; Fri, 28 Aug 92 16:20:56 EDT
Received: by xuucp.ch.apollo.hp.com id <AA22083@xuucp.ch.apollo.hp.com>; Thu,
 27 Aug 92 17:52:33 EDT
Received: from saab.ch.apollo.hp.com by daphne.ch.apollo.hp.com id AA27595;
 Thu, 27 Aug 1992 18:07:40 -0400
Received: by saab.ch.apollo.hp.com id <AA21977@saab.ch.apollo.hp.com>; Thu,
 27 Aug 92 18:07:21 EDT
Date: 27 Aug 1992 18:07:20 -0400 (EDT)
From: labo@apollo.hp.com
Subject: Re: new phone number
In-reply-to: dsb@world.std.com (David Boyce), thu, 27 aug 92 17:23:56
To: David Boyce <dsb@world.std.com>
Cc: Steve Pitschke <steve@praxsys.com>, keith@belmt3.belmont.com,
 coco@centerline.com, gab@centerline.com, sg@corwin.ccs.northeastern.edu,
 steve@praxsys.com, labo@apollo.hp.com, jvs@osf.org, rom@osf.org,
 lawton@world.std.com, arra@inmet.com
Message-id: <9208272152.AA22083@xuucp.ch.apollo.hp.com>
Content-transfer-encoding: 7BIT
Source-Info:  From (or Sender) name not authenticated.

...... Message text deleted ......
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"bob@camb.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 3 Sep 92 00:17:37 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: `Disconnected' remote PhoneNet dial-in processes
X-To:         bob@camb.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> OK.  I understand that now.  We explictly do a SET NOVERIFY in our SYLOGIN.COM
   ,
> just before we quit if the user is a PMDF PhoneNet channel.  So I don't think
> that's the problem (unless it broke, of course :-).

The only thing that stands between the slave process and logging out is
terminal I/O; disconnecting should have no effect if no output is done. The
slave program definitely should not produce any I/O. This leaves the command
file trapping and related environment.

> No, I mean connect to one of those disconnected processes by logging in to the
> PMDF account and then explicitly reconnecting to one of those disconnected
> processes out there. I expect that some output should pop out and the job will
> then log out. The output that appears is what's important.

> I'll try that the next time I see them.  However, I'll have to reset the
> account from it's current setting of DisReconnect.  That couldn't be the
> problem, could it?

Just disable disreconnet prior to doing your reconnect. I don't see how this
could be the problem. You could also simply set the terminal /NODISCONNECT
and let VMS blow the process away instead of leaving it out there.

> I set that at one point because the scripts I'm using
> at the MASTER end couldn't deal with the unexpected prompt when there were
> disconnected processes.

Correct. But the information that pops out when you reconnect to one of
these processes is critical to determining where the problem is.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ECF_STBO%JHUVMS.BITNET@ymir.claremont.edu"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 29 Aug 92 11:01:49 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      PMDF Process Symbiont
X-To:         ECF_STBO@JHUVMS, info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

> 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 thing you might want to watch out for.  Using only the IDLE_TIMEOUT option
means that a really active TASK_SERVER won't time out and exit and allow for
a new TASK_SERVER.LOG file.  You might want to consider using the LIFETIME
option which specifies a delta time after which the TASK_SERVER process will
exit and be restarted even if it never reaches IDLE_TIMEOUT.  For example,

    LIFETIME = 0 06:00:00

in the PMDF_PROCESS_SMB.OPT will create a fresh TASK_SERVER process and new
log file every 6 hours.  The exit is done cleanly, between processing jobs.
Unfortunately this didn't make it into the printed manuals, but is in the
on-line BookReader docs.

        /Kevin Carosso
         Innosoft

ps.  The default if you don't specify is 24 hours I believe.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"dmpm,ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 29 Aug 92 07:10:22 GMT
From:         "James Dryfoos - Postmaster" <DMPM@DUKEMC>
Subject:      From, relpy_to, sender addresses?
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

Help,

I am trying to use PMDF SEND facility to send mail on other peoples behalf.
I want all replies to go back to the designated person.
I am using the /from and /reply_to fields to do this.  It appears
to work fine for internet stuff but not for BITnet.  No matter what
I do with PMDF SEND it always puts in a Sender: field containing the actual
username I was logged in with.  It appears that this is what BITnet nodes
use to send back messages and errors and nothing else (I assume it is what is
on the envelope from field also).  Is this a correct interpretation?
Should I bag this whole idea?  If so, what is another way of doing it?
Is PMDF_RELAYING going to work differently?

Below is a message I sent to non-existent user on a valid BITnet node.
As you can see it went back to sender and not to the address I
put in the /from and /reply_to switches.

-Jim

m;Postman@DUKEMVS.BITNET
DEMPO@DUKEMC.DEMPO

Received: from Jnet-DAEMON by mc.duke.edu (PMDF #3229 ) id
 <01GO4CCQLLMO003445@mc.duke.edu>; Fri, 28 Aug 1992 16:38:03 EST
Received: From DUKEMVS(POSTMAN) by DUKEMC with Jnet id 2326 for DEMPO@DUKEMC;
 Fri, 28 Aug 1992 16:38 EST
Date: 28 Aug 1992 16:33 -0400 (EDT)
From: Postman@DUKEMVS.BITNET
Subject: Undelivered mail
To: DEMPO@mc.duke.edu
Message-id: <01GO4E65D2AY003445@mc.duke.edu>
Content-transfer-encoding: 7BIT

Your mail was not delivered to some or all of its
intended recipients for the following reason(s):

6302 mailbox invalid -> TESTING@DUKEMVS.BITNET

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

Received: (from DUKEMC.BITNET for <DEMPO@DUKEMC.BITNET> via BSMTP)
Received: (from DEMPO@DUKEMC for MAILER@DUKEMVS via NJE)
 (UCLA/Mail V1.500 M-JNET7514-7514-22); Fri, 28 Aug 92 16:33:46 EDT
Received: from mc.duke.edu by mc.duke.edu (PMDF #3229 ) id
 <01GO4E5PAW9C0045JW@mc.duke.edu>; Fri, 28 Aug 1992 16:37:41 EST
Date: 28 Aug 1992 16:37:41 -0500 (EST)
From: POSTMAST@DUKEMC.BITNET
Subject: Test - ignore
To: TESTING@DUKEMVS.BITNET
Reply-to: POSTMAST@DUKEMC.BITNET
Message-id: <01GO4E5PAW9E0045JW@mc.duke.edu>
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: TESTING@DUKEMVS.BITNET
MIME-version: 1.0
Content-transfer-encoding: 7BIT

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"stodola@orion.fccc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 4 Sep 92 01:55:52 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Strange forwarding problem.
Newsgroups: bit.listserv.pmdf-l

> We have a situation where a network alias (J_Blow@fccc.edu) points to Joe's
> VMS account (Blow@rm.fccc.edu).  Joe wishes to forward his VMS mail to his Uni
   x
> account (J_Blow@xyz.fccc.edu).  Unfortunately, xyz recognizes J_Blow as an
> alias which then loops.  We had hoped to fudge the problem by putting a
> backslash in the forwarding address on the VAX side.  Unfortunately, putting
> in one backslash (set forward "in%""\j_blow@xyz.fccc.edu""") appears to
> swallow the backslash, while putting two backslashes causes PMDF to complain
> about a bad address (\J_Blow...).
>
> Flames aside (and I recognize that many are deserved in this situation!), if
> someone could explain how one might do this in PMDF, I'd be most grateful.
> We have some workarounds which may be better anyway, but I'd like to understan
   d
> the options.

Backslash is, in RFC822 parlance, a "special" and must be quoted when it
appears in a mailbox name.  So, the legal RFC822 address for what you're
trying to do is "\j_blow"@xyz.fccc.edu.  To specify such an address in
VMS MAIL, you must use IN%"'\j_blow'@xyz.fccc.edu".  To set a VMS MAIL
forwarding address of this form, use the command

    MAIL> SET FORWARD "IN%""'\j_blow'@xyz.fcc.edu"""

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"bob@camb.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 2 Sep 92 01:24:11 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: `Disconnected' remote PhoneNet dial-in processes
X-To:         bob@camb.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> > It sounds to me like your slave jobs are chattering on the terminal port as
> > they shut down. There should be no output at all between the time that the
> > PhoneNet end command arrives and the session logs out completely. It therefo
   re
> > should not matter if the port gets disconnected or not since this will not
> > affect the proper termination of the job.

> I'm confused.  It's at the slave end that I'm seeing the disconnected
> processes.

Sure. The master job is a batch job. It cannot disconnect.

> You're saying that once the slave job receives the `end'
> it should always ``log off'', independent of what happens to the line.

Correct.

> What does that have to do with ``chattering on the terminal port''?  Is
> this chattering something you picture coming from the slave computer or
> going to the slave computer?

It is stuff coming out of the slave process. The way this works in PMDF is that
SLAVE exits and then SLAVE.COM stops the process. If, for instance, you have
SET VERIFY enabled, there will be noise from the command file that will go out
on the line.

> > You might want to try to connect to one of these things and see what output
> > they produce. I can think of no simpler way to find out what's stuck in the
> > buffers.

> By that do you mean I should dial into the slave computer, log into the
> PhoneNet account, and pretend to be the master end of the connection?
> If so, I guess I can figure out how to do that, after making sure that
> there is nothing queued at the master end for transmission.

No, I mean connect to one of those disconnected processes by logging in to the
PMDF account and then explicitly reconnecting to one of those disconnected
processes out there. I expect that some output should pop out and the job will
then log out. The output that appears is what's important.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.ashe-l
Date:         Tue, 1 Sep 1992 08:20:49 U
              <ASHE-L@MIZZOU1.BITNET>
From:         "Michael Matier" <michael_matier@QMRELAY.MAIL.CORNELL.EDU>
Subject:      ASHE Retiree Recognition
X-To:         ashe-l@umcvmb.BITNET
X-cc:         sylvia_hurtado@um.cc.umich.edu

                       Subject:                               Time:8:04 AM
  OFFICE MEMO          ASHE Retiree Recognition               Date:9/1/92
    The ASHE Graduate Student Committee is soliciting nominations for
recognition at the upcoming ASHE Annual Meeting to be held October 29th through
November 1st at the Marriott City Center in Minneapolis.  If you know of any
individuals who are within one year of retirement (recently retired or about to
retire) please send the individual's name,institution, and phone number or
address by bitnet to:

          Sylvia_Hurtado@um.cc.umich.edu

    We are also interested in the names and phone numbers of any individuals
that may be able to speak in behalf of the candidate you recommend.  Deadline
for receipt of all nominees is October 1, 1992.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU