National Language Support (NLS), sometimes called software globalization, enables SAS to function properly outside the United States. This topic covers a few enhancements and migration issues. For full details, read the SAS National Language Support (NLS): Reference Guide in the SAS online documentation.
Here are a few possible problems and their solutions.
SAS 9.1.3 customers who use transport files to migrate from a previous release with an incompatible encoding will encounter an error. For more details, see SAS Note 20578.
Under OS/390 or z/OS, when the default NONLSCOMPATMODE is in effect, SAS does not support substitution characters in SAS syntax. If you run SAS with NONLSCOMPATMODE, you will have to update existing programs to use national characters in place of those substitutions. For example, Danish customers who have substituted the Å for the $ character in existing SAS programs will have to update the SAS syntax to use the $ in their environments.
In a SAS®9 session, data sets are stamped with an encoding attribute when they are output, replaced, or updated (but not when input only). SAS normally uses the encoding attribute to determine whether CEDA transcoding is required.
This is a wonderful enhancement for SAS®9, but you must take care when processing existing SAS 7 and 8 data sets for the first time, because those data sets do not have an encoding attribute. If you are working under the same operating environmnt where a data set was created, and the data set does not have an encoding attribute, then the session encoding is stamped on the data set by default. This could result in an incorrect encoding stamp. You can override the data set's encoding by using the DATA step option ENCODING= or the LIBNAME options INENCODING= and OUTENCODING=.
Starting with SAS 9.1, enhancements to the LOCALE= system option have made the Locale Setup Window unnecessary, and therefore it is no longer provided. For compatibility with servers that are running an earlier relase of SAS, use the %LS macro. This macro replaces the functionality of the Locale Setup Window and sets up the remote SAS environment for data transfer. If you are running SAS®9 on both your client and server sessions, the %LS macro is not necessary.
When a data set uses the ASCII-OEM character set, the MIGRATE procedure does not correctly translate any non-English characters. Currently, only the ASCII-OEM character set is known to have this issue. See the special migration instructions for these data sets.