Hi @dtravassos
SAS/ACCESS Interface to JDBC is, indeed, a new product!
The following messages indicate that SAS/ACCESS Interface to JDBC is either not installed, or installed incorrectly.
ERROR: The JDBC engine cannot be found.
ERROR: Error in the LIBNAME statement.
Sometimes admins try to install only the SAS/ACCESS engine on an old SAS Foundation install. In the case of a new product, such as SAS/ACCESS Interface to JDBC, it will not work on an older SAS release. The error messages will likely be different than those mentioned above.
Just for fun, here are a couple of examples of JDBC LIBNAME statements.
Up first, AWS Athena
/* The options can span line if the new line starts in column 1 and */
/* there is no space after the ; at the end of the line. */
libname athena jdbc driver="com.simba.athena.jdbc.Driver"
classpath="C:\lib"
URL="jdbc:awsathena://athena.us-east-1.amazonaws.com:443;
s3_staging_dir=s3://bogus-athena/staging/;
S3OutputLocation=s3://bogus-athena/results/;
AwsCredentialsProviderClass=com.simba.athena.amazonaws.auth.profile.ProfileCredentialsProvider;
AwsCredentialsProviderArguments=617292774228-sandbox" DATABASE=jeffdb;
Next, Teradata.
libname tera jdbc classpath="/opt/jdbcdrivers"
class="com.teradata.jdbc.TeraDriver"
user="myuser" password="BogusPW1"
schema=myuser
URL="jdbc:teradata://tdserv.somecompany.com"
PRESERVE_NAMES=YES;
if you get something wrong while connecting, you will see the infamous Java error message dump.
Best wishes,
Jeff
