DATA Step, Macro, Functions and more

Project stop running

Accepted Solution Solved
Reply
Frequent Contributor
Frequent Contributor
Posts: 98
Accepted Solution

Project stop running

I have EG projct running, alwasy at the last few steps stop running. do nto know why.

 

Please see attach log file.

 

 


Accepted Solutions
Solution
‎09-06-2017 10:21 AM
Super User
Super User
Posts: 7,988

Re: Project stop running

It doesn't look like any of that code is running from what you posted, it is like there is an unbalanced quote and it is just writing it to the log as text, there is no Note: Procedure took xyz for instance.  Post your exact log, and make sure the debug options - 

options mlogic mprint symbolgen source source2;

 

Is on, so you can actually see what is going on.

View solution in original post


All Replies
Solution
‎09-06-2017 10:21 AM
Super User
Super User
Posts: 7,988

Re: Project stop running

It doesn't look like any of that code is running from what you posted, it is like there is an unbalanced quote and it is just writing it to the log as text, there is no Note: Procedure took xyz for instance.  Post your exact log, and make sure the debug options - 

options mlogic mprint symbolgen source source2;

 

Is on, so you can actually see what is going on.

Frequent Contributor
Frequent Contributor
Posts: 98

Re: Project stop running

Thank you
Regular Contributor
Posts: 191

Re: Project stop running

Looks more like the pgm-file :0

//Fredrik

Super Contributor
Posts: 345

Re: Project stop running

And post logs as text files, please.

Regular Contributor
Posts: 227

Re: Project stop running

add this statement

 

options mprint;

before you call any of your macros so we can see the macro statements.

 

... and save your logs as *.txt so they are easier to read

 

 

Super User
Posts: 11,343

Re: Project stop running

Posted in reply to Ron_Fehd_macro_maven

A common side effect of macro errors is a very hard to find unbalanced quote or parantheses such that a %mend is never found for a macro during compilation.

The symptom is code text in the log but no messages such as data set read, macro compilied and such. You may want to 1) save code

2) close the SAS session and restart, 3) run the code with the options mprint symbolgen mlogic. That may give you a better chance to find where some error lies.

☑ This topic is solved.

Need further help from the community? Please ask a new question.

Discussion stats
  • 6 replies
  • 139 views
  • 2 likes
  • 6 in conversation