Re: ccsid - is this correct from qsys.lib to IFS to remote storage and back

Hi, I see.

The only pitfall I can see using NAMEFMT 1 is that you give up the implicit
control on the GET over NOT empty SAVF. If the SAVF is not empty you have
to add (Replace.

Best regards
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno gio 14 nov 2024 alle ore 15:02 Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> ha scritto:

Thanks, Rob. And Marco, here's a link to the IBM article that says more
https://www.ibm.com/support/pages/getting-savf-your-desktop-ibm-i-system
- it shows both PUT and GET.

What I don't understand is why IBM also have an article that says to
create the SAVF first.

I often do a variation on this technique - I will CD (change directory)
in NAM 0 to the library where I want to PUT the SAVF - then I execute
QUOTE SITE NAM 1, and I don't have to type the path name on the object -
lazy typist here!

So it could go something like this -

CD MARCO
BIN
QUOTE SITE NAM 1
PUT X X.SAVF

Cheers
Vern

On 11/14/2024 6:50 AM, Rob Berendt wrote:

Marco,
Stop using namefmt 0, or the LIBRARY/OBJECT file system, to transfer save
files.
Use namefmt 1, or the /qsys.lib/mylib.lib/mysavf.SAVF, file system.
Then you no longer have to precreate the save file, IF, you use that

.savf

extension.

On Thu, Nov 14, 2024 at 7:27 AM Marco Facchinetti <
marco.facchinetti@xxxxxxxxx> wrote:

Hi Vern, mind elaborate a little further?

I ask because (via Ftp on my Pc):

BIN
GET QGPL/X

PUT X MARCO/X

and the new file created in library Marco is a PF-DTA not a SAVF (X in

QGPL

is a SAVF).

TIA
--
Marco Facchinetti

--
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
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.