Re: How to display Unicode in SQL

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

OK, so "no conversion" has really meant that for some time. Just have not 
had to deal with this before - never came up.

Thanks

At 02:04 PM 9/15/2004, you wrote:




> I believe this implicit conversion support to job CCSID was actually done
> back in either V3R7 or V4R1.  I did try this on a V5R1 system and it worked
> as expected (no conversion if the job is 65535, conversion if not 65535).
>
>
>
>
>              Vern Hamberg
>              <vhamberg@centerf
>              ieldtechnology.co                                          To
>              m>                        Midrange Systems Technical
>              Sent by:                  Discussion
>              midrange-l-bounce         <midrange-l@xxxxxxxxxxxx>
>              s@xxxxxxxxxxxx                                             cc
>
>                                                                    Subject
>              09/15/2004 01:38          Re: How to display Unicode in SQL
>              PM
>
>
>              Please respond to
>              Midrange Systems
>                  Technical
>                 Discussion
>
>
>
>
>
>
> That did it, too. Sounds like another consequence of V5R3 changes with
> 65535 - is that the case? Does a V5R2 machine work with 66535?
>
> Just curious
> Vern
>
> At 12:20 PM 9/15/2004, you wrote:
>
>
>
>
> >Is your job CCSID 65535?
> >
> >On my system:
> >
> >chgjob ccsid(37)
> >strsql
> >select * from ucsfile
> >
> >shows my UCS2 (13488) data converted to my job CCSID.