Hello Don
Just a couple of thoughts:
I doubt if the CCSID is of any matter to the savefile. A CCSID describes how character data should be interpreted. It tells the system which translation table to use to present the bits and bytes on your disk as characters in a medium like an emulator screen or a spooled file. It's a bit more complicated than that, but that's the basics.
If a CCSID changes when you perform some kind of action on the file, then either the contents is converted to meet the new CCSID definition (i.e. going from EBCID 37 tot UTF8 1208) or the CCSID doesn't matter anymore because it's binary data. A video doesn't need a CCSID, but on the IFS it does have one. So 'manually' changing the CCSID attribute does not change the contents, it may corrupt it though.
That being said, in my experience with transferring savefiles, I frequently ran into a corrupt savefile. I don't know the details but in most cases it helped me to create a savefile on the target LPAR first and then transfer the contents to it with FTP. There's probably a good explanation for it, but I never dove into it further.
Hope this helps
Kind regards, Met vriendelijke groet,
Martijn van Breden
lead software architect
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..
--
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.
--
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.
midrange.com
