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


  • Subject: OK to change QCCSID from 65535 to 37?
  • From: bvining@xxxxxxxxxxxx
  • Date: Mon, 14 Sep 98 12:12:58 CDT

>
>Does anybody know why the untranslateable 65535 is still the default?
>

A strong desire for continued employment?

Seriously, changing the QCCSID default value from 65535 to the preferred
value (as documented in the National Language Support Appendix) should
cause minimal impact to those systems that run in only one national
language and CCSID.  But it could be an absolute nightmare for a
multi-lingual or multi-CCSID system, which has been running effectively
(perhaps not safely but good enough for the user) with 65535 since
V2R1.1, that is suddenly thrown into an active CCSID conversion
environment.  Trying to explain what all may go wrong in this situation
is difficult without pictures (and lots of hand waving) but historically
"incorrect" data that has been viewed for years as "correct" will
suddenly be "correctly" converted by the system to what the user will
now perceive as "incorrect" data (if you follow all that).

Bruce Vining


+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.