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

Hi Monty


What you describe is something we once had to do. For at least maybe 20 years now, we don't have to create the SAVF first - what we do is set NAMing to 1 (path naming), and mode to BINary - then use the file extension SAVF - here is an IBM article on this method, last updated last month, even though the technique has been around for decades - https://www.ibm.com/support/pages/getting-savf-your-desktop-ibm-i-system


Regards
Vern


On Wed, 13 Nov, 2024 at 8:04 AM, Monty G. James via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:


To: 'midrange-l@xxxxxxxxxxxxxxxxxx'
Cc: monty.james@xxxxxxxxxxxxxx
date: Wed, 13 Nov 2024 16:46:51 +1000
from: Don Brown via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
subject: Re: ccsid - is this correct from qsys.lib to IFS to remote
storage and back

Does the empty savf exist in the qsys.lib file system location that you are sending it back to or is the FTP process creating it when you send it back?
If the savf does not exist then you will get an unreadable file in the qsys.lib file system.
You will need to use a (replace on the FTP put or get command when you send it back to the qsys.lib files system.

Hi Vern,

I have retraced my steps and this is what I see specifically.

I> have created a new save file.

If I use wrklnk '/qsys.lib/,,,,/savefile.file' option 8=Display
attributes shows ccsid of 37

I then used ftp in binary mode to put that save file to the IFS.

The file in the IFS shows ccsid 819

The IFS file is then sent to outside storage.

If it does

We reverse the steps

Retrieve the file from outside storage to the IFS

The empty savf needs to exist in the target location before the next step.

Used ftp in binary mode to transfer the file from IFS to qsys.lib file system

dspsavf savefile fails.

I am just rerunning this test to make sure as we have made a couple of changes.

Thanks

Don

________________________________

This email message, including any attachment(s) is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient, please immediately contact the sender by email.