Maybe you could do something like this: %do i=1 %to 5; /*or however many categories there are */ %if &i=1 %then %do; %let catg = 'BEVERAGES'; %let catgdesc = "Beverages"; %end; %else %if &i=2 %then %do; %let catg = 'FOODS'; %let catgdesc = "Foods"; %end; /* etc etc until you have blocks for all categories */ /* Then after the if / else if / else block, put all of your other code here */ %end; ... View more

This won't help you now, but when 9.3 comes out, it will have a %SYSMSTORECLEAR statement that will close the current library and clear the libref. ... View more

You can find out more about using SAS dates here. I hope this helps. http://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a002200738.htm ... View more

Here's an excerpt from the doc. Hope this helps. The %SYSRPUT statement is submitted with SAS/CONNECT to a remote host to retrieve the value of a macro variable stored on the remote host. %SYSRPUT assigns that value to a macro variable on the local host. %SYSRPUT is similar to the %LET macro statement because it assigns a value to a macro variable. However, %SYSRPUT assigns a value to a variable on the local host, not on the remote host where the statement is processed. The %SYSRPUT statement places the macro variable into the global symbol table in the client session. ... View more

An aside: Mike's second example doesn't look like it should work, e.g. one wouldn't expect the SAS Macro Facility to resolve the &path variable inside of the single quotes. But since these lie within double quotes, the macro facility sees the single quotes as plain-old characters and not single quotes and DOES resolve the &path variable within. html = "href='&path./summary_bu.htm'"; put 'HTML: ' html; (snip snip) HTML: href='http://domapp.com/Applications/AS/CZ/03de670ff5/$FILE/summary_bu.htm' ... View more

Can we see what's in your lib077.mac file? Then I'll bet we can figure this one out. ... View more

I haven't been to the forum lately. Is this still an issue for you? When you say "call the macro with %include" it's not clear if you mean that you're including the macro definition up front, then trying to execute it later in the program; or if you actually have the call to the macro in the code you're including. Scott is right. If we can see your code we can probably help with this. If you aren't comfortable posting it here to a public forum, call SAS Technical Support and have them take a look. --Pat ... View more

My guess is that it doesn't like the semicolons in your proc statement. Try using the quoting functions. ... View more

Oops, that link above only works internally. Try this one... http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/z3514quote.htm ... View more

http://swwafs.unx.sas.com/dept/pub/doc/902/gpp/prods/mcrolref/win/mcrolref.hlp/z3514quote.htm The %quote function only masks single quotes when they occur in pairs, UNLESS you proceed one with a %. ... View more

http://support.sas.com/publishing/certguides.html The SAS Macro Facility is covered on the Base SAS certification exams. The certification prep books are very helpful...! ... View more

Exactly. And there are some good examples of how it works in the doc link that Scott posted, above. ... View more

MRECALL is mostly intended as a debugging tool (that's why NOMRECALL is the default) but it can be helpful in figuring out this sort of problem...! ... View more

I believe that if you call Tech Support and explain what you need, they can submit an enhancement request for you and route it to the proper group(s) for consideration. ... View more

Make sure you have the mautosource option set (it should be by default unless it was previously turned off during your SAS session). options mautosource; If your macros are compiled stored macros you also need the mstored option. Then, as was previously mentioned, make sure your sasautos= option is correct. You can either set this to a previously defined fileref or you can use a system path but the system path must be in quotes. Each macro needs to be stored in a separate file with a name that matches the macro name, e.g. impute.sas --Pat ... View more