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.

Macro Variables and System Options <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 <strong>SAS</strong>TRACELOC= System Option 419Output 12.8<strong>SAS</strong> Log Output from the <strong>SAS</strong>TRACE= ’,,t,’ System Option165 options sastrace=’,,t,’ sastraceloc=saslog nostsuffix;166 data mydblib.snow_birthdays(DBTYPE=(empid=’number(10)’));167 set work.winter_birthdays;168 run;NOTE: <strong>SAS</strong> variable labels, <strong>for</strong>mats, and lengths are not written to DBMS tables.NOTE: There were 3 observations read from the data set WORK.WINTER_BIRTHDAYS.NOTE: The data set MYDBLIB.SNOW_BIRTHDAYS has 3 observations and 3 variables.NOTE: DATA statement used (Total process time):real time0.21 secondscpu time0.06 seconds169 proc print data=mydblib.snow_birthdays(dbsliceparm=(all,3));170 run;ORACLE: DBSLICEPARM option set and 3 threads were requestedORACLE: No application input on number of threads.ORACLE: Thread 1 contains 1 obs.ORACLE: Thread 2 contains 0 obs.ORACLE: Thread 3 contains 2 obs.ORACLE: Threaded read enabled. Number of threads created: 3NOTE: There were 3 observations read from the data set MYDBLIB.SNOW_BaaaaaAYS.NOTE: PROCEDURE PRINT used (Total process time):real time1.12 secondscpu time0.17 secondsFor more in<strong>for</strong>mation about tracing threaded reads, see “Generating TraceIn<strong>for</strong>mation <strong>for</strong> Threaded Reads” on page 54.Note: You can also use <strong>SAS</strong>TRACE= options with each other. For example,<strong>SAS</strong>TRACE=’,,d,d’. 4<strong>SAS</strong>TRACELOC= System OptionPrints <strong>SAS</strong>TRACE in<strong>for</strong>mation to a specified location.Default value: stdoutValid in: configuration file, <strong>SAS</strong> invocation, OPTIONS statementDBMS support: DB2 UNIX/PC, HP Neoview, In<strong>for</strong>mix, Microsoft SQL Server, MySQL,Netezza, ODBC, OLE DB, Oracle, Sybase, TeradataSyntax<strong>SAS</strong>TRACELOC=stdout | <strong>SAS</strong>LOG | FILE ’path-and-filename’Details<strong>SAS</strong>TRACELOC= lets you specify where to put the trace messages that <strong>SAS</strong>TRACE=generates. By default, output goes to the default output location <strong>for</strong> your operatingenvironment. Specify <strong>SAS</strong>TRACELOC=<strong>SAS</strong>LOG to send output to a <strong>SAS</strong> log.This option and its values might differ <strong>for</strong> each host.

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

Saved successfully!

Ooh no, something went wrong!