Date:         Wed, 19 Oct 2005 04:03:45 -0400
Reply-To:     Tom Hide <tom.hide@DEHIWORLD.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Tom Hide <tom.hide@DEHIWORLD.COM>
Subject:      Re: SAS session gets stuck sometimes

On Tue, 18 Oct 2005 09:57:13 -0400, Ram <rv8k@VIRGINIA.EDU> wrote:

>Hi
>
>I am a beginner in SAS. Once in a while, when I do something real
>stupid, SAS gets irretrievably stuck. Anything I punch in after that
>just appears as text in the log. For example, this error came up one time--
>
>ERROR: Macro keyword MEND appears as text.  A semicolon or other
>delimiter may be missing.
>
>Is there anything I can do to get out of this mode and back to testing
>my code, other than having to close/open SAS session itself. I tried to
>look for kill process/job, but found nothing.
>thanks,
>Ram

I sometimes get this problem, be it in open code or in macros.
I try some of the methods already suggested.

If all else fails, save and close the SAS session and restart.
If you have a persistent problem, then ensure you save your code prior to
submission. Easy said but easier to forget.

It is so easy to forget to omit a quote somewhere, in open code, or a % in
macro code.

Re macro code, it's best to use "Options mlogic mprint symbolgen" whilst
testing, if you are not already doing so.

As they say, you learn by your mistakes.

Best of luck with you macro coding!