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


  1.  Home
  2. MIDRANGE-L
  3. February 2018

Re: CPYFRMSTMF & character conversion

On Wed, Feb 14, 2018 at 12:10 PM, <dlclark@xxxxxxxxxxxxxxxx> wrote:
Understood. But translation is still being done -- albeit, in
your case, at display time. However, in the OP's case, I was giving to
understand that the data was still displayable as human-readable text
AFTER it was transferred to the flat file. In this case, the flat file is
CCSID 65535 and would NOT be translated for display purposes. Thus, at
least the human-readable text in the flat file would have to be EBCDIC
format.

We are a CCSID 65535 shop. Our data shows up "fine" in green screens.

I don't think it's helpful to talk about the display. That is a
completely separate issue. Yes, I believe OP expressed himself in a
muddled way (saying that È in the stream file should "appear" as È in
the PF, or some such), but clearly the intent was to make sure the PF
contained the desired content, not what that content looked like on
screen.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.