Re: CPF427D when running with CCSID 37 data in a 5026 job

[Bruce Vining <bvining@xxxxxxxxxxxxxxx>]

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