Don't quote me, but....here's a thought.
In MPE, in Block mode screen, the terminal waits for a trigger before
sending data to a reader, usually DC1 as noted.
Eg 
Block mode screen full of data, program waits on a read until Enter pressed.
Relocates cursor, writes Esc-d, issues READ (which normally sends DC1),
terminal sends data to reader. 
This doesn't work in Telnet, as telnet doesn't send DC1s (do a telnet
connection, turn on display functions, should not be any DC1). 
I have block mode working un UX/reflections by telling reflections not to
wait for trigger char from computer, as the connection is telnet.
Looks like this FDEVICECONTROL is setting up for non-DC1 reads.....as if in
telnet?
Make any sense?
jp

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Peter Smithson
Sent: Thursday, 25 November 2004 1:02 AM
To: [log in to unmask]
Subject: [HP3000-L] Serial device FDEVICECONTROL question

 Hello,

I'm helping migrate some code from MPE to HPUX which uses
FDEVICECONTROL.  At some point there's a call to this intrinsic with the
parameters 192, 32 with a NUL character in the buffer.

The manual says this

"Read trigger and block mode trigger character:

Specify which character the DTC should send to trigger a character mode
or block mode read on a device. The standard trigger character is DC1.
If a NUL character is specified, there is no trigger character."

In UNIX terms, does this just mean that the particular call (with NUL)
is turning off flow control?  I'm guessing since DC1 is a flow control
character.

Thanks.

Peter

--
http://www.beluga.freeserve.co.uk

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *