That is because there are very few situations where you ever would want to use the ancient MISSOVER option.   Instead you should always use the modern (probably more than 30 years old) TRUNCOVER option when you don't want the default FLOWOVER option.   The reason you would use MISSOVER in this situation is when you want SAS to IGNORE anything in columns 7 to 185 that does not completely fill all 179 bytes with something.  And since in-line data is padded to use the next multiple of 80 bytes that means that to avoid losing data when using MISSOVER with your code each line would have to have at least 161 bytes. ... View more

Sounds like you only implement HALF of the suggested fix.   If you set the parameter LABEL to the value of 'My Label' and then use "&LABEL" in the code you get "'My Label'" But if instead the macro code just uses &LABEL then you will get 'My Label' in the code, which is exactly what you want.   ... View more

That is easy. Change the macro to expect a quoted string. Then pass it a quoted string. While you are at it make it compatible with VALIDVARNAME=ANY option by using NLITERAL() function. %macro label_it (var=, label=); label &var. = &label.; %mend label_it; proc sql; select cats('%label_it' ,'(var=',nliteral(var) ,',label=',quote(trim(description),"'") ,')') into :labellist separated by ' ' from varlabels; quit; data want; set have; &labellist.; run; ... View more

Please clarify what you are trying to do. Your words make it sound like you want to drop the dataset when it does exist (you cannot drop a dataset that does not exist).  Perhaps you are worried about a warning message if you try to drop a dataset that does not exist? 1 proc delete data=no_such_data ; run; WARNING: File WORK.NO_SUCH_DATA.DATA does not exist. NOTE: PROCEDURE DELETE used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 2 proc sql; 3 drop table no_such_data; WARNING: File WORK.NO_SUCH_DATA.DATA does not exist. WARNING: Table WORK.NO_SUCH_DATA has not been dropped. 4 quit; NOTE: PROCEDURE SQL used (Total process time): real time 0.00 seconds cpu time 0.00 seconds If so then you probably need to conditionally generate CODE. The SAS macro language is good at that. 5 proc sql; 6 %if %sysfunc(exist(no_such_data)) %then %do; 7 drop table no_such_data; 8 %end; 9 quit; NOTE: PROCEDURE SQL used (Total process time): real time 0.03 seconds cpu time 0.00 seconds If instead you meant to drop the table when it has no observations then you will need a different test. ... View more

You are using the verb  "format" ambiguously.  In SAS a format is something that determines how to display a value as text.  You can attach different formats to a variable and have the values display differently.   I suspect you want to change the LENGTH of a character variable.  In that case you should also take care that the variable does not have a format attached to it that will impact how it is displayed.   If you want to change it to be length 15 from length 24 then you need to worry about lose of data.  It might be safest to make a new variable and also check the current values before copying them to the new variable to make sure they will fit. data table2 ; set table1; length plan $15 ; state=state_r ; plan=ptypcd ; if length(ptypcd) > 15 then put 'NOTE: Data will be truncated. ' _n_= ptypcd= plan=; keep state plan; run; ... View more

typo. ... View more

Disconnect/select sounds the same as restart, just in two steps instead of one.  Still better than leaving the application completely and having to restart the application. ... View more

I cannot visualize what you are trying to do. Can you provide input data and expected results. Just enough data so it demonstrates the issue.     Probably PROC FREQ is not the right tool.  For example PROC SUMMARY (aka MEANS) has methods to allow you to provide information on the complete list of possible values. ... View more

Don't use the WHERE statement.  That will prevent PROC FREQ from ever seeing the zipcodes that never have ASTHMA=1. ... View more

@Quentin wrote: That looks like  an un-related problem.  It looks like at some point in the SAS session, you may have submitted a block of code with unmatched quotation marks.  If you get this problem repeatedly, the easiest thing is to exit EG and then restart, and then search your code for unmatched quotation marks. No need to exit Enterprise Guide.  Just restart the SAS session that Enterprise Guide is using to run the SAS code. ... View more

Did you check the meaning of all of the options in the ERRORHANDLING group? Did you try setting the ERRORABEND option?   If there are situations that you consider an "error" but SAS does not (for example model does not fit) then add your own logic at that point to issue an ABORT ABEND command. ... View more

Two issues. 1) You %PUT is before you call the macro that would create NOW. 2) Unless you have created the macro variable NOW before you call the macro then the macro variable NOW it creates will be LOCAL to the macro and no longer exist when the macro finishes.   You can either define the macro variable before calling the macro: %let now=; %x2n(5,pablo,23); %put NOTE- Bienvenido son las &now; Or change the macro to make sure it doesn't define NOW as logic.  The quick (and dirty) method is to use the optional third argument to CALL SYMPUTX().  NOTE: unless there is some strange reason that you need the macro variable to have leading and/or trailing spaces you should never use the ancient CALL SYMPUT() method. %macro X2N(id,nombre,edad); title "Bienvenido %upcase(&nombre), hoy es &sysdate9."; data _null_; call symputX('now',put(time(),time5.),'g'); run; proc print data=y; run; %mend X2N; NOTE: If you want NOW to include leading zero when time() is before 10AM then use TOD format instead of TIME format.   But the better solution would be to only define NOW as GLOBAL when it does not already exist.  Then you could call this macro from another macro that has a LOCAL macro variable named NOW and be able to see the results. %macro X2N(id,nombre,edad); %if not %symexist(now) %then %global now; title "Bienvenido %upcase(&nombre), hoy es &sysdate9."; data _null_; call symputX('now',put(time(),time5.)); run; proc print data=y; run; %mend X2N;   ... View more

@Patrick wrote: @davidsmarch1  As @Tom rightfully flagged: Don't use RETURN but DELETE to always ensure the desired result.  Using RETURN will only work if you also add statement OUTPUT before the run statement. Actually RETURN or DELETE will have the same effect as they will both end the current iteration of the data step.  I think you meant don't use INPUT as that will then allow the iteration to continue to the rest of the code statements. ... View more