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



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi David,

Are you absolutely certain that your source physical file on your UK box is
CCSID 037? It could now be 285. This may be what is causing your
mistranslation.

In 037, $ is x'5B'.
In 285, $ is x'4A'.
In 285, x'5B' is <pound currency symbol>.

The the hex representation of the $ in the source physical file, possibly
via DSPPFM would show something.

As for how to work out how it got there, here goes my understanding.

When keying data in and writing it to disk, the keyboard type, display file
CCSID, job CCSID & disk file CCSID all have a bearing on what occurs.

In your case, the display file, if the keying in is done via SEU, should not
have too much bearing on what is occurring. The answers to keyboard type
(real or emulated), job CCSID and disk file CCSID should at least tell us
what is happening on the input side of the CPYTOSTMF.


Regards,

Kevin Wright

> -----Original Message-----
> From: David Gibbs [mailto:david@midrange.com]
> Sent: Sunday, 8 December 2002 1:37
> To: midrange-l@midrange.com
> Subject: RE: CPYTOSTMF character translation redux
>
>
> At 07:56 PM 12/6/2002, you wrote:
> >It isn't clear what you mean by "translated incorrectly". Do
> you mean the
> >hex value is incorrect or that it displays incorrectly?
>
> A dollar sign typed into the source pf shows up as something
> other than a
> dollar sign in the stream file.
>
> >In particular, is the hex representation of the "$" (US dollar sign)
> >correct when the file is viewed in hex? If it is, then I'd
> look at the
> >character set being used by whatever device is doing the display.
>
> To be honest, I haven't looked at the hex representation of
> the characters
> ... I really don't expect any weird translation to occur, as
> a dollar sign
> is part of both the basic ascii & ebcdic character set.
>
> The source pf is a standard ccsid 37, and the stream file code page is
> *PCASCII ... that translation does not seem like it should be rocket
> science to me.
>
> david
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.