LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (July 2010, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 16 Jul 2010 18:12:51 +0000
Reply-To:     toby dunn <tobydunn@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         toby dunn <tobydunn@HOTMAIL.COM>
Subject:      Re: Why you should always use a RUN statement  (A SAS Gotcha)
Comments: To: peterflomconsulting@mindspring.com
In-Reply-To:  <00fa01cb250f$b3c8ce90$1b5a6bb0$@com>
Content-Type: text/plain; charset="iso-8859-1"

Peter,

Headers should ALWAYS.... be at the very top of a program, the only exception is in my production code, to which I have placed my code to redirect my log and output to a different locations. The reason I did this is so I would explicitly have my header in the log files.

Toby Dunn

"Don't bail. The best gold is at the bottom of barrels of crap." Randy Pausch "Be prepared. Luck is where preparation meets opportunity." Randy Pausch

> Date: Fri, 16 Jul 2010 13:52:47 -0400 > From: peterflomconsulting@MINDSPRING.COM > Subject: Re: Why you should always use a RUN statement (A SAS Gotcha) > To: SAS-L@LISTSERV.UGA.EDU > > Jack Hamilton wrote > <<< > I disagree. I put titles before the item they print for, as a form of > documentation. And I would not omit the RUN under any circumstances. In > addition to making titles work better, RUN makes the SAS log appear in the > right place, and omitting it my cause problems with ODS output. > >>> > > -- > > I also tend to use titles as part of documentation - and it's part that my > colleagues can see, which, if anything, makes it even MORE important that it > is correctly placed. This also lets me divide documentation into public and > private. Since I have had very few colleagues who actually wanted to see > the SAS Code that I wrote, my comments are essentially private. > > I do use the RUN statements as a rule. As proof, I can say that I've been > using SAS for 20 years or so, and this is the first time I got bit by this > particular problem. > > But that lets me raise another question. I often see it recommended to use > a header statement that includes a note as to the location of the program. > But, unless you print your programs, how is this useful? If you've got the > program open, you must have found it somewhere, right? Or is this mostly > useful for people who share code? > > > Peter _________________________________________________________________ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5


Back to: Top of message | Previous page | Main SAS-L page