HP ARPA File Transfer Protocol User's Guide (36957-90159)

80 AppendixA
MPE/iX and POSIX Differences
Building and Transferring a Bytestream File
200 PORT command ok.
150 File: LISTFILE .bytestrm,2 opened; data connection will be opened
PATH= /SYS/PUB/
CODE --------LOGICAL RECORD-------- ----SPACE---- FILENAME
SIZE TYP EOF LIMIT R/B SECTORS #X MX
80B FA 38 2147483647 1 16 1 32 bytestrm
226 Transfer complete.
230 bytes received in 0.01 seconds (24.96 Kbytes/sec)
Example 2:
File transfer HPUX (unix) system to HP3000 MPE/iX system.
vi bytestrm
This is a bytestrm test data file.
:wq
“bytestrm” [New file] 1 lines, 34 characters
ftp> put bytestrm ./bytestrm
200 PORT command ok.
150 File: ./bytestrm;rec=,,b opened; data connection will be opened
226 Transfer complete.
35 bytes sent in 0.00 seconds (64.73) Kbytes/sec)
ftp> dir ./bytestrm
200 PORT command ok.
150 File: LISTFILE ./bytestrm,2 opened; data connection will be opened
PATH= /SYS/PUB/
CODE --------LOGICAL RECORD-------- ----SPACE---- FILENAME
SIZE TYP EOF LIMIT R/B SECTORS #X MX
1B BA 35 2048007 1 16 1 8 bytestrm
226 Transfer complete.
NOTE When transferring a Bytestream file from UNIX to a MPE/iX system it is
necessary to specify “;rec=,,b”. This is required as a result of FTP/iX
supporting a default of “fixed” file type rather than bytestream which is the
default on UNIX and POSIX systems.
Example 3:
File transfer HP 3000 MPE/iX system to HPUX (UNIX) system.
ftp> bytestream
200 Type set to L (byte size 8).
ftp> put ./bytestrm
200 PORT command successful.
150 Opening BINARY mode data connection for ./bytestrm.
226 Transfer complete.
35 bytes sent in 0.00 seconds (+INF Kbytes/sec)