When you sign on to a SAS/CONNECT 8.2 server that is running with a double-byte character set (DBCS) encoding from a client that is running with the DBCS Shift-JIS encoding, you might receive the following warning:

WARNING: The client session encoding is shift-jis while the server session is using an unsupported encoding. Data may not be transmitted correctly.

This problem can occur even if you specify -DBCSLANG Japanese. Most likely, the problem occurs because the -DBCSTYPE settings for the client and the server are different.For example, suppose you have a SAS®9 Windows client session that is started with the following options:

This Windows client session then starts a SAS^® 8 server session in a UNIX environment with the following options:

In this case, the warning is issued because SAS 8 does not have a character encoding ID (CEI) in its requirements vector. As a result, SAS®9 client cannot detect the encoding of the remote session. The default setting assigned to -DBCSTYPE in the Windows client is PCMS. You can avoid the warning if you set -DBCSTYPE to PCMS on both sides. For example, when you start the SAS 8 session, change the -DBCSTYPE setting as follows:

Operating System and Release Information