× 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.



So, Leif, are you creating your own SAVFs on the PC? Who but you? ;-)

The .sav makes no difference, as that is on the client end. And you do specify a qualified SAVF name at the destination.

Using .savf, as Martin describes, works only when using NAMEFMT 1 - you're using NAMEFMT 0, so you need the preexisting SAVF.

Regards

Vern

At 02:34 PM 1/29/2003 +0000, you wrote:
On Wed, 2003-01-29 at 14:11, Leif Svalgaard wrote:
> From: <kirkg@manageinc.com>
>
> > Now I don't do a lot of FTPing, but the only time I use "binary" is for
> > savefiles.  What type of file are you transferrring? If it's a savf then
> > drop the .sav
> >
>
> it was a save file, but why would dropping the .sav make any difference?
> Is the system trying to be smart? and end up being dumb instead?

You should be able to ftp the file as xxxx.savf and the system will
create the save file for you. Otherwise I don't think ftp is bothered by
the extension. .savf seems to be the only 'special' extension that
alters the way OS/400 ftp deals with the file, but if there are others
I'd be interested in knowing them. If the file member is being 'put'
without qualifying the target member, then I think a .mbr extension is
preferred - but that may be just a Linux -> OS/400 thing.

Regards, Martin


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.