Re: Weird result creating a SAVF via FTP

[VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx>]

Justin - this is spot on - the use of NAMFMT 1 and the SAVF extension is an IBM i - only extension, so that the transfer doesn't create a PF Here are a couple docs on this topic -


Getting a *SAVF from Your Desktop to an IBM i System
     https://www.ibm.com/support/pages/getting-savf-your-desktop-ibm-i-system


BTW, you also need to set things as s BINary transfer.


I just looked at the FTP manual at 7.2 - I find it confusing where SAVFs are concerned. Looks like the example uses a GET subcommand to PUT a SAVF on the i - oh, well, the above document is clear.

There's an older document that says pre-create the SAVF, in order to prevent the transfer resulting in a PF. Oh, well!


Cheers
Vern


On Thu, 10 Oct, 2024 at 1:05 PM, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:
 

To: midrange-l

Can't you just bypass the create step and have the PUT create the save file?

namefmt 1   #  set to IFS naming
put file.savf /QSYS.LIB/mylib.LIB/mysavf.savf

It's been a while, so my IFS path might be a bit off.


HTH