It appears that you are trying to create the plot whenever the WHERE statement actually pulls observations.  If so, here's a way to do that: data _null_; set sashelp.cars; where make="BMW" and cylinders=3; call execute ('proc sgplot data=sashelp.cars; vbar type/dataskin=pressed; where make="BMW" and cylinders=3; run;' ); stop; run; There are other mildly similar ways to go about this as well.  If any observations meet the WHERE condition, the DATA step generates a PROC SGPLOT.  If no observations meet the WHERE condition, the DATA step generates nothing.  Either way, the DATA step ends. ... View more

@PaigeMiller's suggestion will remove all dots.  This might be exactly what you need.  OR, removing all might be too much.  You could also try:   tranwrd('L.L.C', 'LLC')   Then you need a separate statement for each word such as S.A. or S.L.   Also note, if the length of your new variable has not been defined, many character functions assign a length of $200.  You could overcome that by assigning a proper length at the beginning of the DATA step, before applying any functions. ... View more

You wil need to re-think what you are trying to do here.   First, in a SAS data set, all variables exist on every observation.  There is no possibility of keeping (or dropping) variables differently from one observation to the next.   Second, KEEP or DROP (no matter how and where specified) cannot be executed conditionally.  They cannnot be part of an IF THEN statement.   Theoretically possible if it meets your needs:  You can create two output data sets.  You could keep a different set of variables in each output data set.  And you might use the in= variables to determine which observations get output to which data sets.   ... View more

Perhaps a little simpler: data want; set have; date = input(big_long_datetime_string, : yymmdd10.); drop big_long_datetime_string; formate date yymmdd10.; run; This gets you the DATE as a proper, numeric SAS date, while getting rid of the time part.  If memory serves, however, you will need to use a DATA step because SQL will not allow the INPUT function.  (Unless times have changed, but I doubt it.) ... View more

Based on this program, what you need to compare is:   The length of TRT1 in DUMMY1 vs. The length of PLACEBO in AE4   If you try to control the length using a LENGTH statement, that statement must come before the SET statement. ... View more

This looks like an all combinations join, where this would do the trick:   proc sql noprint; create table want as select * from subjects, hospitals; quit; No macro language needed.  You just need to begin with the two SAS data sets you describe as the inputs. ... View more

Some procedures print p-values using a format.  So the "<.001" is not necessarily the actual value, just the formatted value.  If that is happening here (and it seems like it might be the case because of the bolding and the lack of an error message), just get rid of the INPUT function and refer to the variable name instead.  It's likely already a small numeric value. ... View more

It might take 3 simple statements, such as: if var3="." then var3=" "; However, first confirm the values that look like blanks or dots. Check using: proc freq data=have; tables months timepoint var3 ; format months timepoint var3 $hex6.; run; ... View more

@bhca60 ,   The requests you have received are all the right questions.  Don't just tell us what happened, show us.  These are all excellent programmers.  If any of them encountered the messages you have received, they would all debug using the same tools:  the log (including not just the error message, but the line of code that generated the message) and a PROC CONTENTS of the underlying data. ... View more

Both files conbtain incorrect formats for SAS dates.  So I wouldn't show you have to convert from one incorrect format to a different incorrect format.  But I will show you how to convert both files so they hold valid SAS dates.   For the first file, converting from character "dates":   data new_file_1; set file1; correct_dob1 = input(dob1 mmddyy10.); correct_dob2 = input(dob2, mmddyy10.); drop dob1 dob2; format correct_dob1 correct_dob2 mmddyy10.; run; For the second file, converting from numeric "dates":   data correct_file2; set file2; correct_dob1 = input(put(dob1, z8.), yymmdd8.); correct_dob2 = input(put(dob2, z8.), yymmdd8.); drop dob1 dob2; format correct_dob1 correct_dob2 mmddyy10.; run; There's a ton of information within the SAS documentation about how to store SAS dates.  Here's a starting point:  https://documentation.sas.com/doc/en/lrcon/9.4/p1wj0wt2ebe2a0n1lv4lem9hdc0v.htm   ... View more

INTCK is counting the number of times a boundary is crossed. Your program crosses a "minute" boundary twice: once at 9:57:00, and once at 9:58:00, so you get 2. ... View more

Getting only positive values is easy. For example, you could program: data want; set test; A1 = 7; A2 = 7; A3 = 7; A4 = 7; A5 = 7; run; However, if this is not the set of positive values that you have in mind, maybe you can describe what the result should look like. ... View more

Often, the best tool for applying the same logic is an array, not a macro. But as others have mentioned, you need to provide logic for a few variables for anyone to evaluate from a distance. ... View more