| Title: | DEC TCP/IP Services for OpenVMS |
| Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
| Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
| Created: | Thu Nov 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5568 |
| Total number of notes: | 21492 |
Crossposted in TURRIS::DECC
One of the applications which we support for our customer is an FTP
implementation (IFTP) written in C. I'm testing a new version on
a VAX running OpenVMS v6.1
They are experiencing some difficulty when copying certain files from
unix to VMS in binary mode. When using Multinet FTP the output file is
created with fixed 512-byte records and the End of File Byte (from
$DUMP/HEAD) is immediately after the end of the incoming data (short
of 512 bytes.) Experimentation shows that UCX does the same thing when
copying binaries from unix to VMS.
IFTP uses:
#define WRITE_BINARY "wb", "rfm=fix", "mrs=512"
file = fopen (temp_path, WRITE_BINARY);
which creates identical output files to the standard FTP *except* for
the End of File Byte which IFTP locates (correctly?) at the beginning
of the next block. When used as input to the application for which this
file is intended, it only works with the EOF marker at the earlier
point.
I need to know what changes to make to the code to get the EOF marker
positioned immediately after the data. Can anyone help?
Thanks,
Dave Lunn.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5328.1 | LASSIE::GEMIGNANI | Tue Mar 11 1997 13:39 | 4 | ||
We (UCX) access the file using RMS and block I/O. We create the file
as a sequential, fixed=512 byte file, and then just write a partial
block. RMS seems to be okay with this. This will leave the EOF at
the absolute end-of-data.
| |||||