Re: DBCS issues

The first CREATE and INSERT were to express the origin of the original table and data, as it existed prior to the /switch/ of "most of its descriptive\name fields from (A) Alphanumeric to (O) DBCS-Open data types." The ALTER intends to reflect the table since the switch from Alpha to Open. The next INSERT was there to mimic possible future inclusion of DBCS data, since that would then have been allowed. After all of that setup, the /original/ qualified filename, in library named ORIGINAL :-), should be representative of a table against which the unchanged SEQUEL queries would presumably still be defined.

The goal was to find a way to create the original file name as a VIEW of the same name in an alternate library. The CREATE VIEW establishes the same filename in an alternate library, in library named ALTERNATE :-), which should be representative of a new VIEW against which the unchanged SEQUEL queries can now be run, simply by OVRDBF FILENAME TOFILE(ALTERNATE/FILENAME) or TOFILE(*LIBL/FILENAME) after also ADDLIBLE ALTERNATE *FIRST. Hopefully that makes sense.?

Regards, Chuck

Dennis Lovelady wrote:

CRPence wrote:

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;
<ed> insert into original.filename values(x'0E0F');
create view alternate.filename ( a50 ) as
( select cast(a50 as char(50) ccsid 37)
from original.filename );