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 (February 2008, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 26 Feb 2008 11:22:04 -0500
Reply-To:     Nathaniel.Wooding@DOM.COM
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Nat Wooding <Nathaniel.Wooding@DOM.COM>
Subject:      Re: Need to constantly restart SAS
Comments: To: Anthony Pitruzzello <tonypit45@YAHOO.CA>
In-Reply-To:  <588064.71195.qm@web57010.mail.re3.yahoo.com>
Content-Type: text/plain; charset="US-ASCII"

Anthony

You say that the code appears in the log with no comment which I interpret as meaning that you see no notes at the end of each step boundary. A couple of good possibilities are that 1) you have never ended a macro definition and 2) never closed a /* */ comment.

If you are submitting your code by first highlighting a chunk and then submitting and perhaps not highlighting a %mend or a */, it is really easy to cause problems like the ones above.

Nat Wooding Environmental Specialist III Dominion, Environmental Biology 4111 Castlewood Rd Richmond, VA 23234 Phone:804-271-5313, Fax: 804-271-2977

Anthony Pitruzzello <tonypit45@YAHOO. To CA> SAS-L@LISTSERV.UGA.EDU Sent by: "SAS(r) cc Discussion" <SAS-L@LISTSERV.U Subject GA.EDU> Need to constantly restart SAS

02/26/2008 11:06 AM

Please respond to Anthony Pitruzzello <tonypit45@YAHOO. CA>

I recently transitioned form mainframe to PC SAS9. I notice that sometimes, seemingly at random periods, if I run a SAS program with an error in it, I correct the error, rerun the program, but the program doesn't appear to actually run. The log records an exact copy of the program without any comment at all. I have to shut down the application, restart it, then the program will run. I have no idea why this happens some days but not others.

I notice this happens only if the program fails to run properly the first time, which leads me to think this may be a clever way that SAS periodically punishes programmers for sloppy work (which I am sometimes guilty of) in an effort to raise the general programming level. My other theory is that it has something to do with the Earth's magnetic field. However, I'm hoping someone may have a more actionable explanation.

--------------------------------- Ask a question on any topic and get answers from real people. Go to Yahoo! Answers.

----------------------------------------- CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and/or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.


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