i have been asked this Question.
We are using your z/OS DB2 database for developing and testing one of our product.
We found that this database is special with its character setting to be JAPAN EBCDIC DB. And this setting make us failed to retrieve GRAPHIC AND LOB datatype values with other language(like Chinese) characters.
So, could you help us do some configuration for implicit character conversion. This action requires admin user privilege.
Another thing we know is that this database’s MCCSID is 24876, but I didn’t find its GCCSID or ASCCSID.
Also if you want to test the setting is effective or not, please verify the
result of this query “select * from GRAPHIC_TB;” to be readable.
**************************************************
I have suggested them
1. Create a table with CCSID as UNICODE.
2 . In order to get the data in a readable format do casting for the columns
Now they are able to see the data properly. but they want know the following
1. is there any way to handle the Default Encoding table.
2. adding implicit character conversion .( i have never done this before).
Since most of the senior resources are Voluntary retirements. so i have to handle all the responsibility.
This may be helpful in the Future but ar of now i am looking out for those 2 things
1. How to change the Default encoding Scheme E to U.( what i have understood is during installation of DB2 the Default Encoding Scheme should be decided in our case it is E. )
there should be someway to change this. ( since my tso id is having all the privileges i can give a try )
2. could you help us do some configuration for implicit character conversion.
The UCS customization process includes the following six steps:
1.Get the original conversion table in text mode.
2.Customize the conversion table in text mode.
3.Generate the binary conversion table.
4.Apply the conversion table to the system.
5.Update the z/OS system for the next IPL.
6.Update the application runtime environment to pick up the new conversion table.
