HP 3000 Manuals

Transferring Remote Host Files to MPE/iX [ HP ARPA File Transfer Protocol User's Guide ] MPE/iX 5.0 Express III Documentation


HP ARPA File Transfer Protocol User's Guide

Transferring Remote Host Files to MPE/iX 

Use the GET command to copy a file from the remote host to your local
MPE/iX system.  FTP does not delete the remote copy of the file.  Enter
the GET command followed by the file name of the remote file, followed by
the name of the file you want to copy to on your local system. 

     ftp> GET remotefile localfile

If you do not specify the localfile name, the file will be transferred
with the remotefile name specified:

     ftp GET remotefile

If the remotefile name used is not a valid file name on MPE/iX, the file
transfer fails.


CAUTION If the local file name you specify already exists on your local MPE/iX system, FTP overwrites the existing file without warning.
Default File Attributes Files copied from the remote host to MPE/iX are saved with default file attributes as follows: Table 4-6. ------------------------------------------------------------- | | | | | File Type | Record: | Disk Space | | | size(bytes), type | | | | | | ------------------------------------------------------------- | | | | | ASCII Binary | 80, fixed 256, | 204,800 204,800 | | BYTESTREAM | fixed 1, byte | 16,384,000 | | | | | ------------------------------------------------------------- Table 4-7. ------------------------------------------------------------------ | | | | ASCII | 80 Bytes Fixed = Default record length for a | | | terminal screen padded with blanks. | | | | ------------------------------------------------------------------ | | | | Binary | 256 Bytes Fixed = Default record length for a MPE | | | executable program file. | | | | ------------------------------------------------------------------ Changing File Building Parameters You can change how a file is copied to your local system with the MPE/iX BUILD command parameters of the GET or PUT command using the following syntax: ftp> GET remotefile localfile;buildparms The supported BUILD command parameters are: Table 4-8. --------------------------------------------------------------- | | | :REC=[-rcsizebytes][,blkfactor[,[{F}][,{BINARY}]]]] | | | --------------------------------------------------------------- | | | | | | {V} | {ASCII} | | | | | --------------------------------------------------------------- | | | | | | {B} | | | | | | --------------------------------------------------------------- | | | [;DEV=device] [;CODE=filecode] | | [;DISC=[numrec][,[numextents][,[initialloc]]]] | | | --------------------------------------------------------------- The parameter REC= can also be specified in words (two bytes per word) using a positive integer value. The default blkfactor size is one. HP ARPA FTP supports a subset of the MPE/iX build parameters implemented by the MPE/iX BUILD command. Accordingly, many of the build parameter defaults are overridden by FTP. The FTP build parameter defaults are configured in the ASCII file BLDPARMS.ARPA.SYS and may by modified as desired. Also, users may make local copies and set their own defaults via a file equation like the following. :FILE BLDPARMS.ARPA.SYS=MYFILE See the chapter on "MPE/iX File System and Data Transfers" for more information about FTP and supported BUILD command parameters. For additional information about BUILD parameters, use MPE/iX online help (HELP BUILD PARMS), see the MPE/iX Commands Reference Manual, or read the BLDPARMS.ARPA.SYS file, for more information. Using file building parameters, you can transfer a file as follows: ftp> GET remfile newfile;REC=-80,,F,ASCII In the next example, using CODE=PROG defaults to a target file of fixed binary, 128 words (which are the REC= default values): ftp> GET filex file2;CODE=PROG Transferring Files to Other Groups From within FTP, you cannot change groups on the local system, until 4.5, when "lcd" can be used to change the local directory and thus the group. To transfer files to other groups in your account, you can exit from FTP, and re-log on into the other group, or specify the group name as part of the localfile specified. For example, you could transfer a file named nsprog to NSTEST1 in GROUP1 as follows: ftp> GET nsprog NSTEST1.GROUP1 Transferring Multiple Files To transfer a group of files from the remote system to your MPE/iX system, use the MGET command. For example, transfer a group of binary files beginning with the letter "B" to your MPE/iX system. First verify the files to be transferred: Table 4-9. ----------------------------------------------------------------------------------- | | | ftp> DIR | | | | 200 PORT command okay. | | | | 150 Opening data connection for /bin/ls -l (123.50.42.32,50895) (0 bytes). | | total 33 | | | | drwxrwxrwx 1 myname guest 10 Feb 13 18:44 bprog1 | | | | -rw-rw-rw- 1 myname guest 100 Feb 12 18:42 bprog2 | | | | -rw-rw-rw- 1 myname guest 100 Feb 12 18:42 bprog3 | | | | -rw-rw-rw- 1 myname guest 110 Feb 13 18:43 bprog4 | | | | 226 Transfer complete | | | | nnn bytes received in n.nn seconds (n.nn Kbytes/sec) | | | ----------------------------------------------------------------------------------- Transfer this group of binary files with interactive prompting off: ftp> BINARY 200 Type set to 1. ftp> MGET b* 200 PORT command okay. Opening data connection for bprog1 (123.50.42.32,56077) (nnn bytes). 226 Transfer complete. nn bytes received in n.nn seconds (n.nn Kbytes/sec) 200 PORT command okay. Opening data connection for bprog2 (123.50.42.32,56077) (nnn bytes). 226 Transfer complete. nn bytes received in n.nn seconds (n.nn Kbytes/sec) The sequence of commands are repeated for each file transferred. Check that the files transferred: ftp> :LISTF b@ FILENAME PROG1 PROG2 PROG3 PROG4


MPE/iX 5.0 Express III Documentation