Double byte from EBCDIC to ASCII. (Tom L. Deskevich) -- MIDRANGE-L

Subject: Double byte from EBCDIC to ASCII. (Tom L. Deskevich)
From: "Tom L. Deskevich" <tld@xxxxxxxxxxxxx>
Date: Mon, 17 Oct 2016 12:33:32 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Jon, I have to say I do not know the double byte character set.
But that is the CCSID (65535) we use for file creation is our standard for
any language that uses symbols and such for the language.
I am creating the extract files, so I have some flexibility.

Chuck, so I should use CCSID 1209 for UTF8?
The CPYTOIMPF ignores all CCSID codes except 65535, so I guess I need
another utility to do this?

The client access method just doubles up the record length, to produce the
double byte information the way I read it.

Thanks
Tom Deskevich

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Double byte from EBCDIC to ASCII. (Tom L. Deskevich) , CRPence
Re: Double byte from EBCDIC to ASCII. (Tom L. Deskevich) , Jon Paris

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.