Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!lakesys!deanr
From: deanr@lakesys.lakesys.com (Dean Roth)
Newsgroups: comp.protocols.tcp-ip
Subject: VMS & TCP/IP
Message-ID: <1512@lakesys.lakesys.com>
Date: 4 Jan 90 15:10:08 GMT
Distribution: usa
Organization: Lake Systems - Milwaukee, Wisconsin
Lines: 43


My company has been asked to port its communications
software to VMS.  The software consists of client and
server software, uses BSD socket interface and was
designed for UNIX and MS-DOS. The software does not perform
any disk or terminal I/O - that is left to the application developer. 
Since I have next to no VMS experience,
I need your advice.  (Please email directly to me.)


I have DEC's "Network and Communications Buyer's Guide".
The guide lists three TCP/IP products for VMS: 

	Fusion TCP/IP
	WIN/TCP
	TCP/IP


Questions:
---------
In general, what is your experience with these products
for writing interprocess communications software?  I do not care about
file transfer (ftp), email or virtual terminal support.

What about installation and support? 

Only WIN/TCP is indicated to be compatible with BSD 4.3 UNIX.
I'm not sure what that means.  Perhaps it means it has
the same C function (socket) interface?

How easily can I port the UNIX software?
Is it (almost) a matter of recompiling?

The server software creates a new process to
handle each connection.  Is this a "problem"
under VMS?  (One party told me it is too
inefficient. Another party said, "No problem".)


Thank you for your help.

Dean
deanr@lakesys.lakesys.com