Comments on: FTP subcommads

By: Brilliant145

Brilliant145 — Thu, 08 Nov 2012 15:30:07 +0000

However have tried BIN, as my friends said have created new savf on target iseries machine followed below cmd from my PC
put Target.LIB/XXX.savf Target.LIB/XXXX.savf
it worked fine, thanks to all

By: TomLiotta

TomLiotta — Tue, 06 Nov 2012 08:34:09 +0000

I think you also need to set the mode to BIN…

Definitely. There should be no character conversions allowed for savefile data.

Tom

By: ToddN2000

ToddN2000 — Mon, 05 Nov 2012 20:19:22 +0000

In addition to doing the FTP in BIN (binary mode) another possible problem can happen if you are trying to transfer this SAVF to another i-Series. It may be that the target system is on a different release. In that case you need to create a new SAVF with the target release set properly.

By: TomLiotta

TomLiotta — Fri, 02 Nov 2012 19:48:35 +0000

For most practical circumstances, there are two types of extensions that make a difference to iSeries: .SAVF and everything else. The .SAVF extension (upper-/lower-case doesn’t matter) can be automatically recognized as a savefile. Everything other than .SAVF will be handled as a plain old physical file.

This only matters for uploads/downloads through the /QSYS.LIB file system. If you’re working through a basic /root file system directory, the extension is irrelevant. All transfers in to or out of /root are straight streamfile transfers.

If any other extension is used for a savefile, you must use CRTSAVF to pre-create the savefile to receive a transfer and retain the savefile format. It can take a couple practice runs to get the hang of it, but it’s reasonably simple once you see it work. Basic tests are easy to set up.

Tom