Slight variation of this topic. I primarily work with systems in two
countries: Germany and USA. On each of these systems, my profile's CCSID is
set to 37. DSPJOB option 2 shows 37 for CCSID, 37 for Default CCSID.
When I go to into QSH on either system and type a command like "touch
new_file" then a new file will be created with CCSID 37. So far so good.
But now I want to interchange files from one system with the other. The
files I want to interchange (from the German system) are all CCSID 819. I
use a command like "tar cvf mytar.tar path_to_files" to package these files.
Interestingly the tarball is created with CCSID 819. (I don't know why this
would be, but I like it - I think.)
Now, I ftp the file to my PC. Because of security restrictions, in order to
get the file to the USA system, I have to make a pit stop at a local server:
FTP to intermediate server from PC. Log in to USA system and FTP from
intermediate to me. All FTP done in strict BINARY mode.
Now the tarball is CCSID 37 on the USA system. But I'm successful
(apparently) in untarring with tar xvf.
However, the untarred files are all CCSID 37. More importantly, they don't
operate as expected. For example, I usually do this with .JAR files, and I
invariably end up with complaints from JAVA about the central directory
being corrupted or some such. I've also tried certain binaries (such as the
AIX ZIP/UNZIP suite), and those don't run either. The QSH command
"setccsid" doesn't seem to help (although it does set the CCSID of the
file), and I'm quite confused as to why this would be.
Any pointers?
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A lawyer is a learned gentleman who rescues your estate from your
enemies... and keeps it for himself."
-- Henry Broughman
midrange.com
