Re: FTP using MPUT to unix does not allow wild card

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

hi Jim,

This error has nothing to do with the Unix system.  It's purely within 
the IBM i system.  When you type MPUT, under the covers the FTP client 
gets a list of files in your current directory/library that matches the 
pattern, then loops through that list doing a STOR (the underlying 
command behind PUT) for each individual file.

So if you type MPUT *1.savf, your IBM i FTP client gets a list of files 
on it's current directory (which is local, not on the Unix box!) that 
match the wildcard, then loops through and sends each one.  That's how 
FTP works.

I think you'll find that you can do "MPUT *.savf" but you cannot do 
"MPUT *1.savf".  This is a limitation in IBM's FTP client for i.  I 
think you'll find the same problem no matter what type of system you 
send to.



Jim Essinger wrote:
> I am trying to put a group of save files on a server, and it will not allow
> me to us mput and specify *01.savf as the generic name.
>
> When I connect from the i5/os FTP it allows me to log in, then I get the
> following message;
>
> UNIX Type: L8
>
> When I use PUT and the entire file name, the file gets sent.  When I use the
> MPUT *01.savf command I get the following error;
>
> Character (*) is not allowed in object name.
>
> Can I not use a wild card with MPUT to this type of file system?  Is there
> another wild card to use that means the same thing?  I don't want to send
> all the save files to the server, just the ones that are named ending in 01
> (I have 01, 02 through 10 as generations of saves).
>
> I searched the archives and thought that I could use the * for a wild card.
> Any thoughts?
>
> Jim