13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The LIBNAME Statement <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 LOCKTABLE= LIBNAME Option 155LOCATION= LIBNAME OptionAllows further qualification of exactly where a table resides.Alias: LOC=Default value: noneValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: DB2 under z/OSSyntaxLOCATION=locationDetailsThe location name maps to the location in the SYSIBM.LOCATION catalog in thecommunication database.In <strong>SAS</strong>/<strong>ACCESS</strong> Interface to DB2 under z/OS, the location is converted to the firstlevel of a three-level table name: location.authid.table. The DB2 Distributed DataFacility (DDF) makes the connection implicitly to the remote DB2 subsystem when DB2receives a three-level name in an SQL statement.If you omit this option, <strong>SAS</strong> accesses the data from the local DB2 database unlessyou have specified a value <strong>for</strong> the SERVER= option. This option is not validated untilyou access a DB2 table.If you specify LOCATION=, you must also specify the AUTHID= LIBNAME option.See AlsoTo apply this option to an individual data set, see the “LOCATION= Data Set Option”on page 333.For in<strong>for</strong>mation about accessing a database server on Linux, UNIX, or Windowsusing a libref, see the “REMOTE_DBTYPE= LIBNAME Option” on page 178.“AUTHID= LIBNAME Option” on page 96LOCKTABLE= LIBNAME OptionPlaces exclusive or shared locks on tables.Default value: no lockingValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: In<strong>for</strong>mixSyntaxLOCKTABLE=EXCLUSIVE | SHARE

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!