No theories off hand, but a couple of questions hoping something comes
out.

1.  What is the hex value for the Greek A in the original file?  Is it
    x'41' (Greek Capital Letter Alpha) or x'71' (Greek Capital Letter
    Alpha with Tonos)?  Use DSPPFM/F10/F11.

2.  What is the hex value for the "missing" character in the new file?
    Use DSPPFM/F10/F11.

3.  Are all occurrences of the Greek A (which ever one it is) missing?
    If not, is there something the "missing" characters have in common
    (first in field, last in field, etc.)

4.  Are no other Greek characters "missing"?

5.  What type of emulator is being used to display the Greek A?  Has
    this software changed also?

6.  Does DSPFFD of both files show the same field level CCSID?

7.  And basically any other information that you may have on the
    situation.

Bruce

>
>We create conversion programs for every upgrade of our software.  This program
>renames the PFs, creates an updated version and then copies data from the old
>to
>the new.
>
>One of our clients run these conversion programs, and their PFs end up with a
>CCSID of 875, which is the correct code for Greek characters. But after the
>CPYF
>even though both the old and new have a CCSID of 875 the Greek character 'A'
>disappears in the new file and cannot be seen on query screens or on any
>display.
>
>Any ideas why this problem is occurring?
>
>Regards
>
>Tunde
>


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].