×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Shalom,
you can use the qsh command setccsid like this:
setccsid 819 mytarball.tar
Once again -- this will set the CCSID of the tarball. The CCSID of the
tarball is irrelevant, since the TAR utility doesn't use it. Running
this setccsid command would accomplish the same thing as changing the
CCSID on the FTP -- it'd accomplish nothing. The CCSID of a tarball is
meaningless since a tarball is not a text document.
What's important here isn't the CCSID of the tarball, but the CCSID of
the files that are extracted FROM the tarball. If you set the
QIBM_CCSID envvar prior to the extraction, they will get created with
CCSID 819 instead of 37 -- which is probably what you want.
(You could use the setccsid utility AFTER the extraction, but you'd have
to run it invdividually on each file that was extracted -- or use it in
conjunction with the "find" utility -- but it's a lot easier, IMHO, to
just set QIBM_CCSID prior to the extraction. )
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
