× 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.



A bit more information would be useful.

“Double byte” doesn’t really tell us anything. _Which_ double byte character set?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Oct 17, 2016, at 11:27 AM, Tom L. Deskevich <tld@xxxxxxxxxxxxx> wrote:

I need to extract a file that is double byte with CCSID 65535 and convert
EBCDIC to ASCII.

Since the files are created on a global partition, the rule is to always use
65535 CCSID.

But when I do a CPYTOIMPF, I get garbage in the fields with CCSID 65535.

We are just using this in the USA for now. But it may eventually be used in
ASIA.

So changing the CCSID works in the USA for my extract file, but need to
eventually produce the data in ASCII for ASIA.

I see that Client Access data transfer has a forced translation switch you
can set for this.

Is this the only option for automatically converting double byte from EBCDIC
to ASCII?



Thanks.



Tom Deskevich

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.