Article 128663 of comp.os.vms:
Path: nntpd.lkg.dec.com!crl.dec.com!crl.dec.com!bloom-beacon.mit.edu!newsfeed.internetmci.com!btnet!tank.news.pipex.net!pipex!uknet!zippy.dct.ac.uk!mcscs2mm
From: mcscs2mm@zippy.dct.ac.uk (Malcolm MacArthur)
Newsgroups: comp.os.vms
Subject: Re: SMG$ to non-terminal devices
Message-ID: <1995Sep6.145053.20399@zippy.dct.ac.uk>
Date: 6 Sep 95 14:50:53 +0100
References: <393980187wnr@nmsg.demon.co.uk>
Organization: Lies, Incorporated.
Lines: 35

In article <393980187wnr@nmsg.demon.co.uk>, Internet User <user@nmsg.demon.co.uk> writes:
> ------------------------------------------------------------------------
> 
> Please help...
> 
> We have an application that we have ported to Alpha.  The application 
> used to use LAT.  A process would sit on a port and fire up when a call 
> was received.  It also ran under tcpware behind port 999.  In these 
> cases SMG$ works as the device is of type terminal.
> 
> On Alpha UCX$ creates a _BGnnn: device which is not a terminal type.  
> How can I get SMG$ to accecpt that this device is a supported terminal 
> type, Say VT100 ???
Well, you could use a pseudoterminal device. If you want to look at some (not 
too clean :-) code to do this, there is a program called BOSS (ftp.spc.edu, in 
[.macro32.savesets]boss.zip, or nic.switch.ch in 
/mirror/vms/spc/macro32/savesets/boss.zip) which is used for pseudoterminal 
applications.

In fact, if you're looking for a _quick_ solution you can get 
BOSS to fire up on port 999, and execute the program (it can do this).
I _think_ BOSS would be able to talk to the non-terminal BGnnn device OK, as it 
doesn't use SMG (It does, however, use certain control keys, so you might have 
to redefine/disable them)

You can use UCX's inetd to to the above.

Good luck,
Malcolm.

--
Malcolm MacArthur                M.McArthur@zippy.dct.ac.uk
I get a little warm in my heart
When I think of Winter
Usual mediocre homepage: http://www.dct.ac.uk/people/mcscs2mm.html