Posted with Gavin's permission. He suggested a stack trace, and this is
the stack trace, which is the same for all seven instances. He also
wrote:
You probably want to turn MPE typeahead ON and Reflection typeahead OFF.

Any help making sense of this, if it is worth making sense out of, is
appreciated, on list or off. If it speaks for itself, that this is
nothing more than waiting for a terminal read, then I guess I'm done.

The reason that I didn't know what to expect is that the last thing that
appeared in Reflection was the output of a LISTFILE ,3, and no prompt.
My best guess is that the 3K sent the prompt, but Reflection didn't see
it (maybe because we had seven different work stations doing this on a
busy network, and on a segment using NetBEUI), so Reflection's TRANSMIT
was waiting for a prompt that it should have already seen, and the 3K
was waiting for the session...

>----------
>From:  Gavin Scott[SMTP:[log in to unmask]]
>Sent:  Thursday, February 05, 1998 8:57 PM
>To:    Stigers, Greg  ~ AND
>Subject:       RE: [HP3000-L] Wait : TERMINAL READ on hung telnet sessions
>
>>        PC=a.0017570c enable_int+$2c
>> NM* 0) SP=41837d30 RP=a.00f2a724
>> notify_dispatcher.block_current_process+$324
>> NM  1) SP=41837d30 RP=a.00f2cbd0 notify_dispatcher+$264
>> NM  2) SP=41837cb0 RP=a.001a5c20 wait_for_active_port+$ec
>> NM  3) SP=41837bb0 RP=a.001a68a0 receive_from_port+$534
>> NM  4) SP=41837b30 RP=a.00349efc extend_receive+$494
>> NM  5) SP=41837930 RP=a.0033891c rendezvousio.get_specific+$158
>> NM  6) SP=418377b0 RP=a.00338c80 rendezvousio+$1d8
>> NM  7) SP=418376f0 RP=a.00338a74 ?rendezvousio+$8
>>          export stub: a.01b0a714 sm_term_ptd.sm_read+$270
>> NM  8) SP=41837370 RP=a.01b0af6c sm_term_ptd+$60
>> NM  9) SP=41837230 RP=a.01b0aed8 ?sm_term_ptd+$8
>>          export stub: a.00f0bcb8 tm_terminal.tm_read+$49c
>> NM  a) SP=418371f0 RP=a.00008008 _tbr_Max_Ranges+$8004
>
>Well, it looks to me (though I don't claim to be an expert) as though
>it is waiting on a terminal read all right.  Do you expect it to be
>doing something else at this point?  You said that this is a telnet
>session from a PC running Reflection?  From this it looks like the
>PC has stopped sending data (assuming the process isn't using any CPU),
>or perhaps the network has dropped one of its packets and it is waiting
>for a timeout before retransmitting.
>
>This probably isn't much help, sorry.
>
>Gavin
>