Desktop productivity for business analysts and programmers

Behavior change from EG4.1 to EG 4.2

Reply
Occasional Contributor
Posts: 14

Behavior change from EG4.1 to EG 4.2

Hi all,
We've noticed a difference between how EG 4.1 and EG 4.2 generate (or store) session parameters.

EG 4.1 generates this output:

%put &_CLIENTUSERNAME &_CLIENTMACHINE;
nick.welke D03CB4


And EG 4.2 generates this:

%put &_CLIENTUSERNAME &_CLIENTMACHINE;
'nick.welke' 'D03CB4'


Does anyone else get this same result? Is it something we can disable in 4.2 to remove the quotes?

TIA
Nick
Contributor
Posts: 55

Re: Behavior change from EG4.1 to EG 4.2

I have noticed the same thing. I had some date macro variables in the titles of my reports that no longer display. I have not spent much time finding a solution, so if anyone has one it would be greatly appreciated!
SAS Employee
Posts: 149

Re: Behavior change from EG4.1 to EG 4.2

Suggestion from SAS Tech Support is:

%sysfunc(compress(&_clientusername,%str(%')))

Nick, you probably received the same message from Tech Support, but I figured I'd post it here for others to look at, Not sure if the EG developers will offer a less programatic workaround in the future.
Respected Advisor
Posts: 4,130

Re: Behavior change from EG4.1 to EG 4.2

Why not using dequote() instead?

%let _CLIENTUSERNAME='nick.welke';
%put %sysfunc(dequote(&_CLIENTUSERNAME));
Super Contributor
Posts: 356

Re: Behavior change from EG4.1 to EG 4.2

One would have to ask why the change? you would think code run in previous versions would be able to run with the same results/output successfully in current versions.

Barry Message was edited by: twocanbazza
Contributor
Posts: 71

Re: Behavior change from EG4.1 to EG 4.2

I dare say that someone complained about problems with unquoted strings. I wonder if the majority of EG users were happy with the old approach.
Ask a Question
Discussion stats
  • 5 replies
  • 404 views
  • 0 likes
  • 6 in conversation