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

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.

We reverse the steps

Retrieve the file from outside storage to the IFS

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





From: "Vern Hamberg via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: "Vern Hamberg" <vhamberg@xxxxxxxxxxxxxxx>
Date: 13/11/2024 02:34 PM
Subject: Re: ccsid - is this correct from qsys.lib to IFS to remote
storage and back
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Hi Don

I've never used a different CCSID on a copy I've made of a SAVF.

Which CPY* commands are you using?

Beyond that, I've used only used FTP in BINary mode or simple Windows
copy to put IFS copies to a drive on my laptop. Does http put have a
option like ftp, for binary or ascii (text)?

Cheers
Vern

On 11/12/2024 9:12 PM, Don Brown via MIDRANGE-L wrote:

Hi All

I think I have a an issue with the following process but it is not

obvious

to me - perhaps someone will see the error or my ways.

I created a save file and the ccsid is 37

I save a library to the save file

I copy the save file to the IFS and assign ccsid 819 to the created

stream

file

I send the stream file to external storage. (http PUT)

Now I do the reverse

Retrieve the stream file from external storage back to the IFS and the
ccsid on the new file is 819 by default

I copy the file from the IFS to qsys.lib and to ccsid 37

But I can not restore the library.

Is there a problem in the above method I am doing that I am not seeing ?

Thanks

Don





--
This email has been scanned for computer viruses. Although MSD has taken

reasonable precautions to ensure no viruses are present in this email, MSD
cannot accept responsibility for any loss or damage arising from the use
of this email or attachments..