× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks for all the replies.

Tried to use NA 1 and /qsys.lib/backup.lib/*01.savf as the input for MPUT.
It fails with the same error message.

I changed a couple of the save file names to S01xxxxxxx and then tried

na 0
lcd backup
bin
mput s01*.savf

That got the results that I am looking for, except now I have to change my
save generation naming.

I guess I will work with the limitation, although I don't like it much! ;^p

Jim

On Wed, Jul 29, 2009 at 3:40 PM, John McKee <jmmckee@xxxxxxxxxxxxxx> wrote:

How about using NA 1
and then put /qsys.lib/.....


I am only guessing, but I believe that the message you get is trying to
tell you
that the * character is invalid for a library/filename. By using NA 1,
you step
over that.

John McKee

Quoting Jim Essinger <dilbernator@xxxxxxxxx>:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.