Hi,
This problem is confusing. I suspect it relates to the message about unbalanced quotes. Using Enterprise Guide, this can actually be tricky to detect, because:
- You can't batch submit a program (this is generally the best way to ensure that you start with a fresh SAS session and get a full log).
- To get a fresh SAS session you need to either quit and restart EG or disconnect from the server and reconnect.
- EG adds a magic string after each code submission, which attempts to close out any unmatched quotes. But this means that sometimes if your code has unmatched quotes the log won't tell you of the problem, because EG added code to close the quotes.
Debugging is helpful to do in small bits. Here's a simple test of your macro code:
%macro gick();
%let last= eat travel;
%do l = 1 %to 2;
%if &l. = 1 %then /*The problem is in this line. It does not recognize &l. as a numeric value*/
%do;
%put I ran ;
%end;
%end ;
%mend gick ;
%gick()
The only code that writes a value to the macro variable L is your %do loop. Testing the above code (in a fresh SAS session) shows that there is no problem with the %DO loop or the %IF statement.
This suggests that the problem is elsewhere in your code. Either unmatched quotes, or an unclosed %macro statement, or ...
I would start a new EG session, open your program, and hit submit. Then go to the top of the log, and start reviewing, looking for errors, warnings, and bad notes.
Also, I just noticed that your log has the line:
options notes nospool;
which suggests that at some point earlier in the program, you set option nonotes. I would recommend you remove that. Meaning, make sure the NOTES option is on for the full session. It's very hard to debug without notes in the log.
BASUG is hosting
free webinars Next up:
Don Henderson presenting on using hash functions (not hash tables!) to segment data on June 12. Register now at the Boston Area SAS Users Group event page:
https://www.basug.org/events.
Click image to register for webinar
