If you want to use %sysevalf, then use only nonmissing values within the first argument to the %SYSEVAL function.
As one work around make sure your macro variables is not equal to missing values like
%let a=%sysfunc(sum(.,0));
%let b=%sysfunc(sum(10,0));
%let c=%sysfunc(sum(20,0));
By that any missing values will be equal to zero.
... View more
It is just typo in your code decide is it "procedure_no" or "procudure_no"?
let them all be the same then you will not get the same issue
... View more
Easier you can use PROC FORMAT, like
proc format;
value $myFormat
'ND1'='ND,1'
'ND2'='ND,2'
'ND3'='ND,3'
'ND4'='ND,4'
'ND5'='ND,5'
'ND6'='ND,6';
run;
Then assign it to your variables
... View more
Because the INPUT statment will figure out variables length based on some observation automatically. If you want the LENGTH statment to have effect let it be before the INPUT statment.
As
data state1;
length name $5 status $50;
input name $ rank status $ ;
datalines;
mekelele 1 nohope
torres 1 depress
valdes 1 sotkaal
bhutia 1 fulltension
;
run;
If you checked your log you will figure out that easily by reading the WARNINGs you got
WARNING: Length of character variable name has already been set.
Use the LENGTH statement as the very first statement in the DATA STEP to declare the length of a character variable.
WARNING: Length of character variable status has already been set.
Use the LENGTH statement as the very first statement in the DATA STEP to declare the length of a character variable.
... View more
CALL SYMPUT AND EXECUTE
The CALL SYMPUT allows the data step to add a new macro variable or overwrite an existing one to the macro space. This action is not performed until the data step is completed its processing. So it is a common knowledge that the macro variable created by CALL SYMPUT cannot be referenced inside the creating data step and you have to use another step outside this data step if you want to check the value of this macro variable or to use it. But CALL EXECUTE gives you the flexibility to reference the macro variable inside the data step used to create it.
Read more thist in CALL SYMPUT Routine doc. here: Problem Trying to Reference a SYMPUT-Assigned Value Before It Is Available
So what will happen when you run your first example for the first time, you get warning like:
WARNING: Apparent symbolic reference MACVAR not resolved.
Then if you run your example again you will not get this warning again, as from your first run the data step is completed and all statements that are stacked for later execution are exected.
But if you used CALL EXECUTE this will not happen, because macro references within CALL EXECUTE are executed immediately.
Still we have limitations for that, but that in more complicated examples. Like here: Can I CALL EXECUTE here?
... View more
data want ;
set have;
by Stock year;
if last.year then output;
run;
That based on the fact that your data are sorted by stock year;
Or you should sort them first
As
proc sort data=have out=have_sorted;
by stock year;
run;
data want ;
set have_sorted;
by Stock year;
if last.year then output;
run;;
... View more
Are you aware of the syntax index that is located at support.sas.com/documentation/?
No
Do you use the syntax index?
No
Do you find it helpful?
....
Would it help you if we added the options for the procedure statements to the syntax index?
Yes ... I think.
... View more
Yes, as A contains duplicate records based on your key. So you will end up with uncomplete left joined data set. Only if you do specify the option multidata="Y". And by that the hash object keeps the multiple values in a list that is associated with the key. Which can be traversed and manipulated by using several methods such as HAS_NEXT or FIND_NEXT as in the first post.
... View more
As your lookup table B is not having duplicate, then this is easier
data test(drop=rc);
if 0 then set b;
declare hash hh_pat(dataset:"b");
rc=hh_pat.defineKey("key");
rc=hh_pat.defineData("d4", "d5", "d6","other");
rc=hh_pat.defineDone();
do until(eof);
set a end=eof;
call missing(d4, d5, d6, other);
rc=hh_pat.find();
output;
end;
stop;
run;
or you can modify the previous post code if you will have duplicate.
... View more
Based on that A is your lookup table
data new_test1(drop=rc r);
if 0 then set a;
declare hash hh_pat(dataset:"a", multidata: "y");
rc=hh_pat.defineKey("key");
rc=hh_pat.defineData("d1", "d2", "d3");
rc=hh_pat.defineDone();
do until(eof);
set b end=eof;
call missing(d1, d2, d3);
rc=hh_pat.find();
output;
if (rc = 0) then do;
hh_pat.has_next(result: r);
do while(r ne 0);
hh_pat.find_next();
output;
hh_pat.has_next(result: r);
end;
end;
end;
stop;
run;
That should be identical to
proc sql ;
select b.key, a.d1, a.d2, a.d3 , b.d4, b.d5 , b.d6
from b left join a
on b.key=a.key;
quit;
... View more
If you cannot find the Renew SAS Software tool from the WIN Start Menu then, Try locate sasrenew.exe in ~\SAS Foundation\9.4\core\sasinst\sasrenew.
... View more
