Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!usc!randvax!ism780c!vail!auto-trol!marbru
From: marbru@auto-trol.UUCP (Martin Brunecky)
Newsgroups: comp.sys.dec
Subject: Re: how to use a Sun workstation as a X-server for VAX/VMS
Keywords: SunOS 4.0.3, VAX/VMS 5.1-1
Message-ID: <513@auto-trol.UUCP>
Date: 14 Dec 89 20:10:06 GMT
References: <2153@ruuinf.cs.ruu.nl>
Reply-To: ncar!ico!auto-trol!marbru (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 29

In article <2153@ruuinf.cs.ruu.nl> ton@ruuinf.cs.ruu.nl (Ton Kloks) writes:
>
>Subject:        How to use a Sun workstation as a X-server for VAX/VMS.
>Sun:            Running SunOS 4.0.3 and X11 release 3 from MIT.
>Vax:            Running VAX/VMS 5.1-1, including DECwindows.
>Communication:  Ethernet
>
>Trying to connect two different machines running different operating
>systems shouldn't be a problem any more, they told me. Just use X-windows.
>
	Don't want to discourage you. But. The DECwindows server
	available with VMS 5.1 (DECwindows 1.0) seemed to have some
        problems with bytes swapping on the protocol from/to machines
        such as Sun4 (I never tried Sun3). Basically, I could not get
    	beyond creating simple windows. However, rummor has it that
	the next release of DECwindows (VMS 5.3 ???) does not have that
  	problem. Plus, it supports TCP/IP transport, so You don't have
 	to worry about DECNET. However, you need TCP/IP transport on VMS
	side. The products comes with support for VMS's UCX TCP/IP, and
	documentation how to write transport layer for other (3rd) party
	TCP/IP implementations (at least that has been said at DECUS).
	By the way, the next release of UCX has telnet, and does work
  	between Sun and VMS.

-- 
###############################################################################
Martin Brunecky, Auto-trol Technology Corporation,
12500 North Washington Street, Denver, CO-80241-2404
(303) 252-2499                                        ncar!ico!auto-trol!marbru