Re: MGET

Dave,

The only difference between GET and MGET (that I can think of) is that GET has two parameters, one for the local filename and one for the remote filename. Whereas MGET has only one parameter for the remote filename. (Local filename will always match the remote one.)

So with individual GET you can do this:

GET file1.txt /tmp/download1.txt
GET file2.txt /tmp/download2.txt
etc.

The remote filenames being file1.txt, file2.txt, and the local filenames being download1.txt and download2.txt. MGET doesn't have an equivalent for that. With MGET you'd have to do this:

lcd /tmp
MGET file*

And then you'd have to rename them from "file1" to "download1" manually.

Otherwise, MGET is identical to running GET multiple times. (It does not combine the files together.... unless, maybe they all have the same name? Seems unlikely.)

Make sure you're using LOCSITE NAMEFMT 1 if you're using IFS paths.


Dave Odom wrote:

I'm trying to use MGET to mass move several files from a non-i
platform (probably a PC server or a *ix box) to the i into the IFS
portion that looks like Windoz or *ix. I can do it one at a time
but when I try to do MGET, to move all files on the source to the
target, I get the impression from watching the action the "getting"
is being done for each file on the source but the i is trying to put
all the files in the same file on the target (the i). Or does MGET
only work like I want on the i?