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.

54 Generating Trace In<strong>for</strong>mation <strong>for</strong> Threaded Reads 4 Chapter 6steps that only read tables. Or, DBSLICEPARM=NONE turns it off entirely. You canspecify it as a data set option, a LIBNAME option, or a global <strong>SAS</strong> option.The first argument to DBSLICEPARM= is required and extends or restricts threadedreads. The second optional argument is not commonly used and limits the number ofDBMS connections. These examples demonstrate the different uses ofDBSLICEPARM=.3 UNIX or Windows <strong>SAS</strong> invocation option that turns on threaded reads <strong>for</strong> allread-only libref.--dbsliceparm ALL3 Global <strong>SAS</strong> option that turns off threaded reads.option dbsliceparm=NONE;3 LIBNAME option that restricts threaded reads to just <strong>SAS</strong> threaded applications.libname lib oracle user=scott password=tiger dbsliceparm=THREADED_APPS;3 Table option that turns on threaded reads, with a maximum of three connectionsin this example.proc print data=lib.dbtable(dbsliceparm=(ALL,3));where dbcol>1000;run;DBSLICE= and DBSLICEPARM= apply only to DBMS table reads. THREADS= andCPUCOUNT= are additional <strong>SAS</strong> options that apply to threaded applications. For morein<strong>for</strong>mation about these options, see the <strong>SAS</strong> Language <strong>Reference</strong>: Dictionary.Generating Trace In<strong>for</strong>mation <strong>for</strong> Threaded ReadsA threaded read is a complex feature. A <strong>SAS</strong> step can be eligible <strong>for</strong> a threaded read,but not have it applied. Per<strong>for</strong>mance effect is not always easy to predict. Use the<strong>SAS</strong>TRACE option to see whether threaded reads occurred and to help assessper<strong>for</strong>mance. These examples demonstrate usage scenarios with <strong>SAS</strong>/<strong>ACCESS</strong> toOracle. Keep in mind that trace output is in English only and changes from release torelease./*Turn on <strong>SAS</strong> tracing */options sastrace=’’,,t,’’ sastraceloc=saslog nostsuffix;/* Run a <strong>SAS</strong> job */data work.locemp;set trlib.MYEMPS(DBBSLICEPARM=(ALL,3));where STATE in (’GA’, ’SC’, ’NC’) and ISTENURE=0;run;The above job produces these trace messages:406 data work.locemp;407 set trlib.MYEMPS(DBSLICEPARM=(ALL, 3));408 where STATE in (’GA’, ’SC’, ’NC’) and ISTENURE=0;409 run;

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

Saved successfully!

Ooh no, something went wrong!