RE: DBCS issues

["Dennis Lovelady" <iseries@xxxxxxxxxxxx>]

Thanks, Chuck:

>    The open data type is probably not so good, at least as compared
> to having chosen Unicode :-(  Either way however, there is going to
> be the problem that the data in the physical file eventually may not
> be representable in an alternate logical view of the data; i.e.

Yes, this is also one of my concerns, and makes me wonder about the wisdom
(pardon the misuse) of doing this particular change to a non-globalized
version of software.  But alas!

Having resolved myself to this, I am trying to understand your example.  Can
you tell the reason for creating the column one way and then changing it -
particularly how this applies to my question?  Are you indicating that
something like this must be done in order for the view to work?  Pardon my
lack of understanding.

>      create table original.filename ( a50 char(50) );
>      insert into  original.filename values('This is 037 text');
>      alter  table original.filename alter column a50 set data type char
ccsid 5035;
>      create view alternate.filename
>          ( a50 ) as
>          ( select cast(a50 as char(50) ccsid 37)
>          from       original.filename   )
>          ;
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"TV is a medium, because it is neither rare nor well done."
        -- Ernie Kovacs