08-16-2014 05:08 PM
Two similar warnings come out:WARNING: Apparent symbolic reference TYPE not resolved.
I think the first %put &type; should resolve to Train; the second %put &type; should resolve to Automobile.
Could anyone explain to me why I am totally wrong? Thank you guys.
08-16-2014 05:33 PM
Maybe this is what you are trying to do. But it doesn't seen to have a point.
08-16-2014 09:14 PM
It's all about scoping rules.
Macro variables are stored in symbol tables. There is a global symbol table (used for the whole SAS session), and a macro can create a local symbol table which exists while the macro is executing.
Your macro creates a local symbol table to hold the parameter (macro variable) TYPE. When CALL SYMPUT executes and writes the value TRAIN to a macro variable TYPE, it needs to decide whether to write it to the local macro variable that exists named TYPE, or to the global symbol table. The scoping rules CALL SYMPUT follows tell it to write the the macro variable TYPE in the local symbol table.
Your %PUT statements outside of the macro don't resolve, because they are looking for a macro variable named TYPE in the global symbol table. And there isn't one.
data_null_'s solution explicitly tells SYMPUTX to write the macro variable TYPE to the global symbol table, accomplishing your apparent purpose.