Many thanks to:
Lucio Chiappetti lucio_at_ifctr.mi.cnr.it
Bob Grandle grandle_at_acodbob.larc.nasa.gov
The question:
> When we transfer a binary file (file with record lengths > 512bytes)
> which originally resides on a DU box, it arrives to an OVMS box with
a
> fixed record length of 512 bytes (we got this info with ANALYZE /
> RMS). This happens using "get" and "put" with the file type set to
> "image" on both cases.
The theory:
1. UNIX (any flavour) handles files as streams of bytes, where the
record length is NOT an attribute. This is not true on OpenVMS.
2. When a file arrives to the OVMS node, it arrives with a 512 bytes
record length. This is the normal behavior when the OpenVMS node is at
the end, and it has not info regarding the record length. For that
reason, the OpenVMS ---> OpenVMS transfers works fine. Both sides have
info about the record length, so it arrives safely.
The solution:
It was very simple. We use a very simple DCL command, which sets the
file attributes on the OVMS side ( this works on VAX and Alpha ) :
$ SET FILE / ATTRIBUTE=(RFM:STM, LRL: 1024, MRS: 2048) File_name
This sets the file type to stream, with a record length of 1024 bytes,
and a maximum record size of 2048.
Thanks all .
UNIX ADMINISTRATOR
- application/ms-tnef attachment: stored
Received on Fri Feb 21 1997 - 15:54:41 NZDT