Date:         Tue, 8 Oct 1996 10:49:03 -0400
Reply-To:     Robb <robb@MACROINT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Robb <robb@MACROINT.COM>
Subject:      Wonky SAS Problem solved
Comments: To: herr@macroint.com, wilder@macroint.com, mccormick@macroint.com,
          gilhooly@macroint.com

  On friday, as some of you may know, I having problems with SAS running
  the wrong code.  I had made some edits in the source file, and the log
  file showed the pre-edit verson running.  I checked the .bak file, and it
  was not being run.  Our best guess was that somehow caching got screwed
  up and SAS was running a cached copy of the unmodified code.
 
  However, it turned out to be simpler, and sillier that that.  I had
  inadvertantly created a version of the code in a file with NO extension.
  SAS was running this code, as I was not specifiying an extension on the
  command line.
 
  The rule sas uses is to check for the file specified on the command
  line, and if that does not exist, take the filename with the .sas
  extension as the default. So typing "SAS file-o-code" will execute sas
  with "file-o-code."  over "file-o-code.sas".
 
  Live and Learn,
  Will