I recently just had this issue, and I noticed that SAS had shortened the name of the interaction variable when I printed out the dataset.    An example of the proc print:   proc print data = a_preg; where _imputation_ = 1; run;   My variable's name had been shortened from new_surgery1*timetrying to new_surge*timetrying. Once I included the shortened variable name in PROC MIANALYZE, the program was able to run sufficiently.   Hope that works for you as well, because this error took me hours to troubleshoot.   ... View more

SQL is by far the best approach i think however hash is fun data current; infile cards; input id visit_date; attrib visit_date length=4 informat=date9. format=ddmmyy10.; cards; 1 01nov14 1 11nov14 2 22nov15 2 24nov15 3 01nov16 4 01nov16 ; run; data previous; infile cards; input id last_date; attrib last_date length=4 informat=date9. format=ddmmyy10.; cards; 1 01jan14 1 11feb14 1 02jan15 1 01nov14 2 01nov15 2 22nov15 2 23nov15 3 01nov16 4 12nov16 ; run; data want; if _n_=1 then do; if 0 then do; set current;set previous;end; declare hash h(dataset: 'previous',multidata:'y'); h.definekey('id'); h.definedata('last_date'); h.definedone(); end; set current; rc=h.find(); do while(rc = 0); if visit_date>last_date then _t=max( _t, last_date); rc = h.find_next(); end; last_date=_t; drop rc _:; run; ... View more

Obviously, choose whichever method you think will work best for you. I have one question, though: is there anything that can be used to consistently differentiate between variable name and data lines?  If there is, a solution can be achieved that would work without ever having to modify the code. ... View more

JITTER is supported at SAS 9.4.  Jitter kicks in when the data is very dense.  But it may not kick in for sashelp.class. proc sgplot data=sashelp.cars(where=(type ne 'Hybrid'));   scatter x=type y=mpg_city / jitter           MARKERATTRS=(symbol=circlefilled);   run; We are considering other types of jitter and options.  Please feel free to provide your suggestions. ... View more

And here:  https://communities.sas.com/message/215449#215449 ... View more