You need to switch your SAS server environment to Unicode (UTF8) encoding. It may not be using it currently.
Try connecting with Enterprise Guide and running "proc options option=encoding; run;". If it says anything other than UTF8, you can use Chinese until you switch to UTF8.
If it is confirmed that you need to switch the encoding, this is quite a major change in the way SAS works, so do not attempt this switch on a live production environment if it is already operational and in use by the users - unless you have first tested it extensively in your non-prod environment (if you have one) have plenty of downtime window and you have properly backed up everything, e.t.c. It's easier if it is a brand new environment only being configured.
Normally the UTF8 encoding is selected at the time SAS is installed ("Use SAS as Unicode server" checkbox") but it can be switched after the fact: http://support.sas.com/kb/51/586.html
After the switch, you will certainly need to recreate the MAMisc.Sequence dataset - SAS MA won't work until you do it. Use Enterprise Guide:
proc sql;
create table MAMisc.Sequence_copy as select * from MAMisc.Sequence;
drop table MAMisc.Sequene;
create table MAMisc.Sequence as select * from MAMisc.Sequence_copy;
run;
Depending on your environment, if your or custom stored processes store and update datasets in Base SAS libraries, you may have other base SAS datasets that need to be migrated / recreated with the new encoding. MATables library should be fine though (you can leave it as is).
Your users will also need to use "K functions" in calculated variables instead of traditional text manipulation functions (length, cat, find, substr etc).
-------
Dmitriy Alergant, Tier One Analytics