@whymath wrote: Thank you. I am shocked, does that means the supervisor will return control to the top of data step, after running DOW-Loop? What's the usage of this feature? That is how the data step works.   It does not care (or even really know) that you put the SET statement inside a DO loop.   Most data steps are like your first one, they stop when they read past their inputs. 2 data _null_; 3 put _n_= eof= 'BEFORE'; 4 set oneobs end=eof; 5 put _n_= eof= 'AFTER'; 6 run; _N_=1 eof=0 BEFORE _N_=1 eof=1 AFTER _N_=2 eof=1 BEFORE NOTE: There were 1 observations read from the data set WORK.ONEOBS. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 second But you can explicitly tell it when to stop, like in your second one. 8 data _null_; 9 put _n_= eof= 'BEFORE'; 10 set oneobs end=eof; 11 put _n_= eof= 'AFTER'; 12 stop; 13 run; _N_=1 eof=0 BEFORE _N_=1 eof=1 AFTER NOTE: There were 1 observations read from the data set WORK.ONEOBS. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.00 seconds Or if there are no inputs at all then it knows not to start are second iteration. 15 data _null_; 16 put _n_= bmi= 'BEFORE'; 17 bmi=(180*0.4536)/(75*0.0254)**2; 18 put _n_= bmi= 'AFTER'; 19 run; _N_=1 bmi=. BEFORE _N_=1 bmi=22.498604997 AFTER NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds And if there are inputs but you complete an iteration without actually advancing any of the inputs then it stops and says it is because of looping. 21 data _null_; 22 put _n_= eof= 'BEFORE'; 23 if _N_=1 then set oneobs end=eof; 24 put _n_= eof= 'AFTER'; 25 run; _N_=1 eof=0 BEFORE _N_=1 eof=1 AFTER _N_=2 eof=1 BEFORE _N_=2 eof=1 AFTER NOTE: DATA STEP stopped due to looping. NOTE: There were 1 observations read from the data set WORK.ONEOBS. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds ... View more

I am not sure what you are saying is the issue.   Are you just talking about how SAS in general is displaying the variable ACTUAL?  Or is it something specific to PROC COMPARE is the issue?  Or perhaps to ODS EXCEL?   Is the variable named ACTUAL numeric or character?  What display format do you have attached to it in your two input SAS dataset?  Does it display the values the way you want?   ... View more

can you explain what you want to create it more detail?  It would help if you showed an example input dataset and the output you want from it.   Also explain the reasons for any restrictions. For example why does it matter if the column headers in the EXCEL file are character strings instead of numbers?   Note if you are using the YEAR value as the indication of what variable to transpose into then you probably do NOT need to use PROC TRANSPOSE.    You can just use a DATA STEP with an ARRAY that uses YEAR as the index.  Something like this: data wide; do until(last.id); set tall; by id; array m [2014:2025] y2014-y2025 ; if year in (2014:2025) then m[year] = value; end; drop year value ; run; And if you want an EXCEL file from your TALL dataset then you might not need to transpose it at all.  Just use ODS EXCEL and PROC REPROT to make the file. ods excel file='myfile.xslx'; proc report data=tall; column id value,year; define id / group; define year/ across ' '; define value / sum ' '; run; ods excel close; ... View more

If you really want to use looping try these loops. data want; set have ; array q q1-q20; flag=0; do index=1 to dim(q) while(flag=0); if 0 < q[index] then flag=1; end; do index=1 to dim(q) while(flag=0); if q[index] in (-7 -8 -9) then flag=.; else if q[index] ne 0 then put 'WARNING: Unexpected value. ' q[index]=; end; drop index; run;   ... View more

Does not look like you need to use looping.  Instead just use functions that can operate on multiple variables. data have; input q1-q20 flag_want; datalines; 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 20 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 20 0 -7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 . -8 -7 -7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 . -7 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 ; data want; set have; if max(0,of q1-q20) > 0 then flag=1; else if whichn(-7,of q1-q20) or whichn(-8,of q1-q20) or whichn(-9,of q1-q20) then flag=.; else if 0=min(0,of q1-q20)=max(0,of q1-q20) then flag=0; run; And perhaps if those special values, -7, -8 and -9 are the only valid values that are less then zero then the second IF can be simpler.  For example you could use MIN() function. else min(0,of q1-q20)<0 then flag=.; Or if -7, -8 and -9 are really just different special missing codes if you actually code the data using special missing values (instead of valid numbers) you could use the NMISS() function.  For example by using .A, .B, and .C instead of -7, -8 and -9. missing abc ; data have; input q1-q20 flag_want; datalines; 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 20 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 20 0 A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 B 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 . B A A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 . A 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 ; data want; set have; if max(0,of q1-q20) > 0 then flag=1; else if 0<nmiss(of q1-q20) then flag=.; else if 0=min(0,of q1-q20)=max(0,of q1-q20) then flag=0; run;     ... View more

Because SAS (and most computer languages) use BINARY (base 2) floating point numbers.  Not the decimal numbers (base 10) that humans like to use.   None of those values can be exactly represented as binary numbers.  And when you add them all up the difference is enough that the normal equality test considers the values to be unequal.   Why not just the ROUND() function to reduce the number to a reasonable number of digits. data test; input x1-x4; total = sum(of x1-x4); diff = total-2; if total=2 then put TOTAL= 'is exactly 2.'; if round(total,0.0001)=2 then put TOTAl= 'is close enough to 2.' / 'since difference is ' diff:32.25 ; cards; .8 .6 .4 .2 ; ... View more

