Xref: utzoo comp.windows.x:7342 comp.os.vms:11128 comp.sys.dec:943
Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!mailrus!cornell!uw-beaver!blake!oregon!dsmith
From: dsmith@oregon.uoregon.edu (Dale Smith)
Newsgroups: comp.windows.x,comp.os.vms,comp.sys.dec
Subject: Re: DECwindows: does it use DECnet, TCP or both?
Message-ID: <168@oregon.uoregon.edu>
Date: 17 Jan 89 12:34:29 GMT
References: <2017@sun.soe.clarkson.edu>
Organization: University of Oregon
Lines: 24

In article <2017@sun.soe.clarkson.edu>, abstine@sun.soe.clarkson.edu (Arthur Stine) writes:
> Does anyone know what underlying byte stream protocol DECwindows
> uses? I assume that it uses DECnet, but what about TCP? How would I
> use it in a network with X on Suns, etc?

As I am sure you have seen, DECwindows v1 on VMS will only support 
DECnet as a network transport facility.  I had a long conversation with
the DECwindows/VMS/ULTRIX folks at fall DECUS about TCP/IP support for
VMS DECwindows and it looks abysmal.  As far as I could find out, DEC's
position on this is that they are now offering a TCP/IP product for VMS
and that is what they are going to use.  However, they would make no
committment to provide a *fully functional* TCP/IP implementation for
VMS, nor provide the hooks for third parties to provide a transport
mechanism for VMS DECwindows.  So, if you are running WIN/TCP, Fusion,
etc., and want to run DECwindows (v2) over TCP/IP, it looks like you'll
be out of luck.  Your choices will be to toss your TCP/IP and get DEC's
TCP/IP (with no named, gated, finger, timed, ...etc.....) or to not run 
DECwindows over TCP/IP.    GGGGGGGGGrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr.

Dale Smith
Asst. Director of Network Services	Internet: dsmith@oregon.uoregon.edu
University of Oregon			BITNET: dsmith@oregon.bitnet
Computing Center			UUCP: ...hp-pcd!uoregon!dsmith
Eugene, OR  97403-1212			Voice: (503)686-4394