comp.soft-sys.sas - The SAS statistics package.
Is it a particular query or application that is running slow? More details might help to isolate where the potential bottleneck is. Rgds
To comp.soft-sys.sas -- I'm using ODS RTF to write SAS/GRAPH results to an RTF file. The date- time stamp that gets written in the header of the RTF file is: 05:33 Wednesday, April 09, 2008 The only problem is, that the time is really 5:33 PM -- so it should say either "5:33 PM" or (preferably) "17:33". Does anyone know how to fix this? Thanks much! --Tom
Peter , I fear you have missd the lesson here, you should have looked at your log. Rule of thumb, never ever ever ever ever ....... to infinity..... ever.... let a program go out with errors. If there is an error always and I mean always fix it. Toby Dunn From: Peter Constantinidis < XXXX@XXXXX.COM > Reply-To: Peter Constantinidis < XXXX@XXXXX.COM > To: XXXX@XXXXX.COM Subject: Fwd: Watch out for SAS keeping old data in memory while running Date: Tue, 6 Jun 2006 22:34:24 -0400 Sigh. I made a test program so I could demonstrate to interested parties but alas, the problem in this case really was a combination of my fault, and misleading behavior (my opinion) on the part of SAS. Here is what's happened, my comments in brackets: (beginning, 3 sets are made, and run, with no errors. now for output portion, a set has been deleted on purpose.) 32 data report; 33 set perm.set1 perm.set2 perm.set3; ERROR: File PERM.SET2.DATA does not exist. (so far so good, it recognizes that set1 and set3 exist, but set2 has been removed.) 34 ods html body='c:\test.htm' ; NOTE: Writing HTML Body file: c:\test.htm NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set WORK.REPORT may be incomplete. When this step was stopped there were 0 observations and 2 variables. WARNING: Data set WORK.REPORT was not replaced because this step was stopped. (here it is saying that work.report was not replaced with updated data because a missing set in a set statement is enough to stop the step, it does not skip over like I expected). 35 proc print data=report noobs label split='/'; 36 var name bananas; 37 run; NOTE: There were 9 observations read from the data set WORK.REPORT. NOTE: PROCEDURE PRINT used (Total process time): real time 0.06 seconds cpu time 0.01 seconds 38 ods html close; (misleading newbie trap! even though the previous step was STOPPED, it still went ahead and printed what it had in memory. sas is doing what it was told to do, and work.report was never replaced but it was never deleted either.) And that is what happened and it is my fault. The moral here for students, is that you have to write a new data statement every time if you're going to have a different # of files, otherwise it'll use the old data it still has in memory. :( Well, I'll certainly never make that mistake again.