My question here is very simple. When you compile a macro, you would see the macro in default log window, but you will not see it in the external log file you created using proc printto unless you call it or execute another data or proc step. Why??
... View more
Okay, lets say i am creating a permanent file instaed of temp file. Then also i do not see the compiled statements as i woould see in the standard log location (Log window). Should i use printto again to redirect?? Why is this behaviour??
... View more
That is may be you have few statements after macro compilation. Will only the below code gives you anything in the log??
filename log1 temp; proc printto log=log1 new ; run; %macro mymac; %put &sysmacroname; %mend mymac;
... View more
Hi All,
I was trying to save my logs using proc printto and noticed that all the macros that i compile are not coming into the log unless i call them or i run some procedures after compiling a macro. I do not understand why i do not get the compiled macro statement into the permanent file as it comes in standard LOG location. Can somebody please help me understanding this.
For Example:-
proc printto log="abc.txt"; run;
%macro abc; %put anbc; %mend;
If i use the DM statement, i get all log contents for the session. Which one is better to use??
dm 'log; file "abc.txt"';
... View more
Macro language only has character datatype. There is no numeric datatype in Macro language. Hence quotations are not needed. If the value has quotes then you have to compare using the quotes else you dont need the quotes.
... View more
%let YYYYMMDD="11MAY2015"d; data need; if &YYYYMMDD=intnx("month",today(),0,"e") then need=input(put(intnx("month",&YYYYMMDD,1,"b"),yymmddn8.),8.); run; proc print; run;
... View more
I understood why the program was runnnig in my session. I had a numeric as well as character format with the same name. Instead of applying character format, SAS was applying numeric format i guess.
... View more
