SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

94 ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS= LIBNAME Option 4 Chapter 10SyntaxADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES | NOSyntax DescriptionYESindicates that column lengths are divided by the DBSERVER_MAX_BYTES= valueand then multiplied with the DBCLIENT_MAX_BYTES= value. So ifDBCLIENT_MAX_BYTES is greater than 1, thenADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES.NOindicates that any column lengths that byte semantics specify on the server are usedas is on the client. So if DBCLIENT_MAX_BYTES=1, thenADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=NO.ExamplesWhen ADJUST_BYTE_SEMANTICS_COLUMN_LENGTHS=YES, column lengthsthat byte semantics creates are adjusted with client encoding, as shown in this example.libname x3 &engine &connopt ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES;proc contents data=x3.char_sem; run;proc contents data=x3.nchar_sem; run;proc contents data=x3.byte_sem; run;proc contents data=x3.mixed_sem; run;In this example, various options have different settings.libname x5 &engine &connopt ADJUST_NCHAR_COLUMN_LENGTHS=NOADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=NO DBCLIENT_MAX_BYTES=3;proc contents data=x5.char_sem; run;proc contents data=x5.nchar_sem; run;proc contents data=x5.byte_sem; run;proc contents data=x5.mixed_sem; run;This example also uses different settings for the various options.libname x6 &engine &connopt ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YESADJUST_NCHAR_COLUMN_LENGTHS=YES DBCLIENT_MAX_BYTES=3;proc contents data=x6.char_sem; run;proc contents data=x6.nchar_sem; run;proc contents data=x6.byte_sem; run;proc contents data=x6.mixed_sem; run;See Also“ADJUST_NCHAR_COLUMN_LENGTHS= LIBNAME Option” on page 95“DBCLIENT_MAX_BYTES= LIBNAME Option” on page 119“DBSERVER_MAX_BYTES= LIBNAME Option” on page 136