Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!hc!beta!cmcl2!rutgers!im4u!ut-sally!utah-cs!utah-gr!uplherc!nrc-ut!nrcvax!kvc
From: kvc@nrcvax.UUCP (Kevin Carosso)
Newsgroups: comp.os.vms
Subject: Re: Terminal hangup
Message-ID: <1269@nrcvax.UUCP>
Date: Tue, 3-Nov-87 14:43:24 EST
Article-I.D.: nrcvax.1269
Posted: Tue Nov  3 14:43:24 1987
Date-Received: Sun, 8-Nov-87 02:03:06 EST
References: <8710310940.AA17786@ucbvax.Berkeley.EDU>
Reply-To: kvc@minnie.UUCP (Kevin Carosso)
Organization: Network Research Corp.  Oxnard, CA
Lines: 18

In article <8710310940.AA17786@ucbvax.Berkeley.EDU> U00170@HASARA5.BITNET writes:
>It is waiting for a <CTRL>Q but the laserwriter, for some reason,
>does not do that.
>
>Is there a way to reset the terminal driver, without having
>to reboot the entire system? Who has ever made such a reset
>program?

DEC has... :-)

You might try doing a SET TERMINAL/XON to the hung up device.  This tells
the terminal driver to pretend it just received an XON (^Q) and to resume
output.  You may need the SHARE privilege to do this to the device if
someone, like a print symbiont, owns it.  I don't know where, or if, this
is documented.

	/Kevin Carosso                  kvc@nrcvax.uucp
	 Network Research Co.           kvc@engvax.scg.hac.com