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

SAS/ACCESS Interface to Aster nCluster 4 Data Set Options for Aster nCluster 443OptionUSE_ODBC_CL=UTILCONN_TRANSIENT=Default ValueNONOAster nCluster LIBNAME Statement ExamplesIn this example, SERVER=, DATABASE=, USER=, and PASSWORD= are theconnection options.LIBNAME mydblib ASTER SERVER=npssrv1 DATABASE=testUSER=netusr1 PASSWORD=netpwd1;PROC Print DATA=mydblib.customers;WHERE state=’CA’;run;In this next example, the DSN= option, the USER= option, and the PASSWORD=option are connection options. The Aster nCluster data source is configured in theODBC Administrator Control Panel on Windows platforms. It is also configured in theodbc.ini file or a similarly named configuration file on UNIX platforms.LIBNAME mydblib aster dsn=nCluster user=netusr1 password=netpwd1;PROC Print DATA=mydblib.customers;WHERE state=’CA’;run;Here is how you can use the NOPROMPT= option.libname x aster NOPROMPT="dsn=aster;";libname x aster NOPROMPT="DRIVER=nCluster; server=192.168.28.100;uid=username; pwd=password; database=asterdb";This example uses the PROMPT= option. Blanks are also passed down as part of theconnection options. So the specified value must immediately follow the semicolon.libname x aster PROMPT="DRIVER=nCluster;";The REQUIRED= option is used in this example. If you enter all needed connectionoptions, REQUIRED= does not prompt you for any input.libname x aster REQUIRED="DRIVER=nCluster; server=192.168.28.100;uid=username;pwd=password; database=asterdb ;";This error results because the database was specified as asterdb, which contains atrailing blank, instead of asterdb.ERROR: CLI error trying to establish connection:ERROR: Database asterdb does not exist.Data Set Options for Aster nClusterAll SAS/ACCESS data set options in this table are supported for Aster nCluster.Default values are provided where applicable. For details about this feature, see the“Overview” on page 207.