Incorporating "%" in SAS variable

[VinnyR]

Hi,

I am trying to create a variable which will have value like "ABZ%ABZ". How can I create a variable which will contain this variable without the warning that Apparent invocation of macro ABZ nor resolved. Can somebody Guide?

Thanks,

Vinny 

[novinosrin]

%let var=%nrstr(ABZ%ABZ);

%put &=var;

%put &=var;
VAR=ABZ%ABZ

[VinnyR]

Thanks Novinosrin

[RW9]

The question would be why?  % is a macro trigger language, so its really not a good idea to put it in there, or you will just need to keep superquoting or wrapping it to make it work.  I can guarentee there are better methods to achieve whatever your outcome is.

[VinnyR]

Thanks for your replies. Please check the shell Extract that I am supposed to present the data in with the expected naming. DO you think it's unreasonable? and why?

[RW9]

No, there is nothing wrong with the shell, these kind of summary statistics are something quite generic.  However I have never put the statistic text in a macro variable.  Take a means output:

proc means...;
  ...
  output out=stats n=n mean=mean stddev=stddev...;
run;

data want (keep=col1 ord trt1);
  set stats;
  length col1 trt1 $50;
  ord=1;
  col1="N";
  trt1=strip(put(n,best.));
  output;
  ord=2;
  col1="Mean (SD)";
  trt1=strip(put(mean,8.3))||" ("||strip(put(stddev,8.4))||")";
  output;
...
run;

Shows one simple manual datastep where values are transposed out into their correct pieces (formatted as text to get %'s and other symbols in), with the stats column being put in.  You can simplify it a bit, and a lot of companies have macros to o these kind of things already.

[andreas_lds]

---

@VinnyR wrote:

Thanks for your replies. Please check the shell Extract that I am supposed to present the data in with the expected naming. DO you think it's unreasonable? and why?

---

Maybe it is to late, but why do you need that in a macro-variable? Please post more information, preferable not as attachments.

[VinnyR]

Sorry, that was a mistake, rectified!

[Kurt_Bremser]

To produce text output, use a data step.

In a data step, you can easily take precautions against unwanted resolution of macro triggers.

[VinnyR]

I did use data step

[Kurt_Bremser]

Then why do you store data in macro variables instead of a dataset or a text file?

---

@VinnyR wrote:
I did use data step

---

[VinnyR]

That was a mistake, I have edited the initial post

[Tom · Accepted solution]

Use single quotes instead of double quotes. The macro processor does not resolve macro triggers inside of single quotes.

data ....;
  ...
  myvar =  'ABZ%ABZ';
  ....
run;

[andreas_lds]

Just use single instead of double/normal quotes.

[VinnyR]

Thanks all for your contributions.

Regards,

Vinny