Very Unusual ftp dir get and mget results

[Rich Wright]

I ftp to site.
cd to "incoming" directory.
dir shows two files.
ap.husbaan100.inbound.0212121548
ap.husbaan140.inbound.0212121548
dir ap* (shows no files.)
dir *inbound* (shows no files.)
dir *100* (shows only the first file.)
dir *140* (shows only the second file.)
dir *0212* (shows both files.)
get ap.husbaan140.inbound.0212121548 (works)
ftp> mget * (does not work)
mget *? y
Error opening local file *.
> *:Invalid argument

In summary, numeric matching seems to work, but not alpha.
mget does not want to work no matter what.

get seems to work OK.

What is going on here?

[Jeff Schussele]

Hi Rich,

Sounds like file name globbing is disabled by default.
At an ftp> prompt enter
glob
and then try your wildcards again.

HTH,
Jeff

[Rich Wright]

I had already tried toggeling "glob" option with no success.
Since my initial post, I discovered that UPPER CASE letters would match.
dir AP* (shows both files)
mget AP* (will get both)

My guess is that the files are stored as upper case and ftp is mapping to lower case before displaying results to me.

Does this sound possible?

[Patrick Wallek]

What type of machine are you ftp'ing to? I suppose this MIGHT be possible if you were ftp'ing to some sort of Windoze machine.

[Jeff Schussele]

Certainly, especially if the ftp server is a UNIX system.

I don't think it's translating - it's just being literal.

You can try
ftp> case
to get the server to switch cases & test the wildcards on the mget command.

Rgds,
Jeff

[Judy Traynor]

Try mget \**