|
On Feb 13, 2018, at 4:53 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:
This character needs to stay as-is:
É
Not become:
Ã■
-----Original Message-----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Tuesday, February 13, 2018 3:45 PM
To: Midrange-L Midrange-l <midrange-l@xxxxxxxxxxxx>
Subject: Re: CPYFRMSTMF & character conversion
Assume you have a magic wand. What would you turn the two byte character into?
Until we know what you want to do with the data we can't really offer useful advice. All we can do is tell you it won't work as it is.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Feb 13, 2018, at 3:09 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:
I'm familiar with CCSID 65535.
The CCSID isn't by choice, it's an OS restriction. The only way to get something other than 65535, is to make an externally-described file, and then CPYFRMSTMF breaks. Is there a way to copy a fixed-width stream file into a single column DDL table?
-----Original Message-----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Tuesday, February 13, 2018 1:32 PM
To: Midrange-L Midrange-l <midrange-l@xxxxxxxxxxxx>
Subject: Re: CPYFRMSTMF & character conversion
Did you read the document I referenced?
In order for translation to work the file must be in a character set that supports conversion. That probably means code 37. You need to find out why anyone thinks it has to be the binary code.
Without translation any two byte character in the source file will always end up as two bytes in the target file.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.