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

Overview of In-Database Procedures 4 Miscellaneous Items 71Databases” on page 87, “LIBNAME Statement Data Conversions” on page 841, and“DBFMTIGNORE= System Option” on page 404.LIBNAME Statement3 These LIBNAME statement options and settings prevent in-database processing:3 DBMSTEMP=YES3 DBCONINIT3 DBCONTERM3 DBGEN_NAME=SAS3 PRESERVE_COL_NAMES=NO3 PRESERVE_TAB_NAMES=NO3 PRESERVE_NAMES=NO3 MODE=TERADATA3 LIBNAME concatenation prevents in-database processing.Data Set-related OptionsThese data set options and settings prevent in-database processing:3 RENAME= on a data set.3 OUT= data set on DBMS and DATA= data set not on DBMS.For example, you can have data=td.foo and out=work.fooout where WORK is theBase SAS engine.3 DATA= and OUT= data sets are the same DBMS table.3 OBS= and FIRSTOBS= on DATA= data set.Miscellaneous ItemsThese items prevent in-database processing:3 DBMSs do not support SAS passwords.3 SAS encryption requires passwords which are not supported.3 Teradata does not support generation options that are explicitly specified in theprocedure step, and the procedure does not know whether a generation number isexplicit or implicit.3 When the database resolves function references. the database searches in thisorder:1 fully qualified object name2 current database3 SYSLIBIf you need to reference functions that are published in a nonsystem, nondefaultdatabase, you must use one of these methods:3 explicit SQL3 DATABASE= LIBNAME option3 map the fully qualified name (schema.sas_put) in the external mapping