Thanks to all who responded. My original post:
> At our site he have been ftp_ing data from Unix to VMS without
> any problem. Recently, however, we have a need to ftp data from
> VMS to Unix. When we try this we get strange formatting errors.
> Is there a quick fix to this problems? I will summarize.
Sorry for the vagueness, next time I'll provide more information. The
problem was carriage returns showing up in files. Now we transfer
in ascii mode not binary. Everyone who responded provided very useful
information, especially Sheila Franklin.
The replies:
from SYSTEM_SF_at_unode2.nswc.navy.mil,
If you're transfering ASCII files and you use the binary option of ftp (some
systems it's the default), the files keep the carriage return line formating of
the host system. Since OSF/1 and VMS use different methods, the format of the
ascii text isn't correct. If you did the transfers with ascii mode selected,
your ftp program does the conversion of the carriage return line feeds for you.
from amy_at_aloha.gsfc.nasa.gov,
What exactly are the strange formatting errors you're getting?
What kind of files are you sending? What versions and flavors
of Unix and VMS are you using? You *have* been using binary
mode for non-ascii files, right? And have you realized that
fixed record length is a problem going VMS-Unix?
from teh_at_chinook.phy.anl.gov,
We've had similar problems ftping unformatted data from VMS to Unix. We
run Multinet for TCP services on VMS. The problem exists only for
unformatted files with variable length records. On VMS, these records are
preceeded by a record byte count. Multinet tries to be smart and interprets
this record length. However, when it gets over to the Unix side, the record
byte count is corrupted, so the record is pretty much useless.
We've essentially advised our users not to use variable length records, but
fixed length records. Then the file comes over fine in binary mode. The other
advantage of fixed length records is that you can do NFS mounting of VMS
file systems on Unix and have access to the file without formatting problems.
from luchini_at_siberia.ups-tlse.fr,
The only thing that springs to mind (I've seen this problem many times),
is make sure that you always 'set type binary' in your ftp session.
Because the alpha is 64bit ftp messes up on binary data.
from MARCH_at_mtl.marconi.ca,
Who's TCP/IP package are you using? We're using
Wollongong Pathway Access. When pushing binary data
with special RMS settings, you have to set block i/o
mode: io_mode on the VAX or quote site io_mode whe
pulling from the UNIX side.
from dsr_at_lns598.lns.cornell.edu,
No generic fix, and the specific fix depends on the file type on the
VMS system. The first step is to do a 'dir/full' on the VMS sytem
and find out what the record attributes of the files are. For text
files, either transfer 'em in text mode or make sure they are in
STREAM_LF format. Fixed length records should transfer fine in binary
mode. Binary data with variable length records in formats like the
infamous "VFC, 2 byte header" form are trouble--you'll have to
understand what delimits the records before you can convert 'em to a
sensible format, and may have to write a custom program to do the
conversion. The VMS 'convert' utility may help, but my VMS days are
long enough ago that I don't remember the details.
from scottm_at_disc-synergy.com,
What file format are you using when transferring the files: ASCII,
Image, or Binary? Are you starting the transfer from the Unix or VMS
side?
If you are going from the VMS side to the Unix and you are transferring
ASCII files you may have problems both ways. If you are transferring
from the VMS side to the Unix and you are transferring binary files you
may want to switch from Image to Binary or Binary to Image. There is
a difference. If you are transferring binary files and you are logged
in on the Unix you may want to try it from the VMS side and play with
the Image/Binary modes.
from hammr_at_ucfv.bc.ca,
which VMS TCP/IP stack are you using? (hope it's not UCX)
are they binary files?
you could've supplied more info here.
from intrepid!dino!tb_at_uunet.uu.net,
Make sure the file transfer type is the same. binary or ascii.
from jacy_at_fluid.mro.dec.com
When you ftp'ed...
Did you make sure to set transfer mode to binary???
>From the VMS world if your UNIX system has DECnet you can also use spool
spool/trans=block filename UNIX::'filename'
Or exchange with trans=block... The problems you get with be because of
the record length....
Why can't you UNIX system "pull" the data from the VMS system???
Received on Wed Jul 05 1995 - 19:29:44 NZST