Not sure what you're asking here....??? ... View more

Automatic macro variables are created by the macro processor when you invoke SAS. All of them are global except for SYSPBUFF which is local. But, you won't see it listed with a "%put _local_" because that only lists user-generated local macro variables. Of the automatic macro variables that can be assigned values, they still remain global no matter where you assign the new value... ... View more

There aren't -- to the best of my knowledge -- any O'Reilly books (including a "cookbook") on SAS. But the other books listed above are all good ones. ... View more

Yeah, don't use the double quotes. With the double quotes around it, the %let stores them (along with the good stuff inside) in the symbol table... 15 %let dir = "C:\"; 16 %put &dir; "C:\" ... View more

Works for me, too. Scott is probably right. Try it again in a new SAS session. ... View more

I guess you need to write some sort of a %DO %UNTIL loop for this? ... View more

What version of SAS are you running? ... View more

Do you typically see errors every time you run your program or are you just trying to debug it? ... View more

You could just turn off all the notes with the 'nonotes' option... ... View more

I'm not sure I get what your problem / question is.... ... View more

This works correctly at SAS 9.3 (which is about to be released -- keep sitting there). As for the problem at 9.2 - this appears to be an issue with Proc Genmod. The SAS Macro Facility merely fetches the value for &syserr from the rest of the SAS System, where it's supposed to be set correctly by the data steps / procs. ... View more

When I run his code, the %put statement works because he's passing in the values for &var1 and &var2 as arguments to the macro, so use of the call symput is irrelevent w.r.t. the macro. That being said, any other attempts to %put the values of &var1 and &var2 in open code won't work. It's a timing thing. The call symput does its thing during execute time, but all of the macro statements in open code are evaluated during compile time. ... View more

My guess is that this is a "timing" thing. The warning is likely coming during the compilation of the %check_n macro which occurs before execution time (when your PROC SQL runs). ... View more

FYI you can find lots of info on SAS dates / times here: http://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a002200738.htm ... View more