|
Hi Roger
Yes, that changed quite awhile ago - you don't need to pre-create the
SAVF anymore - and it works also with existing SAVFs just fine.
Here's an IBM page on this -
https://www.ibm.com/support/pages/getting-savf-your-desktop-ibm-i-system
- it is dated December, 2019
Interesting that IBM has a similar article for IBM i to IBM i dated
October, 2021, and it uses the older method - but it would not have
needed to -
https://www.ibm.com/support/pages/transferring-savf-one-ibm-i-another-ibm-i-using-ftp
Then there is this link - http://www.midrangenews.com/view?id=1217 -
by Bob Cozzi, from 2011. This includes this paragraph -
If the PC file name ends with .FILE you may optionally rename it toThis is followed by a statement that it works as you described
xxxx.SAVF (for example: COZTOOLSRT.FILE to COZTOOLSRT.SAVF). Having
the .SAVF extension tells the IBM i system to create a save file on
the target. If a file extension of .FILE is detected, a regular
database file is created and that will not be useful to the RSTOBJ or
RSTLIB commands.
If however, a save file already exists on your IBM i system with the
same base name, the system also recognizes that you are transferring
a save file and behaves as you would expect
I like to save typing path names, so for transferring between IBM i
LPARs, I first cd and lcd in namefmt 0, then go to namefmt 1 so that I
can use the .savf extension.
Cheers
Vern
On 6/3/2023 8:42 PM, Roger Harman wrote:
Has something changed?
My recollection is you had to create an empty SAVF on the target and
do a put <whatever> (repl.
-----Original Message-----
From: MIDRANGE-L<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Vern Hamberg via MIDRANGE-L
Sent: Saturday, June 3, 2023 2:13 PM
To:midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Vern Hamberg<vhamberg@xxxxxxxxxxxxxxx>
Subject: 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.Personally, I stick with the default. I rarely use the IFS, and FTP
It can easily be set to default to namefmt 1 (as I do on my
systems) or namefmt 0 which is the IBM default.
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 andThe client isn't aware about any naming format. This is a sole IBM i
client are using the same naming convention.
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
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
