The following options
are not implemented in the SPD Server NLS functions:
The LIBNAME option
OUTENCODING=<client-server encoding>
is not supported and
will produce a WARNING message if submitted to
sasspds.
In addition, the related
data set option
ENCODING=<client-server encoding>
is supported by the
SAS LIBNAME engine for OUTPUT data sets only. Character data is assumed
to be in the encoding of the session that initiates the CONNECT to
SASSPDS and is normally stored using that encoding. ENCODING= will
cause SPD Server to transcode from the SAS session encoding to the
specified encoding for storing data. If you specify ENCODING= for
a data set that is not an OUTPUT data set, and if the encoding value
that you specify does not match the data set's encoding, when you
open the data set, SPD Server produces a warning:
ENCODING= specified on table open fails to match table
encoding. Option ignored.
The LIBNAME option
TRUNCWARN=YES
Suppresses hard failure
on NLS transcoding overflow and character mapping errors. When using
the TRUNCWARN=YES LIBNAME option, data integrity can be compromised
because significant characters can be lost in this configuration.
The default setting is NO, which causes hard Read and Write stops
when transcode overflow or mapping errors are encountered. When TRUNCWARN=YES,
and an overflow or character mapping error occurs, a warning is posted
to the SAS log at data set close time if overflow occurs, but the
data overflow is lost.