Another way to deal with this is to use an iterative DO loop (instead of using the DO OVER syntax that SAS has been trying to eliminate).  Then you can take advantage of the fact you can combine the iterative DO with an UNTIL() clause. data DSMESY2_test; set DSMESY2; array Ace ProblemSolving ReducingRisk BeingActive HealthyCoping HealthyEating Monitoring TakingMeds ; do index=1 to dim(Ace) until (AchievedGoal); AchievedGoal = (Ace[index]="Achieved"); end; drop index; run;   ... View more

Perhaps this is what you are trying to do? First let's name you variable that has DATETIME values as DATETIME instead of DATE to avoid confusion in our example.  And display it with 4 digit years for the same reason. data have; input id datetime :datetime.; format datetime datetime19.; cards; 1 27JUL25:09:00:00 2 05AUG25:10:00:00 3 15AUG25:08:00:00 4 20AUG25:21:30:00 ; Now we can make that complex string using the CATX() and PUT functions.  It does make the code simpler to first make a variable with just the DATE (number of days since 1960). data want; set have; length string $50; date=datepart(datetime); format date date9.; string = catx(', ' ,put(date,downame.) ,catx(' ',put(date,monname.),day(date)) ,put(datetime,timeampm.)); run; Result Obs id datetime string date 1 1 27JUL2025:09:00:00 Sunday, July 27, 9:00:00 AM 27JUL2025 2 2 05AUG2025:10:00:00 Tuesday, August 5, 10:00:00 AM 05AUG2025 3 3 15AUG2025:08:00:00 Friday, August 15, 8:00:00 AM 15AUG2025 4 4 20AUG2025:21:30:00 Wednesday, August 20, 9:30:00 PM 20AUG2025 ... View more

Why do you need to make so many new variables? Why not just apply different formats for different levels of granularity?   You can get very close to that desired output using a PICTURE format.  data have; input id date :datetime.; format date datetime16.; cards; 1 27JUL25:09:00:00 2 05AUG25:10:00:00 3 15AUG25:08:00:00 4 20AUG25:21:30:00 ; /* Wednesday, August 27, 2025 9:00 AM */ proc format ; picture mydt (default=40) low-high= '%F, %C %d, %Y %H:%0M %p' (datatype=datetime); ; run; proc print data=have; format date mydt.; run; Result: Obs id date 1 1 Sunday , July 27, 2025 9:00 AM 2 2 Tuesday , August 5, 2025 10:00 AM 3 3 Friday , August 15, 2025 8:00 AM 4 4 Wednesday, August 20, 2025 21:30 PM You might want to run it though the COMPBL() function however. data want; set have; string = left(compbl(put(date,mydt.))); run; Result Obs id date string 1 1 27JUL25:09:00:00 Sunday , July 27, 2025 9:00 AM 2 2 05AUG25:10:00:00 Tuesday , August 5, 2025 10:00 AM 3 3 15AUG25:08:00:00 Friday , August 15, 2025 8:00 AM 4 4 20AUG25:21:30:00 Wednesday, August 20, 2025 21:30 PM Might need to add a TRANWRD() function call also. string = tranwrd(left(compbl(put(date,mydt.))),' ,',','); ... View more

There are two ways to produce that type of a listing.   If your variable named DATE has DATETIME values with the DATETIME format attached to it with a width between 16 and 18.  NOTE: the DATETIME format has a bug and you must specify at width of at least 19 for it to actually print the 18 characters needed to display datetime value with 4 digit years. data have; input id date :datetime.; format date datetime16.; cards; 1 27JUL25:09:00:00 2 05AUG25:10:00:00 3 15AUG25:08:00:00 4 20AUG25:11:30:00 ; But then I do not know what you are asking for help with since you already have the value as a datetime.  If the variable is datetime already what is your actual question?   But perhaps instead you have the DATE variable defined as CHARACTER instead. data have; input id date :$16.; cards; 1 27JUL25:09:00:00 2 05AUG25:10:00:00 3 15AUG25:08:00:00 4 20AUG25:11:30:00 ; Both of those will print the same way:   In that case to work with those values as actual datetime values you will need to first convert them.  And you will need to make a new variable since the variable DATE is already defined as a character variable. data want; set have; datetime = input(date,datetime24.); format datetime datetime19.; run; Result: Note it does not matter if you have 4 observations or hundreds or millions the code is the same. ... View more

You were almost there. The pattern you want is something like: AchievedGoal="No "; do over Ace; if Ace = "Achieved" then AchievedGoal="Yes"; end; You set the result to false before the loop.  Then in the loop set it to true when the condition is met. ... View more

Since you are running a macro.  And a macro that already generates steps (PROC REPORT) you can add the commands to shut down listing to your macro.   You could just close the listing and open it again. .... ods listing close; proc report ..... ods listing ; ... But that would open the listing if it wasn't open before.   Instead why not use ODS SELECT instead and only generate the commands when the listing destination is active. data _null_; set sashelp.vdest; where destination='LISTING'; call execute('ods listing select none;'); run; proc report .... ... data _null_; set sashelp.vdest; where destination='LISTING'; call execute('ods listing select all;'); run; ... View more