Re: FTP question

Hi Patrik

I find I use FTP mostly for moving SAVFs around, either uploading to the i, but more moving objects from LPAR to LPAR. For that, you use bin instead of ascii transfer type, and you specify nam 1 - then I usually do cd and lcd (actually first, when it is nam 0, because there is less to type!) Then to transfer the SAVF, you use put filename.savf - if you don't, if you use something like filename.file, it creates a PF on the i.

Neat trick, very handy extension for IBM i FTP only.

Cheers
Vern

On 6/3/2023 3:25 AM, Patrik Schindler wrote:

Hello Jim,

Am 03.06.2023 um 01:04 schrieb Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>:

The default directory name convention is set by the FTP server. It can easily be set to default to namefmt 1 (as I do on my systems) or namefmt 0 which is the IBM default.

Personally, I stick with the default. I rarely use the IFS, and FTP is most often a manual process, not automated. Using namefmt 1 needs much more typing.

Best to pick which one you want and set it when the session starts.

In addition, the FTP server automatically changes namefmt to 1 for a given session if you issue any request to a remote path starting with a /.

By issuing the command you then make sure both the server and client are using the same naming convention.

The client isn't aware about any naming format. This is a sole IBM i server side thing.

I sometimes use mget/mput even with namefmt 0. This works expectably if you have a local subdirectory named like the library on the server side. You end up with FILE.MEMBER files on the local side.

Lots of fun when the two are different.

Not at all. The user must be aware of the differences. Many "problems" are omitted when you always use local and remote file names accordingly, not just "directories", letting the FTP client fill out the file name.

:wq! PoC