About martha_sas

bpowell · ‎07-14-2021

Something about proc export, which uses ODS under the hood (so I understand) writes to the log in such a way that it bypasses whatever it was in the log break routine that has failed when killing code. Again, this only happens in some cases - sometime if you kill code it dies gracefully and the log is unimpacted. When it does stop updating, there is something about interupting the call to ODS in an export statement that manages to restart the log write.

SASKiwi · ‎03-15-2019

I'm guessing but it is probably something like this: %include "C:\Users\jaiga\Desktop\SAS_Test_Practise\Macro\Macro1.sas" You can get the correct path by navigating to the folder in Windows Explorer then copying and pasting from the navigation bar at the top.

rmoreno · ‎05-31-2016

Maybe Scott refered to something like this, which I usually use for adapting dates to Excel format and somehow prefer as more beautiful: DATA WPolSummary0 (DROP=state_old); length state $5.; SET rateBusPack rateISR rateBW (RENAME=(state=state_old)) rateCAR ; state=state_old; RUN; Cheers! (Is this actually used as a "goodbye"? Best wishes or best regards maybe sounds like "too much" here ^^)

martha_sas · ‎02-25-2009

Real time is actual clock time it took to execute the proc print. It can change depending on system capacity and current load. CPU time is the processing time the CPU used to execute the procedure. It's not supposed to depend on load factors. That 4 observation data step is so short that it required less than 1/100 of a second in CPU time for the print procedure, so the CPU time is showing up as 0:00. Does this answer your question?