Hello- I'm clearly missing something simple here. Any idea why the following code will not change the value of the macro variable?
%SYMDEL MACRO1;
DATA _NULL_;
%GLOBAL MACRO1;
%LET MACRO1 = 0;
%PUT MACRO1 IS NOW &MACRO1.;
CALL SYMPUTX('MACRO1',1, 'G');
%PUT MACRO1 IS NOW &MACRO1.;
RUN;
In your example there is no need to use a DATA step or call symputx. The main use of call symputx is to write a DATA step variable to a macro variable.
%GLOBAL MACRO1;
%LET MACRO1 = 0;
%PUT MACRO1 IS NOW &MACRO1.;
%LET MACRO1 = 1;
%PUT MACRO1 IS NOW &MACRO1.;
If you want to use call symputx then the value of macro1 will only change after the DATA step boundary as it is an executable DATA step statement.
DATA _NULL_;
%GLOBAL MACRO1;
%LET MACRO1 = 0;
%PUT MACRO1 IS NOW &MACRO1.;
CALL SYMPUTX('MACRO1',1, 'G');
RUN;
%PUT MACRO1 IS NOW &MACRO1.;
In your example there is no need to use a DATA step or call symputx. The main use of call symputx is to write a DATA step variable to a macro variable.
%GLOBAL MACRO1;
%LET MACRO1 = 0;
%PUT MACRO1 IS NOW &MACRO1.;
%LET MACRO1 = 1;
%PUT MACRO1 IS NOW &MACRO1.;
If you want to use call symputx then the value of macro1 will only change after the DATA step boundary as it is an executable DATA step statement.
DATA _NULL_;
%GLOBAL MACRO1;
%LET MACRO1 = 0;
%PUT MACRO1 IS NOW &MACRO1.;
CALL SYMPUTX('MACRO1',1, 'G');
RUN;
%PUT MACRO1 IS NOW &MACRO1.;
Thank you!
April 27 – 30 | Gaylord Texan | Grapevine, Texas
Walk in ready to learn. Walk out ready to deliver. This is the data and AI conference you can't afford to miss.
Register now and lock in 2025 pricing—just $495!
Still thinking about your presentation idea? The submission deadline has been extended to Friday, Nov. 14, at 11:59 p.m. ET.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.