Re: Weird result creating a SAVF via FTP

Hello Patrik

Yes, it was a later add-on - my intent was to suggest that in my post by saying there was an older document - I think I was too subtle in my post!

I don't remember when this feature was added, but it was before 2013, because I remember learning of the "enhanced" feature while working at RJS Software, which was 2005-2013

Now I am searching the MIDRANGE archives for this subject. I found a post from Mel Rothman from January, 2005 - https://archive.midrange.com/midrange-l/200501/msg01154.html - here is the content of that post -

Another alternative is to take advantage of the fact that when IFS naming conventions are used, the save file is created if doesn't exist. This is done by using namefmt 1. In the following example, if save file mylib/yoursavf doesn't exist, it is created. Otherwise, it is replaced.

bin
namefmt 1
lcd /qsys.lib/mylib.lib
cd /qsys.lib/yourlib.lib
get yoursavf.savf (replace
quit

By the way, Mel wrote the original CGIDEV tools that were improved by Giovanni Perotti (RIP, as he passed away early this year).

Regards
Vern

On 10/10/2024 4:18 PM, Patrik Schindler wrote:

Hello Vern,

Am 10.10.2024 um 22:43 schrieb VERNON HAMBERG Owner via MIDRANGE-L<midrange-l@xxxxxxxxxxxxxxxxxx>:

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

Maybe the automatic creation of a missing file (when using the UNIX style namefmt) was a later add-on to the FTP server?

:wq! PoC