James B. Byrne ([log in to unmask]) wrote:
: I have a question regarding executable (program) file transfers between
HP3000's
: vis the Internet. Paul Gobes of Robelle and myself spent a great deal of
: Tuesday getting the HP3000 LYNX program transferred from his 3000 to mine.
: Eventually we succeeded but I am wondering if in our frustration with various
: bits and piece we engaged in a bit of overkill....
Here's two specific examples of using FTP to transfer a
NMPRG file from a 3000 to a unix to a 3000 system, without
using anything other than FTP itself.
----------------------------------------------------------------
TRANSFER NMPRG FILE FROM HP3000 to HP9000 to HP3000
USING ONLY FTP
CASE 1: User runs mostly on HP3000 (use MPE's ftp client)
----------------------------------------------------------------
First, transfer NMPRG file MYPROG from HP3000 to HP9000:
:listf MYPROG,2
ACCOUNT= ARPAXL GROUP= BITONDO
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
MYPROG NMPRG 128W FB 103 103 1 112 1 *
:ftp.arpa.sys
File Transfer Protocol [A0007000] (C) Hewlett-Packard Co. 1990
ftp> open hp9ksys
220 hp9ksys FTP server (Version 1.7.193.3 ...
Connected to hp9ksys.cup.hp.com (nn.nn.nn.nn). (FTPINFO 40)
Name(steve): sbitondo
331 Password required for sbitondo.
Password:
230 User sbitondo logged in.
Remote system type is UNIX.
ftp> binary
200 Type set to I.
ftp> put MYPROG
200 PORT command successful.
150 Opening BINARY mode data connection for MYPROG.
226 Transfer complete.
26368 bytes sent in 0.01 seconds (4291.67 Kbytes/sec)
ftp> exit
221 Goodbye.
:
Now we have a file on the HP9000 called MYPROG. We transfer this back
to a HP3000, working on the HP3000. (I am actually transfering back
to the same 3000, so I will rename it MYPROG2 so as not to overlay the
original.)
:ftp.arpa.sys
File Transfer Protocol [A0007000] (C) Hewlett-Packard Co. 1990
ftp> open hp9ksys
220 hp9ksys FTP server (Version 1.7.193.3 ...
Connected to hp9ksys.cup.hp.com (nn.nn.nn.nn). (FTPINFO 40)
Name(steve): sbitondo
331 Password required for sbitondo.
Password:
230 User sbitondo logged in.
Remote system type is UNIX.
ftp> get MYPROG MYPROG2;code=nmprg;rec=128,1,f,binary;disc=112 03
200 PORT command successful.
150 Opening BINARY mode data connection for MYPROG (26368 bytes).
226 Transfer complete.
26368 bytes received in 0.03 seconds (830.65 Kbytes/sec)
ftp> exit
221 Goodbye.
3. Now, let's compare the orginal MYPROG to the current one:
:listf my@,2
ACCOUNT= ARPAXL GROUP= BITONDO
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
MYPROG NMPRG 128W FB 103 103 1 112 1 *
MYPROG2 NMPRG 128W FB 103 103 1 112 2 8
:fcopy from=myprog;to=myprog2;compare
HP31900A.05.02 FILE COPIER (C) HEWLETT-PACKARD CO. 1990
EOF FOUND IN FROMFILE AFTER RECORD 102
103 RECORDS PROCESSED *** 0 ERRORS
END OF SUBSYSTEM
:
----------------------------------------------------------------
TRANSFER NMPRG FILE FROM HP3000 to HP9000 to HP3000
USING ONLY FTP
CASE 2: User runs mostly on HP9000 (use HP9000's ftp client)
----------------------------------------------------------------
From the HP9000 I transfer the file from the HP3000:
/users/sbitondo[167] ftp HP3KSYS
Connected to HP3KSYS.cup.hp.com.
220 HP ARPA FTP Server [A0007003] (C) Hewlett-Packard Co. 1990
Name (HP3KSYS:sbitondo): STEVE.ARPAXL
331 Password required for STEVE.ARPAXL. Syntax: userpass,acctpass
Password:
230 User logged on
Remote system type is MPE/iX.
ftp> binary
200 Type set to I.
ftp> get MYPROG
200 PORT command ok.
150 File: MYPROG opened; data connection will be opened
226 Transfer complete.
26368 bytes received in 0.10 seconds (263.48 Kbytes/s)
Now I transfer it back, renaming it to MYPROG3:
ftp> put MYPROG MYPROG3;rec=128,1,f,binary;code=nmprg;disc=103
200 PORT command ok.
150 File: MYPROG3;rec=128,1,f,binary;code=nmprg;disc=103 opened;...
226 Transfer complete.
26368 bytes sent in 0.01 seconds (3346.33 Kbytes/s)
ftp> quit
221 Server is closing command connection
/users/sbitondo[168]
Now, back on the HP3000, let's prove MYPROG3 is the same as MYPROG:
:listf my@,2
ACCOUNT= ARPAXL GROUP= BITONDO
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
MYPROG NMPRG 128W FB 103 103 1 112 1 *
MYPROG2 NMPRG 128W FB 103 103 1 112 2 8
MYPROG3 NMPRG 128W FB 103 103 1 112 2 8
:fcopy from=myprog;to=myprog3;compare
HP31900A.05.02 FILE COPIER (C) HEWLETT-PACKARD CO. 1990
EOF FOUND IN FROMFILE AFTER RECORD 102
103 RECORDS PROCESSED *** 0 ERRORS
END OF SUBSYSTEM
Some observations/opinions:
1. If you are only transferring one or two files, especially
transferring TO the HP3000, go ahead and transfer it directly with
FTP.
1a. Use the "right side of :FILE equation parameters" on your GET or
PUT command to force the correct MPE record and file characteristics.
Generally, this requires fewer keystrokes than going thru MOVER. You
can ALWAYS do this if you are running the ftp client on the 3000
itself i.e., the 3000 ftp client program won't get upset at the "right
side of :FILE equation parameters" appearing following a semicolon
after your GET or PUT or similar FTP command. Also as I've shown
above, the HP9000 client also won't get upset at this. I think any
ftp client is SUPPOSED to allow anything following a semicolon on a
GET or PUT, but I'll bet there are some ftp clients out there
somewhere that won't like this. Of course, if you are using a GUI'd
ftp client, I don't know how you're going to append the semicolon and
"right side of :FILE equation parameters".
1b. If you do not specify a "right side of :FILE equation parameters"
in your GET or PUT or other ftp transfer command, and your target is
an HP3000, then the FTP subsystem on the 3000 has to GUESS what file
characteristics you want. FTP protocol itself does not define a
standard way of transfering MPE's file and record characteristics!
The HP3000 networking lab engineers designed some reasonable defaults
for these characteristics, but they do not work for all cases. In
particular, they do not assume code=NMPRG, for example. You can
configure the defaults for your MPE system.
Please consult the "HP ARPA File Transfer Protocol User's Guide" (i.e.
the HP3000 FTP user reference manual) for more on all of this.
2. I prefer using MOVER if/when there are a lot of files and/or
subdirectories involved. Then, use MOVER to create a "mailtruck"
file, transfer that file using FTP binary mode, thru whatever
middle systems needed, then on the target MPE system (must be
5.0 or greater!) use MOVER to extract it again. MOVER's mailtruck
file is a bytestream file.
In the above examples, the software versions were:
MPE: RELEASE: C.50.00 MPE/iX HP31900 B.79.06
MPE FTP: version A0007000
HP-UX: A.09.05
...wishing everybody happier ftp'ing in the future...
Stephen Bitondo
Hewlett-Packard Company (MS 47UE) Email: [log in to unmask]
19447 Pruneridge Avenue phone: +1 (408) 447-1074
Cupertino, CA USA 95014-9913 FAX: +1 (408) 447-1178
|
