In this first example,
SERVER=, DATABASE=, USER=, and PASSWORD= are the connection options.
LIBNAME mydblib ASTER SERVER=npssrv1 DATABASE=test
USER=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 the ODBC Administrator Control Panel
on Windows platforms. It is also configured in the odbc.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 the connection
options. Therefore, 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 connection options,
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 ;";
As shown above, when
asterdb (contains
a trailing blank) is specified as the database instead of
asterdb (no
trailing blank), this error results:
ERROR: CLI error trying to establish connection:
ERROR: Database asterdb does not exist.