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

SAS/ACCESS Interface to Aster nCluster 4 Special Catalog Queries 445OptionSASDATEFMT=SCHEMA=Default ValuenoneLIBNAME option settingSQL Pass-Through Facility Specifics for Aster nClusterKey InformationFor general information about this feature, see “Overview of SQL ProcedureInteractions with SAS/ACCESS” on page 425. Aster nCluster examples are available.Here are the SQL pass-through facility specifics for the Aster nCluster interface.3 The dbms-name is ASTER.3 The CONNECT statement is required.3 PROC SQL supports multiple connections to Aster nCluster. If you use multiplesimultaneous connections, you must use the alias argument to identify thedifferent connections. If you do not specify an alias, the default ASTERalias is used.3 The CONNECT statement database-connection-arguments are identical to itsLIBNAME connection options.CONNECT Statement ExampleThis example uses the DBCON alias to connect to mynpssrv the Aster nClusterdatabase and execute a query. The connection alias is optional.PROC sql;connect to aster as dbcon(server=mynpssrv database=test user=myuser password=mypwd);select * from connection to dbcon(select * from customers WHERE customer like ’1%’);quit;Special Catalog QueriesSAS/ACCESS Interface to Aster nCluster supports the following special queries. Youcan use the queries to call the ODBC-style catalog function application programminginterfaces (APIs). Here is the general format of the special queries:Aster::SQLAPI’parameter–1’, ’parameter-n’Aster::is required to distinguish special queries from regular queries. Aster:: is not casesensitive.SQLAPIis the specific API that is being called. SQLAPI is not case sensitive.