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



Bruce,

You must have a dandy reference that lists the character set and code
page for each CCSID. I have a lot of trouble finding such a reference
when I need one. Would you post a link?

TIA
Dan Kimmel

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bruce Vining
Sent: Thursday, November 06, 2008 10:27 AM
To: Midrange Systems Technical Discussion
Subject: Re: CPF427D when running with CCSID 37 data in a 5026 job

David,

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.

In your case, CCSID 5035 uses character set 1172 and code page 1027
for SBCS data. CCSID 290 also uses character set 1172, though encoded
with code page 290 (which is not relevant to the message you're
getting). CCSID 37, on the other hand, uses character set 697 -- most
decidedly not the same.

To eliminate the message you can use a compatible character set for
the database and job. If you can't change the character sets in use and
you don't want the message, you will need to remove it/them.

Bruce Vining

David Gibbs <david@xxxxxxxxxxxx> wrote:
Folks:

I've got a CCSID problem that's been bugging me for quite a while.

We've got an application that has it's data and messages stored with
CCSID 37.

When we run the application in a CCSID 5035 job, we get a bunch of
CPF427D messages (sev 10) in the message subfile whenever the database
files are open ("Substitution characters may be used in data
conversion.").

We initially thought the message was showing up because there was no
translation table between CCSID 37 and 5035, but I have determined that
such a translation table does exist (since messages with CCSID 37 show
up fine in CCSID 5035).

All the character fields in the database files contain nothing but
English upper & lower case data. There is no double byte data in the
files.

If we change the database files to CCSID 290, we don't get the message.

Is there something we need to do to the database files so the CPF427D
message doesn't show up?

david

--
IBM i on Power - For when you can't afford to be out of business
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.




Bruce
Bruce Vining Services
507-206-4178
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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:
Replies:

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.