HDTenEightyP/NetNews huggingface dataset:
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Using PMDF to deliver printer files
Date: 3 Sep 92 03:35:31 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 03 Sep 1992 10:35:31 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOCF9LH4BM95PAH0@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"HELMKE@CRF.CUIS.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>    We have a number of small satellite VAX/VMS systems all over the
>    USA that we remotely support via dialup logins and PMDF e-mail.
>
>    We are investigating the possibility of setting up a home grown
>    implementation of something that acts like DQS, but uses PMDF
>    (dialup PhoneNet) and DELIVER instead of a DECNet connection to
>    transfer print files.  We are facing the fact that even a modest
>    file (without any graphics--just line printer ASCII of 200-1000
>    blocks) will take many minutes to transfer so we must consider a
>    data compression utility as well.
>
>    Has anyone "pushed the envelope" with PMDF and associated
>    utilities to deliver files to remote printer queues?  Any
>    suggestions for implementation (or pit falls)?

Actually several people have done things like this using PMDF and DELIVER.  For
instance, Ned had a mechanism set up which would allow him to typeset a theatre
program and then have it printed on a printer back in Oklahoma where members of
the community theatre he worked with could then pick it up.

Probably the best way to do this with DELIVER is:

   (1) Set up a command procedure which does the following:
       (a) LZW compress the file and then
       (b) mail it to an account running DELIVER on the remote system
   (2) PhoneNet delivers it to the remote system
   (3) MAIL.DELIVERY for the account on the remote system then executes a
       command procedure which does the following:
       (a) decompress the message body and then
       (b) print the resulting file

You can embed printing information into the message body or you can try using
a Comment: header and use a 1, 2, or 3 DELIVER action to extract that header.
Using the comment header is risky though.  While PMDF doesn't strip Comment:
headers other mailers sometimes do.  Also, another Comment: header my get
added along the way.

If the files may be large, then you can consider using the message
fragmentation support so as to break the message into smaller units.  By doing
this you avoid the problem whereby a phone line glitch kills the message half
way through its transmission and you then PhoneNet has to start sending the
message again from scratch.  The /MAXBLOCKS qualifier to PMDF SEND may be used
or you can use a maxblocks keyword on the PhoneNet channel itself.

It is unfortunate that MIME does not have a compression scheme since that would
have simplified your life greatly.  However, the working group did not come to
closure in time on a compression scheme.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: FAX pop-up form and VMS MAIL keypad keys: problem resolved
From: "Daniel C. Newman" <dan@sigurd.innosoft.com>
Date: 11 Sep 1992 19:31:12 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Sep 1992 19:31:12 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOO4B07P3M984QBX@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Several sites have reported a problem whereby the FAX pop-up form disrupts the
ability to use the VMS MAIL keypad keys.  Thanks to Concordia University
(Riverforest, Illinois), we've managed to finally track this problem down.

The only workaround at present is to keep your terminal set /PERM/APPLICATION.
Of course, this is not practical for sites who need to keep their terminals set
/NUMERIC.

Here's what goes wrong.  When you enter VMS MAIL, MAIL uses a $QIO SETMODE
operation to _temporarily_ enable the application keypad (/APPLICATION) and
thereby allow keypad commands to be used.  Now, when the pop-up form is
invoked, SMG$ is used to create a virtual display and keyboard.  When creating
the keyboard, SMG$ incorrectly does a $QIO SENSECHAR and notes the _permanent_
keypad setting and not the temporary one.  Then, when the pop-up form exits and
SMG$ deletes the display and keyboard, it resets what was the _permanent_
keypad setting.  So if, before entering MAIL, the keypad was set /APPLICATION
then everything is okay and the keypad will still function within VMS MAIL.
However, if the keypad was set /NUMERIC before MAIL was invoked, then SMG$
will restore this setting thereby losing MAIL's temporary /APPLICATION setting.

