Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!samsung!usc!apple!oliveb!amdahl!rtech!ferret!dcarter
From: dcarter@ferret.rtech.com (Dan Carter)
Newsgroups: comp.sys.hp
Subject: Re: hp3000 mpe & terminals query...
Keywords: hp3000 enq ack terminal
Message-ID: <4480@rtech.rtech.com>
Date: 15 Jan 90 22:30:40 GMT
References: <83@blender.UUCP>
Sender: news@rtech.rtech.com
Reply-To: dcarter@rabbit.RTech.COM (Dan Carter)
Distribution: na
Organization: Ingres Corporation, Alameda, CA
Lines: 28

In article <83@blender.UUCP> dan@blender.UUCP (Dan Keizer) writes:
>Is there an easy way to have the 3000 terminal ports stop their use of
>the enq/ack (^E/^F) flow?  
>As a side note, is there a way to have "cu" automatically feed a ^F to
>the 3000 after receipt of a ^E?
>Dan.

Configuring the LDEV as termtype 18 (Brand X ASCII terminal, as opposed to a
full-function HP terminal) will eliminate ENQ/ACK.  This can be done perma-
nently, as a boot-time characteristic of the device, or programmatically, with
FCONTROL(38).  Note that there are side effects:  you won't get the DC1 
trigger on reads, which is only of consequence if you're doing block reads
(including terminal status and reads from the display [ESC d]), you won't be 
able to run VPLUS applications (full-screen, block-mode) while so configured,
and you may need to invent some other flow-control mechanism if the HP3000 can
overrun the target device.  

Regarding "cu", I'm afraid I'm not familiar with the term.

In a different posting, you inquire about a memory parity error you experienced
on an HP3000.  In ten years of HP3000 programming and system management, I've
seen that only once, on an aged Series 40 that had been unmercifully overheated
due to a weekend air conditioning failure.  You should definitely get hardware
service to take care of it.

Dan Carter
Ingres Corporation
dcarter@rabbit.rtech.com