[net.unix] UNIX to VMS communication problems

universe@byucsa.UUCP (Daryl Gibson) (07/17/84)

<>
I am having problems transferring files from our
UNIX Sys. III unit to a VAX running VMS. The transfer
seems to work fine at 300 baud, but not at 1200,
over a Ventel 212 link. At 1200, the file
on the VMS side bombs out after a short number
of characters. I imagine this is a parity or
flow control problem, but not knowing VMS adequately,
I don't know how to solve it. We are using
cu(1) to call the VMS system and then reading the
file from UNIX using cat(1) into a VMS editor.
Any hints would be appreciated.

Thanks,

Daryl R. Gibson
BYU Communications Dept.

decvax!harpo!utah-cs!beesvax!byucsa!universe

fair@dual.UUCP (Erik E. Fair) (07/20/84)

This is a flow control problem of the Vax's. A VAX 780 running VMS
can't keep up with a 1200 baud line transferring ASCII without some
form of flow control. Perferably XON/XOFF (^S/^Q) so that the UNIX
system can do it by default. What you need is for the VMS system to
generate a ^S when it's input buffers are nearly full, and a ^Q when
they have drained sufficiently.

	That's why I call it VMESS...

	Erik E. Fair	ucbvax!fair	fair@ucb-arpa.ARPA

	dual!fair@BERKELEY.ARPA
	{ihnp4,ucbvax,hplabs,decwrl,cbosgd,sun,nsc,apple,pyramid}!dual!fair
	Dual Systems Corporation, Berkeley, California

rbbb@RICE.ARPA (07/20/84)

From:  David Chase <rbbb@RICE.ARPA>

You can speed up the VMS end substantially by doing reads larger than a
single character, set alarm, wait for completion of alarm.  We don't have
much trouble communicating at 9600 baud (run uucp at 4800, just to be safe).
I have no trouble running emacs through a serial line and VMS process at
4800 baud, and THAT uses single character reads.  (NB this is on a 780, and
the person managing it (ME) tries to keep things working well.  Perhaps your
VMS is run by an ignorant slob).

drc

mcferrin@inuxc.UUCP (P McFerrin) (07/20/84)

We do xfers from Unix to VMS.  The flow-control problems can be solved
by changing the VMS port.  Before starting the xfer, we send the following
VMS commands to VMS:
	set terminal /noecho
	set terminal /hostsync/ttsync/lowercase
This should solve your flow-control problems.  Refer to your VMS
documentation (or help command) for explanation of the above 'set' commands.

smh@mit-eddie.UUCP (Steven M. Haflich) (07/21/84)

I have used the following shell script command to transfer files from
4BSD to VMS at 1200 baud without problem.  Your problem might be that
many text editors cannot swallow steady 1200 baud input; they were
designed to be driven by people.

You will have to edit this before it will work.  All the "^M" strings
should be replaced with the single char \215, and the "^Z" should be
replaced with \032.  You might have to make additional simple changes to
run this under S5 if you don't have csh, or if echo is significantly
different.

========================
#! /bin/csh
if ( -r $1 ) then
	echo -n set term/noecho \^M
	sleep 2
	echo -n create $1 \^M
	sleep 2
	cat $1 | tr '\012' '\015'
	sleep 2
	echo -n ^Z
	sleep 2
	echo -n set term/echo \^M
else
	echo -n Nothing doing -- $1 unreadable \^M
endif
========================

Steve Haflich, MIT