Thanks for walking it through with examples - it's really helpful. The final example does as I had intended. So that's two solutions now 🙂 ... View more

Thanks for your response. I can see the difference in the log when I use %nrbquote and %nrstr - however there is still an issue when I use %nrstr. I was focussed (probably wrongly) on the hidden triggers in string2 (which I was expecting to be revealed during execution) rather than the more obvious %maxl trigger that would be detected during compilation! As you can see below in the log, SAS is still trying to resolve the hidden triggers contained in the string2 variable when I use %nrstr - any ideas how to stop this happening? 1 + %maxl(dsn=DS1 , MLOGIC(MAXL): Beginning execution. 2 + lib1=SD2 , 3 + lib2=SD3 , 4 + pdbf=Y , lib1f=Y , setstr="set &lib1..&dsn &lib2..&dsn;" , WARNING: Apparent symbolic reference DSN not resolved. WARNING: Apparent symbolic reference LIB1 not resolved. WARNING: Apparent symbolic reference DSN not resolved. WARNING: Apparent symbolic reference LIB2 not resolved. WARNING: Apparent symbolic reference DSN not resolved. 5 + lib2f=Y ); MLOGIC(MAXL): Parameter DSN has value DS1 MLOGIC(MAXL): Parameter LIB1 has value SD2 MLOGIC(MAXL): Parameter LIB2 has value SD3 MLOGIC(MAXL): Parameter PDBF has value Y MLOGIC(MAXL): Parameter LIB1F has value Y MLOGIC(MAXL): Parameter SETSTR has value "set &lib1..&dsn &lib2..&dsn;" MLOGIC(MAXL): Parameter LIB2F has value Y ... View more

Thanks but the problem is the dataset variable string2 does contain macro variable triggers and these are not being masked. When you say, just wrap it around the macro name (or even just the % itself), I'm not sure what you mean? ... View more

You were right - I already had what I needed! I was complicating matters. I'm not sure it was possible to mask the triggers the way the string was.   Thanks for taking the time to look at it 🙂 ... View more

Thanks but the problem is the dataset variable string2 does contain macro variable triggers and these are not being masked. When you say,  just wrap it around the macro name (or even just the % itself), I'm not sure what you mean? ... View more

Thanks for your response.   I can see the difference in the log when I use %nrbquote and %nrstr - however there is still an issue when I use %nrstr. I was focussed (probably wrongly) on the hidden triggers in string2 (which I was expecting to be revealed during execution) rather than the more obvious %maxl trigger that would be detected during compilation! As you can see below in the log, SAS is still trying to resolve the hidden triggers contained in the string2 variable when I use %nrstr - any ideas how to stop this happening?     1      + %maxl(dsn=DS1                                                                    , MLOGIC(MAXL):  Beginning execution. 2      +          lib1=SD2                                                                        , 3      +          lib2=SD3                                                                            , 4      +                  pdbf=Y       ,                                                     lib1f=Y       ,          setstr="set &lib1..&dsn &lib2..&dsn;"  , WARNING: Apparent symbolic reference DSN not resolved. WARNING: Apparent symbolic reference LIB1 not resolved. WARNING: Apparent symbolic reference DSN not resolved. WARNING: Apparent symbolic reference LIB2 not resolved. WARNING: Apparent symbolic reference DSN not resolved. 5      +    lib2f=Y       ); MLOGIC(MAXL):  Parameter DSN has value DS1 MLOGIC(MAXL):  Parameter LIB1 has value SD2 MLOGIC(MAXL):  Parameter LIB2 has value SD3 MLOGIC(MAXL):  Parameter PDBF has value Y MLOGIC(MAXL):  Parameter LIB1F has value Y MLOGIC(MAXL):  Parameter SETSTR has value "set  &lib1..&dsn &lib2..&dsn;" MLOGIC(MAXL):  Parameter LIB2F has value Y ... View more

I did try it although I didn't really expect it to work as my understanding is it masks the macro triggers at compilation. ... View more