In order first: UTF-EBCDIC
Of course in wikipedia is a description of UTF-EBCDI http://en.wikipedia.org/wiki/UTF-EBCDIC , like good. And on site IBM there is a link http://www-01.ibm.com/software/globalization/ccsid/ccsid_registered.html on CCSID 1211 (UTF-EBCDIC) , But there is no full description of the code page. And By default, in system z/OS v1r13 does not install the code page CCSID 1211 . So I de facto work only encoding IBM-1047 on z/OS. second: ASCII<>EBCDIC I have long tested z/OS in work with EBCDIC. And pax , and tar | iconv ,and chcp And optimal variant ftp server on z/OS. that is, I unzip the archive on loclahost and ftp-client send to the server z/OS files. Course *.с *.h *.pl files are encoded in UTF-8 . But only in comments , in documentation , in test there are multibyte encoding. so the majority of of errors in test are accounted for incorrectly conversion UTF-8<>EBCDIC and check UTF-8 . ------------------------------------------------------------------------ Yaroslav Kuzmin Developer C/C++ ,z/OS , Linux 3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia Tel: +7.922.2.38.33.38 Email: [email protected] Web: www.rocketsoftware.com ________________________________________ From: [email protected] <[email protected]> Sent: 14 April 2014 22:43 To: Yaroslav Kuzmin; Karl Williamson; [email protected]; demerphq; [email protected]; Perl5 Porters Subject: Re: НА: Fwd: Re: USSP-37: Info Request for Perl Fwd: EBCDIC support is onthe chopping block Yaroslav, I did not have a question. Karl Williamson asked "I am curious how Rocket gets things going from a tarball? That is in ASCII and UTF-8, with more and more in UTF-8 beyond ASCII. I could not find anything that would convert to UTF-EBCDIC, so one of the procedures is to run a script I wrote that does the conversion." Karl Nordstrom On 04/14/2014 12:26 PM, Yaroslav Kuzmin wrote: > Hi Karl, > > Thanks for the examples ;). > > But, What is the question ? What do you want to know ? > > Thanks. > > ------------------------------------------------------------------------ > > > Yaroslav Kuzmin > Developer C/C++ ,z/OS , Linux 3 Zhukovskiy Street · Miass, > Chelyabinsk region 456318 · Russia Tel: +7.922.2.38.33.38 Email: > [email protected] Web: www.rocketsoftware.com > > ________________________________________ From: > [email protected] <[email protected]> Sent: 14 April > 2014 21:11 To: Karl Williamson; [email protected]; Yaroslav Kuzmin; > demerphq; [email protected]; Perl5 Porters Subject: Re: НА: Fwd: > Re: USSP-37: Info Request for Perl Fwd: EBCDIC support is onthe > chopping block > > I have used pax to convert character sets. > > http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1p03.html > > You can set an environment variable in your .profile to handle > conversion from ASCII to EBCDIC for text files contained in > archives. Here is an example showing how to set an environment > variable called A2E and then use it: > > $ export A2E= '-ofrom=ISO8859-1,to=IBM-1047' > > $ pax $A2E -rzf foobar.tar.Z > > Also, the command: > > pax -wf tpgm.pax -oto=IBM-1047,from=ISO8859-1 /tmp/posix/tpgm > > backs up the /tmp/posix/testpgm directory, which is in the > character set CP1047, into an archive file that is targeted to an > ASCII character set(IS646). > > On 04/13/2014 10:44 PM, Karl Williamson wrote: >> On 4/12/2014 5:56 AM, Jarkko Hietaniemi wrote: >>> On Saturday-201404-12, 1:13, Karl Williamson wrote: >>>> blead contains many fixes for EBCDIC support that aren't in >>>> 5.16, such as to charclass_invlist.h. There is no sense in >>>> you trying to refix these. The branch khw/ebcdic has even >>>> more fixes, mainly to tests to make them EBCDIC aware. Last >>>> we tried it we were up to about 92% of core tests passing, >>>> most of the failures were due to one bug, I believe, >>>> involving pack/unpack, and to-be-expected porting tests that >>>> just need to be changed to be skipped on non-ASCII >>>> platforms. >>> >>> Sounds good! >>> >>> Karl: to kick things off, maybe you could prepare a >>> snapshot.tar.gz of your branch for Yaroslav, something concrete >>> to try out immediately? I have no idea (but I have my doubts) >>> that the z/OS UNIX tools might not include git. This would >>> complicate things somewhat. >>> >>> Yaroslav: take a look at http://www.test-smoke.org/ and >>> http://www.test-smoke.org/FAQ.html - that is what you need to >>> set up an automated periodic "smoke build". A continuous >>> build would be the best, daily build would be okay, a weekly >>> build kind of acceptable. (Of course depends on how powerful >>> systems you have: on older systems it was not unusual for a >>> single build to take more than a day!) >>> >>>> This is the branch that ongoing work should start with. I am >>>> willing to work with you to get it to really work, but only >>>> if we identify a smoker for ongoing testing. Without this, >>>> the pumpking has decreed, and I fully agree, EBCDIC support >>>> will be dropped. Instead of now working to root out the bugs >>>> you've found, which are likely already fixed in blead, we >>>> should be working to get a smoker identified, one with a >>>> long-term commitment to its continued availability. >>>> >>> >> >> That branch requires some undocumented boot-strap procedures to >> get it going on an EBCDIC platform. I am not actually in a >> position to do much currently until I recover more from traffic >> accident injuries. Hopefully the 5.16 port is good enough to try >> smoking. >> >> I am curious how Rocket gets things going from a tarball. That >> is in ASCII and UTF-8, with more and more in UTF-8 beyond ASCII. >> I could not find anything that would convert to UTF-EBCDIC, so >> one of the procedures is to run a script I wrote that does the >> conversion. > > -- Karl Nordstrom Storage Systems Group Information Technology > Services The Pennsylvania State University (814) 863-1936 > -- Karl Nordstrom Storage Systems Group Information Technology Services The Pennsylvania State University (814) 863-1936
