Hi Dennis
Here is a link to the ibm site.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzakb
/rzakbmsttdccsid.htm
It looks though like the redefining of the CCSID will only work in the
following situations.
For logical files, the following characteristics must be true before the
CCSID keyword is allowed on a logical file field.
If the specified value on the logical file CCSID keyword uses a Unicode
encoding scheme, then the field data type must be G for a UCS-2 Level 1 or a
UTF-16 encoding scheme, and the field data type must be A for a UTF-8
encoding scheme. Also, the corresponding physical file field must be of
types A, G, or O.
If the specified value on the logical file CCSID keyword does not use the
Unicode encoding scheme, then the field data type must be A, O, or G. Also,
the corresponding physical file field must be a G type field and have the
CCSID keyword specified with a UCS-2 or UTF-16 value, or be an A (character)
type field with a UTF-8 CCSID.
So it won't work with the O specs on your physicals, sorry I missed this
fact.
Does SEQUEL support the Unicode data types?
Regards
Neill
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of iseries@xxxxxxxxxxxx
Sent: 20 October 2009 20:52
To: 'Midrange Systems Technical Discussion'
Subject: RE: DBCS issues
If you want to do it with logical files just refine the field as alpha,
but
make sure you specify an appropriate CCSID for the data.
Thanks, Neill, that was very helpful. Is there a document that describes
which CCSID applies to which scenario? For example, how does one determine
which CCSID applies when trying to change an O-type field to A-type when one
knows the data is US English data? (BTW: Tried CCSID(37) and the system
didn't like that - received CPD7928.) I have never seen any down-to-earth
documentation for proper care and feeding of CCSID values, so pointers are
welcome!
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Experience enables you to recognize a mistake when you make it again."
-- Franklin P. Jones
midrange.com
