[net.decus] VMS UUCP

malloy@ittral.UUCP (William P. Malloy) (09/27/84)

As I see this request constantly reappearing on the net let me tell one and
all there already IS a VMS UUCP.  It's called UVCP (cute no?) and it's from
the company named below.  Now as to how good it is.  Well lets just say it
does work, finally, after much pain and effort.  As to whether the problems
was with UVCP itself (the first versions didn't work)  or with VMS (probably)
or with our VMS Support Staff (who had NO desire to install anything that
makes it easier for UNIX to talk to their machines) I'm not sure.  We finally
have it installed however, and let me tell you it's a whole lot easier then
using magtape and `vmstp'.  The only problem is that uucp has to be hacked on
the UNIX end because of the difference between UNIX and VMS on line terminator
characters.

Address from net.news.map, not sure if this is sales.  Site name `mprvaxa'.
		Microtel Pacific Research
		8999 Nelson Way
		Burnaby, BC  Canada  V5A 4B5
		Phone: (604) 294-1471

And I have no connection to the company, nor did I have anything to do with
installing it.  It's just a lot easier then tape.  I personally think it would
have been a whole lot better to get those VMS perverts to use a REAL OS.
--
Address: William P. Malloy, ITT Telecom, B & CC Engineering Group, Raleigh NC
	 {ihnp4!mcnc, burl, ncsu, decvax!ittvax}!ittral!malloy

root@vortex.UUCP (The Superuser) (10/01/84)

The reasons I've continued work with my VMS UUCP (in the presence
of the VUCP thing that the Canadian firm has) are basically
threefold:

1) I get lots of reports of trouble with VUCP -- which isn't at all
   surprising given the mess of porting Unix code to VMS.

2) I consider close integration of UUCP with the VMS mail system
   to be essential for a full mail/uucp implementation (as opposed
   to simple mail kludges).  It became obvious that only by coordinating
   my efforts closely with DEC could I accomplish this and also track
   future VMS changes.

3) My code is independent of Unix code and thusly does not (unlike the
   other product) require a Unix binary (which the customer must pay
   for of course) to be imbedded within the product.

Anyway, to some these points might not matter, but to others
they well might.  My whole package has been oriented toward being a 
full mail/uucp package with 822 compatibility, rather than 
a "simple" system to mainly replace tape transfers...

--Lauren--