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 sdcsvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!ittatc!dcdwest!sdcsvax!bob
From: bob@sdcsvax.UUCP (Robert Hofkin)
Newsgroups: net.dcom,net.lan
Subject: Re: TCP/IP for VAX VMS with FTP
Message-ID: <1517@sdcsvax.UUCP>
Date: Thu, 6-Mar-86 17:29:02 EST
Article-I.D.: sdcsvax.1517
Posted: Thu Mar  6 17:29:02 1986
Date-Received: Sat, 8-Mar-86 21:26:01 EST
References: <1451@gitpyr.UUCP> <2401@prls.UUCP> <674@calmasd.CALMA.UUCP>
Reply-To: calmasd!rjh@UCSD (Bob Hofkin)
Organization: GENERAL ELECTRIC CALMA, ADVANCED SYSTEMS, San Diego, CA
Lines: 27
Xref: watmath net.dcom:1723 net.lan:1337

This is a reposting -- the original seems to have been swallowed.

We've had Wollengong's TCP/IP product on a VMS system for a few
months, and so far it has performed far below our expectations.
We are trying to resolve these problems with Wollengong, but so far:

  * Flow control in TELNET is incompatible with 4.2BSD Unix
    implementations.

  * The FTP server cannot handle passwords over 8 characters long.

  * Unix-compatible libraries were not provided...QIO isn't portable.

  * VMS-to-Unix mail is extremely restricted and unreliable [mostly the
    fault of VMS].

  * I am told there are problems in a cluster environment.

Wollengong's phone support is generally friendly, but not especially
knowledgeable.  They can help you understand the documentation, but
often have to ask around to resolve bugs.  They're slow to call back,
but send update tapes readily.

Given the cost of the package and its level of incompleteness, I
would probably recommend that you investigate the competition more
fully before reaching a decision.  (We accepted an internal GE
recommendation and did not perform a full evaluation.)