Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!cbosgd!ucbvax!yale.arpa!LEICHTER-JERRY
From: LEICHTER-JERRY@YALE.ARPA
Newsgroups: mod.computers.vax
Subject: Re: IO to spooled device
Message-ID: <8603212239.AA14667@ucbvax.berkeley.edu>
Date: Fri, 21-Mar-86 17:40:00 EST
Article-I.D.: ucbvax.8603212239.AA14667
Posted: Fri Mar 21 17:40:00 1986
Date-Received: Sat, 22-Mar-86 20:32:06 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: <LEICHTER-JERRY@YALE.ARPA>
Organization: The ARPA Internet
Lines: 16
Approved: info-vax@sri-kl.arpa

I don't know off-hand how you get at the device underlying a spooled device;
but:

    Is there an alternative to setting a device spooled that prevents the
    login sequence and broadcast messages?  (other that allocating the
    device).
To prevent logins on a terminal line, set the terminal line /NOTYPE_AHEAD.
To prevent broadcasts on it, set it /NOBROADCAST.  You should set these in
the permanent terminal characteristics (SET TERM/PERM - requires LOG_IO).

Note that once you've allocated the terminal from a program, you can re-enable
typeahead; characters will go to the program, not the job controller.  When
the program deallocates the terminal, the permanent characteristics will be
re-established.
							-- Jerry
-------