×
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.
Database chose to warn the user of a possible problem. Message Handler, in their implementation, obviously did not. For consistency it should be one way or the other across the board, but I doubt that we really want more instances of that message ;) I personally wish there was a way to tell database "it's OK, I know and take responsbility for this". But if there is a way I don't know it.
Database, of course, is also more concerned with loss of character representation when storing the data. MH is more a retrieve and toss scenario.
Bruce
David Gibbs <david@xxxxxxxxxxxx> wrote:
Bruce Vining wrote:
The operative word in the error is MAY. Database is warning you that
the character sets supported by the two CCSIDs do not match, so at
run time substitution could occur.
Hmmm ... OK. That makes sense.
Given that, why don't I get similar messages when a program retrieves a message from a message file that has CCSID 37 in a 5026 session.
david
As an Amazon Associate we earn from qualifying purchases.
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.