Clearly, this is a SMG$ bug.  We'll fix this in PMDF V4.2 by doing the obvious:
undoing what SMG$ does after SMG$ is shut down.  Unfortunately, it is not
possible for us to patch this in 4.1 as it involves a piece of code not shipped
with PMDF.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: No-such-(Phonenet)-host bounce msg
From: Bob Tinkelman <bob@camb.com>
Date: 11 Sep 1992 08:28:18 -0400 (EDT)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Sep 1992 08:28:18 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GONDH0CMRM9FMFYY@INNOSOFT.COM>
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

I have a somewhat cosmetic question on the issue of bounce messages.

Attached is a bounce message generated at gs.com.  Mail arrived through
camb.com (its Internet mail exchanger).  The node was unknown.  [It was
a misspelling, with an `oh' for a `zero'.]  The bounce message subject
was
  Subject: Undeliverable mail: PhoneNet de

Beside the fact that it is truncated, is this what is really wanted?
I expect that I can substitute my own message using the $? syntax with
a wild card rule.  [I'm the postmaster at both sites.]  Is this the
recommended course?

BTW, I was also confused by the chronologically first Received:-header.

  Received: from camb.com by gs.com (PMDF #2348 ) id <01GON9E23POW95MU9E@gs.com>;
   Fri, 11 Sep 1992 04:53:32 EDT
  Date: 11 Sep 1992 04:53:31 -0400 (EDT)
  From: PMDF Mail Server <postmaster@gs.com>

This message is being generated on gs.com.  And yet it's claiming the msg
was received from camb.com.  That is where the msg causing the bounce came
from.  Is this what's intended?  It did confuse me at first.
Received: from gs.com by camb.com (PMDF #2344 ) id
 <01GONBEI7AHC90Q1TW@camb.com>; Fri, 11 Sep 1992 05:51:19 EDT
Received: from camb.com by gs.com (PMDF #2348 ) id <01GON9E23POW95MU9E@gs.com>;
 Fri, 11 Sep 1992 04:53:32 EDT
Date: 11 Sep 1992 04:53:31 -0400 (EDT)
From: PMDF Mail Server <postmaster@gs.com>
Subject: Undeliverable mail: PhoneNet de
To: BISEXU-L@BROWNVM.brown.edu
Message-id: <01GON9MIXNFE95MU9E@gs.com>
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Message failed for the following reason:
no addressees
unknown host or domain: user@ARONO1
----------------------------------------
Received: from camb.com by gs.com (PMDF #2348 ) id <01GON597U2OG95N40R@gs.com>;
 Fri, 11 Sep 1992 03:07:37 EDT
Received: from BROWNVM.brown.edu by camb.com (PMDF #2344 ) id
 <01GON4S4PAJK90QBWL@camb.com>; Fri, 11 Sep 1992 02:35:43 EDT
Received: from BROWNVM.BROWN.EDU by BROWNVM.brown.edu (IBM VM SMTP V2R2) with
 BSMTP id 0523; Fri, 11 Sep 92 01:36:55 EDT
Received: from BROWNVM.BITNET by BROWNVM.BROWN.EDU (Mailer R2.08 R208004) with
 BSMTP id 5830; Fri, 11 Sep 92 01:36:55 EDT
Date: 11 Sep 1992 01:35:00 -0400 (EDT)
From: kc55 <Kelly_K_COOKSON@UMAIL.UMD.EDU>
Subject: Re: teaching
In-reply-to: <9209101754.AA19696@umailsrv0.UMD.EDU>
To: Multiple recipients of list BISEXU-L <BISEXU-L@BROWNVM.brown.edu>
Reply-to: Bisexuality Discussion List <BISEXU-L@BROWNVM.brown.edu>
Message-id: <01GON4TKIASA90QBWL@camb.com>
X-Envelope-to: berryr@ARONO1
Content-transfer-encoding: 7BIT

...text deleted...
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Defragment channel
From: Bob Tinkelman <bob@camb.com>
Date: 15 Sep 1992 13:27:18 -0400 (EDT)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Sep 1992 13:27:18 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOT6L946GY9EDAGR@INNOSOFT.COM>
X-Vms-To: IN%"DAN@INNOSOFT.COM"
X-Vms-Cc: IN%INFO-PMDF,TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Dan, thanks for the quick response.

> Does the remote system have a "defragment" channel.

I assume that `remote' means the `receiving' system.  The answer is yes.

>                                                      These are generated
> by the PMDF V4.1 configuration utility.  If the remote system does not have
> such a channel, then add to the system's PMDF configuration rewrite rules of
> the form
>
>       defragment.sigurd.innosoft.com  $U@defragment.sigurd.innosoft.com

Ah, I didn't think about a rewrite rule.  How does this work?  What makes PMDF
look for the name `defragment.sigurd.innosoft.com'?

> and a channel block of the form
>
>       defragment nox_env_to
>       defragment.sigurd.innosoft.com

I didn't have the `nox_env_to', but I did have a channel block.

> Also, make sure that the local channel is marked "defragment"

Yup.  I have that.  Does this redirect mail sent to the official-host-name
to defragment.official-host-name?

> > I could use a pointer to documentation on how to configure the
> > target system.
>
> No such documentation exists at present.

Too bad.
From: alistair@mits.com.au
Newsgroups: vmsnet.mail.pmdf
Subject: Mail system to use with PathWorks?
Date: 10 Sep 92 02:45:01 GMT

We are currently in the process of connecting all our PC's to the
network using PathWorks, and I am trying to determine the most
appropriate mail system to put in place.  It must be able to integrate
with VMS Mail.

The possibilities seem to be:

1.	The unsupported mail client.  This is a DOS application and
	most of our users use Windows, so this is a bit clunky.

2.	Microsoft Mail as licensed with MS Office.  Has anyone
	integrated this with PMDF?

3.	DEC's Mailworks.

I would appreciate any comments.  If you wish to avoid a lengthy
argument on the list, feel free to mail opinions directly to me, and I
will summarise in a couple of weeks.

Thanks in advance,

Alistair Grant

Internet:     alistair@mits.com.au
Alternate:    alistair%mits.com.au@ucsvc.ucs.unimelb.edu.au
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Defragment channel
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 15 Sep 1992 14:25:36 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Sep 1992 14:25:36 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOTF5S4N1G9851LD@YMIR.CLAREMONT.EDU>
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

The defragmentation mechanism in PMDF is very simple. All you need to do is:
(1) Mark the channels you want to have defragmented with the defragment keyword
(this usually means marking the l and d channels this way) and (2) Have a
defragment channel in your configuration. That's it -- nothing else is needed.
You don't need rewrite rules for the defragment channel since it is
automatically used whenever it is needed.

There is little documentation on this because none is needed. CONFIGURE.COM
does everything for you -- it generates the channel and puts the defragment
keyword in most of the appropriate places.

				Ned
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: NOTES channel for PMDF 4.0
Date: 1 Sep 92 17:59:59 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 01 Sep 1992 10:59:59 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO9NITIEQQ95P06Y@YMIR.CLAREMONT.EDU>
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

I believe this has been discussed before, but to repeat...

The PMDF-->NOTES channel was written with the idea that a NOTES-->PMDF
piece would be written later. This hasn't been done but it is on the to-do
list for the next PMDF release.

				Ned
From: ned@innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: BN_MASTER and SEND/FILE
Date: 6 Sep 92 17:58:50 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Sep 1992 10:58:50 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOGN0VZPS296VM7I@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"jjc+@pitt.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> I am running PMDF 4.0, JNET 3.4, Multinet 3.0, and VMS 5.4-3.

> We have a connection to an MVS machine on our campus via BITNET.  The
> mailer on that machine really wants the External Writer field to be set
> to the destination user.  If this is not done, it parses the headers for
> the "To:" line, which causes unpleasant results.

Mailers that parse the To: line for envelope information are fundamentally
busted. It is totally unacceptable to implement this even as an option.

> By default, the SEND/FILE command comes from Joiner with "/OPTIONS" set
> to "".   I see from the source that the Options file seems to be used to
> create a "/OPTIONS=blah" switch on the SEND/FILE that BN_MASTER performs.

> Here are my questions:

> 1. Can I add a "W=" to the options file to have it set use the options
> as follows:

> 	SEND/FILE/OPTIONS="W="

Sure. Just add a line saying

    OPTIONS=W=

to the option file for the channel you use to connect to this system.

This isn't documented but it should work fine.

> 2. Joiner Tech Support tells me it is safe to include "/OPTIONS="W=" to
> have the external writer field filled in on each SEND.  Is that true?
> Are there any NJE mail software packages that would not like this?

There is no way to ever be sure of this. BITNET simply doesn't have any rules
about this sort of thing. As a result you may find all sorts of bizarre usage
out there. All I can say for sure is that I have never seen a mailer that's
sensitive in this way. However, my experience also tells me that when it comes
to BITNET there is almost certainly such a system out there.

> If there are, what is the best way to have this option apply to our
> specific host (or a specific queue)?

It is actually hard to have it any other way, since this is a per-channel
option. Most configurations usually have dozens of BITNET channels. I would
recommend setting up a special channel that is only used for this host
with an appropriate associated option file. This way there is no chance of
this option information ever messing up anyone else.

				Ned
From: ned@innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Problems with cc:Mail channel.
Date: 12 Sep 92 21:41:51 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Sep 1992 14:41:51 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOP8IEH0QA984RON@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"andrewr@itd.adelaide.edu.au"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> 	I'm having two problems with the cc:Mail channel under PMDF.
> The first, of irritance value only, is that it manipulates spaces
> inside quotes in names to underscores in it's output file namem,
> including those around the "AT" which signifies the post office to go
> to, so it's treated as one user. We've got around this with a small
> program on the DOS side to change it back, and using cc:Mail's
> directory propogation so we don't have to specify the post office.

I gather from this that you're entering cc:Mail addresses as

    "user AT postoffice"@ccmail.whatever

on the Internet/PMDF side of things. This is incorrect and unsupported. The
proper form to use is

    user%postoffice@ccmail.whatever

where any spaces in the user part are replace with underscores and any
commas are replaced with plus signs. This is the supported format; it is
also the format that will be produced by the slave channel program.

> 	The second problem is that it only works one way. It creates
> the output file just fine, in the correct format, but it doesn't seem
> to look at the input file specified. EG:

What are you doing to force processing of the input file? Processing
is not automatic -- it cannot be since PMDF has no way of sensing the
creation of the input file. You have to arrange to do a

    $ @PMDF_ROOT:[EXE]MASTER CC_LOCAL POLL

at the proper time. The periodic job can be told to do this when it runs if you
mark the channel with the master channel keyword.

> Obviously I'm doing something wrong as others have got this to
> work - can anyone offer any suggestions? The PC accesses the
> filesystem via PC-NFS through Multinet NFS on the VAX side.

What version of PMDF are you running. There have been a number of changes
and enhancements since the initial release. Please contact service@innosoft.com
and request the most recent version if you're not running at least V4.1-10.

				Ned
From: mjstraw@grove.iup.edu (Mark_Strawcutter)
Newsgroups: vmsnet.mail.pmdf
Subject: bookreader setup
Date: 4 Sep 92 21:39:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 04 Sep 1992 17:39 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GOFT0YIOT696VMU9@YMIR.CLAREMONT.EDU>
X-Organization: Indiana University of Pennsylvania
X-Vms-To: IN%"info-pmdf@ymir.claremont.edu"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Based on info from various sources and a fair amount of playing around,  I've
come up with two ways to integrate the bookreader docs from various sources.

Most come with a LIBRARY.DECW$BOOKSHELF file in the same directory as the
various book/bookshelf files.  I can define DECW$BOOK to be a searchlisted
logical pointing to an infoserver drive, pmdf_root:[doc], multinet_root:
[multinet.documentation] etc.  Bookreader appears to combine the contents
of all the LIBRARY files, and when you pick a shelf/book if finds it (via
the search list or perhaps by remembering which LIBRARY the thing came from).

I can also define DECW$BOOKSHELF as a searchlisted logical with each item
being the full filespec of a LIBRARY.DECW$BOOKSHELF file.  All the contents
are again combined, and it finds stuff in the right place (must be by knowing
which shelf/book came from which LIBRARY file)

I've seen the discussions about puting DECW$BOOK in the system logical name
table since it's searched before the decwindows table.  That's not my problem.
My question is if either of the above methods is to be preferred over the
other.

----------
Mark J Strawcutter                           BitNet:    MJSTRAW@IUP
Director, Systems and Communications         DNS (mx):  mjstraw@grove.iup.edu
Indiana University of Pennsylvania           Voice:     (412) 357-4000
Indiana, PA   15705                          "you can't nail jello to a tree"
From: especially the mouth part of the face
Newsgroups: vmsnet.mail.pmdf
Subject: Postmaster bounces 4.1-10
Date: 31 Aug 92 15:08:35 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 31 Aug 1992 10:08:35 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO817OKK6Q95OPBK@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Thanks for the comments, Ned and Kevin. If you think bouncing addresses asap is
a win in general, I guess I can live with that. Getting other peoples mail puts
the postmaster in an awkward position. I would rather not get incorrectly
addressed mail, unless the bounce couldn't be sent back to the originator. I
wouldn't mind it at all if I only got the headers. I liked it when all local
checking was done by the local channel because I could put nosendpost there
and pretty much miss all the NOSUCHUSER type postings. I haven't encountered
any real problems on the local channel that were not very obvious and
required copies of bounces. Maybe a dontbounceincorrectlyaddressedmailtopostmast
keyword would help here, or maybe something in an options file, or is this too
hideous too imagine?? This are ERROR postings as far as I know, and errsendpost
will still cause them to be bounced to me. For now, I think I'll try taking
nosendpost off all channels and then gradually put it back on channels where
'defaults postheadonly' isn't working.

About the logfiles, I was really getting like 500 files and 10000 blox within a
couple of hours. The disk space doesn't bother me at all, it's just the overhead
of creating so many files and spewing that much data. Then they all have to be
purged, etc... It may not seem like much, but if I can handle a few more users
with this hardware by doing a few things like this it's worth it. The main
logfile has all the output from the programs. Most of the default output is
just tracing master.com over and over again anyway. I turn off set verify
and get rid of the separate logfiles (I've never used batch jobs by the way)
every time I install PMDF. I don't mind doing it, and many sites may not care,
I was really just suggesting that sites with heavy message traffic might want
to look into doing this.

-Tom O'Toole
-JHUVMS Postmaster
From: bob@camb.com (Bob Tinkelman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: `Disconnected' remote PhoneNet dial-in processes
Date: 1 Sep 92 19:07:29 GMT
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 01 Sep 1992 15:07:29 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GO9TNN0FKY9ED99S@INNOSOFT.COM>
X-Vms-To: IN%"NED@SIGURD.INNOSOFT.COM"
X-Vms-Cc: IN%"info-pmdf",TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Thanks for responding so quickly.

> 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 therefore
> 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.  You're saying that once the slave job receives the `end'
it should always ``log off'', independent of what happens to the line.
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?

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

> > The remote system is running 4.1-9 and this system is running 4.1-6.
>
> This should be the same even if you were running PMDF V2.4.

You know, I used to do just that!