Re: Changing CCSID

On 03 May 2012 10:13, Scott Klement wrote:

At the very least, is there something I can tell my PC guy to put
into his SQL statement to translate ?

It wouldn't go in the SQL statement... it would go in the driver
configuration. If he's using IBM's ODBC driver, you can go into the
ODBC administration and check/uncheck the "Translate CCSID 65535"
checkbox.

FWiW:

The request _can_ go in the SQL statement for [VAR]CHAR Columns incorrectly defined as FOR BIT DATA [or similarly DDS A[lphanumeric] Fields incorrectly defined as H[ex] or with CCSID(*HEX)] by using the CAST function. For example:

create table binDta
( reallyChar char(10) for bit data
, reallyBin char(10) for bit data
)
; -- table has two /hex/ fields; 1st incorrectly, 2nd correctly

select cast(reallyChar as char(10) ccsid 37) as ReallyChar
, cast(reallyBin as binary(10) ) as ReallyBin
from binDta

The above SELECT should be able to avoid any need for the "forced translation" trickery, and should function well even if that chicanery is in effect.

Regards, Chuck